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.
Description of problem:
In dracut's 40network module, arping is used to detect Duplicate addresses :
40network/ifup.sh:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
if ! arping -f -q -D -c 2 -I $netif $ip; then
warn "Duplicate address detected for $ip for interface $netif."
return 1
fi
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
40network/dhclient-script.sh code:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
if ! arping -f -q -D -c 2 -I $netif $new_ip_address ; then
warn "Duplicate address detected for $new_ip_address while doing dhcp. retrying"
exit 1
fi
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
For some reason, if the network interface is not available, in particular in the "ifup.sh" case (because for dhclient, it's retried), arping will print "Device XXX not available" but then dracut will abort and print "Duplicate address detected" which is not the real error.
Version-Release number of selected component (if applicable):
All dracut version, including RHEL8's one
How reproducible:
Don't know how to reproduce arping's "Device XXX not available" error
Additional info:
arping returns exit(2) upon device error and other errors (mostly getopt errors), whereas exit(1) is returned when a duplicate address is found:
exit(2):
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
int
main(int argc, char **argv)
{
[...]
fprintf(stderr, "arping: Device %s not available.\n", device.name);
exit(2);
[...]
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
exit(1) (Duplicate address detection, dad == 1):
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
void finish(void)
{
if (!quiet) {
printf("Sent %d probes (%d broadcast(s))\n", sent, brd_sent);
printf("Received %d response(s)", received);
[...]
if (dad)
exit(!!received);
[...]
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Dracut code should distinguish between rc == 2 and rc == 1 instead of using "! arping" test condition.
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed.
From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."
If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook
Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product.
Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.
[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7
Description of problem: In dracut's 40network module, arping is used to detect Duplicate addresses : 40network/ifup.sh: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- if ! arping -f -q -D -c 2 -I $netif $ip; then warn "Duplicate address detected for $ip for interface $netif." return 1 fi -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 40network/dhclient-script.sh code: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- if ! arping -f -q -D -c 2 -I $netif $new_ip_address ; then warn "Duplicate address detected for $new_ip_address while doing dhcp. retrying" exit 1 fi -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- For some reason, if the network interface is not available, in particular in the "ifup.sh" case (because for dhclient, it's retried), arping will print "Device XXX not available" but then dracut will abort and print "Duplicate address detected" which is not the real error. Version-Release number of selected component (if applicable): All dracut version, including RHEL8's one How reproducible: Don't know how to reproduce arping's "Device XXX not available" error Additional info: arping returns exit(2) upon device error and other errors (mostly getopt errors), whereas exit(1) is returned when a duplicate address is found: exit(2): -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- int main(int argc, char **argv) { [...] fprintf(stderr, "arping: Device %s not available.\n", device.name); exit(2); [...] -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- exit(1) (Duplicate address detection, dad == 1): -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- void finish(void) { if (!quiet) { printf("Sent %d probes (%d broadcast(s))\n", sent, brd_sent); printf("Received %d response(s)", received); [...] if (dad) exit(!!received); [...] -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Dracut code should distinguish between rc == 2 and rc == 1 instead of using "! arping" test condition.