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.
DescriptionBeniamino Galvani
2022-01-12 10:24:25 UTC
Description of problem:
If a connection profile has connection.multi-connect=multiple, then the number of autoconnect retries is global across all connection attempts for the profile; instead it should be per-device.
Version-Release number of selected component (if applicable):
1.35.3, and any previous NM version since connection.multi-connect was introduced
Steps to Reproduce:
1. Prepare a machine with two interfaces eth0 and eth1 connected to a network without DHCP server
2. Create a connection profile with connection.multi-connect=multiple, connection.autoconnect-retries=2 and without interface name
3. Check that at boot the connection starts on both devices
Actual results:
4. After the connection fails on eth0, it is retried one time
5. After the connection fails on eth1, it is not retried because eth0 already decreased the autoconnect counter for the profile
Expected result:
4. After the connection fails on eth0, it is retried one time
5. After the connection fails on eth1, it is retried one time
Additional info:
In NM 1.26, nm-initrd-generator used to create profiles with 4 autoconnect retries and a DHCP timeout of 45 seconds. That means that for profiles bound to a single device NM would wait in the initramfs for 45*4=180 seconds. However, due to this bug, if the profile had multiconnect enabled (as for `ip=dhcp`) then some devices could wait 45s, some more, depending on the number of devices and activation order.
Since NM 1.30, nm-initrd-generator creates profiles with autoconnect-retries=1 and a DHCP timeout of 90 seconds, so this issue is no longer visible because each devices tries exactly one time.
However, the issue is still present for non-initramfs activations.
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 (NetworkManager bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:6585