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.

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).

*** This bug has been marked as a duplicate of bug 948824 ***