Bug 948824 - ifup-aliases arping check takes too long
ifup-aliases arping check takes too long
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: initscripts (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Lukáš Nykrýn
: 948833 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2013-04-05 09:17 EDT by Chris Adams
Modified: 2016-11-25 07:57 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Users were not informed about performing ARP check well. Consequence: Users might be confused about time needed to bring the interface up. Fix: On every arp check print out the message to user. Result: User is informed about what is happening.
Story Points: ---
Clone Of:
Last Closed: 2013-11-21 17:12:06 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Adams 2013-04-05 09:17:35 EDT
The change in ifup-aliases to arping every address takes way too long, especially on systems with lots of IPs (web hosting servers for example).  I'm using ifcfg-*range* files to create lots of aliases rapidly (380 on one server for example), but with the arping added, my 2 minute reboot goes up to 15, with no output at the console about what is happening (just looks like the system is hung).

ARPCHECK=no should be the default for range files (which are typically used for lots of IPs), and there should be some console output about what is happening.  If this is going to be enabled by default for range files, there should be a better way to check (some type of parallel check or something; anything that doesn't take 2 seconds per IP).

Also, while I saw the technical note about ifup-aliases checking for duplicate IPs, it didn't mention that this would cause a 2 second pause for each additional IP, nor did it mention the ARPCHECK=no setting to disable this.  This should have been better documented (and IMHO such a change should have defaulted to off).
Comment 1 Lukáš Nykrýn 2013-04-05 10:55:19 EDT
*** Bug 948833 has been marked as a duplicate of this bug. ***
Comment 2 Lukáš Nykrýn 2013-04-05 11:22:13 EDT
Thanks for submitting this bug. In previous version there was no possibility to check for duplicates for aliases and I think that was wrong. I agree that this change id not ideal for everyone and I should mention ARPCHECK=no in release notes. I don't think that disabling arp check by default for some set of configuration files would be the best way, because it would bring inconsistency. I also can't add parallel check for this, because that could cause nondeterministic behavior. Because of these reasons, I would rather keep current behavior, but I am open to other suggestions and I will definitely consider adding some info message about running arping, so the system would not look stuck.
Comment 3 Chris Adams 2013-04-05 12:23:43 EDT
I did figure out one inconsistency (that confused me for a bit): I had two servers that were not affected by this change.  They have nVidia network interfaces with the forcedeth module, and it apparently doesn't set /sys/class/net/<dev>/operstate, so ifup-aliases didn't run arping on those servers.  It looks like nothing else (at least in the "classic" network scripts) checks operstate, so that should probably be changed (add check to ifup or drop it from ifup-aliases).

Anyway, I understand the motivation for the change (I'm mostly just frustrated by it being made in the middle of RHEL 6, even at a point release, and that the effects weren't more prominently documented).  I'd suggest that all arping checks (including in ifup-eth) should probably print a message, since each one causes a two-second pause (in the normal case of "no conflict found").  I hadn't really looked, but I'd wondered why "ifup eth0" with a static IP (and no aliases) went from a fraction of a second to several seconds; printing something would be good.
Comment 12 errata-xmlrpc 2013-11-21 17:12:06 EST
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.


Note You need to log in before you can comment on or make changes to this bug.