Bug 1207975
Summary: | ifup-aliases does not proper catch arping failure | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Peter Bieringer <pb> | |
Component: | initscripts | Assignee: | initscripts Maintenance Team <initscripts-maint-list> | |
Status: | CLOSED ERRATA | QA Contact: | Jan Ščotka <jscotka> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.1 | CC: | alexander, fedoraproject, jscotka, kskoda, lnykryn, trianman | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | initscripts-9.49.25-1.el7 | Doc Type: | Bug Fix | |
Doc Text: |
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:
|
Story Points: | --- | |
Clone Of: | ||||
: | 1275550 (view as bug list) | Environment: | ||
Last Closed: | 2015-11-19 11:29:44 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1275550 |
Description
Peter Bieringer
2015-04-01 06:53:24 UTC
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 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 |