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: When an interface is set to have both ipv4 and ipv6 dynamic addresses the ipv4.may-fail and ipv6.may-fail attributes should also be set so the interface waits for both addresses before being considered up. Currently this is not happening, which can cause problems for components that wait on interface status and need both addresses to be configured.
This was initially reported in https://issues.redhat.com/browse/OCPBUGS-3394 but since I think it needs to be fixed in NMState I'm moving it to a bz.
Version-Release number of selected component (if applicable): Reported against OCP 4.12, so I believe it would be based on RHEL 8.6.
How reproducible: Always
Steps to Reproduce:
1. Generate connection profiles with ipv4 and ipv6 both enabled on an interface. For example,
interfaces:
- name: eno3
type: ethernet
state: up
ipv4:
enabled: true
dhcp: true
ipv6:
enabled: true
dhcp: true
Actual results:
[connection]
id=eno3
uuid=ea4b2498-c55e-49b2-96d4-81cd18c1088c
type=ethernet
interface-name=eno3
[ethernet]
[ipv4]
dhcp-timeout=2147483647
method=auto
[ipv6]
addr-gen-mode=eui64
dhcp-iaid=mac
dhcp-timeout=2147483647
method=dhcp
ra-timeout=2147483647
[proxy]
Expected results:
[connection]
id=eno3
uuid=ea4b2498-c55e-49b2-96d4-81cd18c1088c
type=ethernet
interface-name=eno3
[ethernet]
[ipv4]
dhcp-timeout=2147483647
method=auto
may-fail=no
[ipv6]
addr-gen-mode=eui64
dhcp-iaid=mac
dhcp-timeout=2147483647
method=dhcp
ra-timeout=2147483647
may-fail=no
[proxy]
Additional info:
I don't believe we're planning to ship any releases on 8.8, so we don't need it there. The OCP release this was reported against is based on 8.6 so if it's possible to backport to that release it would be helpful to us. The severity of the original bug is only moderate, however, so if that's a big hassle we can probably wait until 4.13, although that may be based on 9.0, in which case we'd still be missing this fix.
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 (nmstate 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:2772