Description of problem: After latest EL7 updates VMs on Virtuozzo having public IPv4 addresses only configured in alias config files the IPv4 addresses are no longer applied. Version-Release number of selected component (if applicable): initscripts-9.49.24-1.el7.x86_64 Mi 01 Apr 2015 01:08:31 CEST How reproducible: always after reboot Steps to Reproduce: 1. update initscript 2. reboot Actual results: Only the IPv6 address is applied, defined in /etc/sysconfig/network-scripts/ifcfg-venet0 Expected results: IPv4 addresses also applied from /etc/sysconfig/network-scripts/ifcfg-venet0:0 /etc/sysconfig/network-scripts/ifcfg-venet0:1 Additional info: while ifup-eth is catching the return code of arping already proper, ifup-aliases still don't. Workaround: fix script manually until a fixed initscript package is available --- ifup-aliases.orig 2015-04-01 08:46:08.179879018 +0200 +++ ifup-aliases 2015-04-01 08:46:52.558427785 +0200 @@ -261,7 +261,8 @@ is_available ${parent_device} && \ ( grep -qswi "up" /sys/class/net/${parent_device}/operstate || grep -qswi "1" /sys/class/net/${parent_device}/carrier ) ; then echo $"Determining if ip address ${IPADDR} is already in use for device ${parent_device}..." - if ! /sbin/arping -q -c 2 -w ${ARPING_WAIT:-3} -D -I ${parent_device} ${IPADDR} ; then + /sbin/arping -q -c 2 -w ${ARPING_WAIT:-3} -D -I ${parent_device} ${IPADDR} + if [ $? = 1 ]; then net_log $"Error, some other host already uses address ${IPADDR}." return 1 fi
dev_ack for fixing this in 7.2
JFYI: OpenVZ guys fixed this problem in another way: http://git.openvz.org/?p=vzctl;a=commitdiff;h=24a0a40277542fba;hp=f4d35dde74fd74ab068e34748919ac0b9a6a21aa But vzctl with this fix is not yet released. Of course this does not negate the need to fix initscripts package.
This needs to be fixed immediately! There are thousands of OpenVZ containers that are broken and NOONE knows it. When they reboot, they will be zombie OpenVZ containers with no network access. This functionality was taken away from 17 to 24, and needs to be returned immediately.
Can you please file a ticket through customer portal? That will speed things up.
I can't open a ticket because I found the issue on a private CentOS 7 system hosted @Strato - but Red Hat QA should have strong interest to get this fixed asap before all the OpenVZ containers reboot and have broken IPv4 connectivity all around the world. Container customers and support of the platform will get very unhappy then. (I was able to fix mine by myself, because IPv6 config was defined in main ifcfg-venet0 and therefore not affected).
upstream fix: https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=55a50ebc591ebd0f4cfbb8ecc204fa20ee6a7368
https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel7-branch&id=eeb66ed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2134.html