Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
We use arping for detection of duplicate ip addresses on the network. For aliases previous check failed not only in the case that there was a duplicate address on the network, but also in the case that arping failed for some other reason.
Consequence:
Fix:
Now we fail only in the case that there is a duplicit address on the network.
Result:
DescriptionPeter Bieringer
2015-04-01 06:53:24 UTC
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
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.
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).
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
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