In /etc/init.d/vz line 96 # we don't operate on a running interface if /sbin/ip addr list | grep -q "venet0:.*UP" 2>/dev/null; then return 0 fi Line 97 faiuls due to this (from iproute2 changelog): *iproute2-3.5.0-r1 (13 Aug 2012) 13 Aug 2012; Mike Frysinger <vapier@gentoo.org> +files/iproute2-3.5.0-ip-a-s.patch, +iproute2-3.5.0-r1.ebuild: Fix `ip a s` so it shows addresses #430320 by Graham Murray. Move ip into /bin #330115 by Thilo Bangert. As the ebuild in question no longer exists in the tree I cannot tell if any thought was given to possible consequences of this move giving a warning of any sort, at least there is none in the oldest next after it 3.5.1, anyhow not sure what the proper fix is for openvz and vzctl, a symlink, init script test or depend on iproute2-3.4.0? Anyhow it's a bug and should be fixed in some end. Reproducible: Always Steps to Reproduce: on an openvz-sources system 1. Run unstable aka KEYWORDS="~amd64" 2. Emerge vzctl iproute2 3. /etc/init.d/vz restart Actual Results: I can't get the error output in here as this luckily came out on an isolated test system but basically it fails to load containers as the script fail in a /sbin/ip not existent error. Expected Results: script should succeed and load containers.
I may add, creating the symlink, # ln -s /bin/ip /sbin/ip seem to work although I don't know if this is a wise solution or if if may cause other complications. At least containers load and can be used.
Wranglers, please assigne vz bugs to me Thanks
upstream informed
Fixed in git: http://git.openvz.org/?p=vzctl;a=commit;h=2fc34ffb5f5e
+ 03 Jan 2013; Sergey Popov <pinkbyte@gentoo.org> -vzctl-3.3.ebuild, + -vzctl-3.3-r1.ebuild, +vzctl-3.3-r2.ebuild, + +files/vzctl-3.3-initscript-paths.patch: + Fix initscript paths, wrt bug #444201. Patch by Kir Kolyshkin. Drop old + revisions
