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:
Installation of latest RHEL-8.4 builds fails, probably due to waiting on unconnected Ethernet interfaces
Version-Release number of selected component (if applicable):
RHEL-8.4.0-20210113.n.1 BaseOS x86_64
RHEL-8.4.0-20210114.n.0 BaseOS x86_64
How reproducible:
4/4 on dell-per7425-02.khw.lab.eng.bos.redhat.com and lenovo-sr650-02.lab.eng.rdu2.redhat.com, possibly other x86_64 with multiple Ethernet devices, where some are not connected to network
Steps to Reproduce:
1. install latest x86_64 RHEL-8.4.0 build using Beaker
2. wait for the job to fail
3. see console output
Actual results:
Beaker jobs J:4981006, J:4980987, J:4979888, J:4979996
Console output like:
(...)
] Reached target Basic System.
[ 19.062675] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 19.092631] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 19.100303] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
[ 19.151588] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
[ 19.158578] IPv6: ADDRCONF(NETDEV_UP): eno3: link is not ready
[ 19.207064] IPv6: ADDRCONF(NETDEV_UP): eno3: link is not ready
[ 19.213673] IPv6: ADDRCONF(NETDEV_UP): eno4: link is not ready
[ 19.261921] IPv6: ADDRCONF(NETDEV_UP): eno4: link is not ready
[ 19.268666] IPv6: ADDRCONF(NETDEV_UP): enp5s0f3u1u3: link is not ready
[ 22.278454] igb 0000:04:00.0 eno3: igb: eno3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[ 22.287677] IPv6: ADDRCONF(NETDEV_CHANGE): eno3: link becomes ready
[ 25.875513] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 25.882827] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
[ 25.890397] IPv6: ADDRCONF(NETDEV_UP): eno4: link is not ready
[
OK
] Started cancel waiting for multipath siblings of sda.
[ 32.511755] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 32.519102] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
[ 32.526666] IPv6: ADDRCONF(NETDEV_UP): eno4: link is not ready
(last 3 rows repeat until installation fails)
Expected results:
installation successfull
Additional info:
From the first look, seems like waiting for all network interfaces to be configured by DHCP, even those not connected. Could you have a look if this is the real cause of the failed installation?
(not graphical installation, could not find a better component than Anaconda)