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.
Created attachment 1910738[details]
nmstate yaml
Description of problem:
Running nmstatectl gc with the attached yaml sets dns settings on a seemingly random interface every run. Sometimes including disabled interfaces leading to the following NetworkManager warning:
Sep 06 21:59:27 localhost NetworkManager[1740]: <warn> [1662501567.3995] keyfile: load: "/etc/NetworkManager/system-connections/ens6.nmconnection": failed to load connection: invalid connection: ipv4.dns: this property is not allowed for 'method=disabled'
Version-Release number of selected component (if applicable):
2.1.4
How reproducible: 100%
Steps to Reproduce:
1. run `nmstatectl gc` using the provided config several times
2. observe output
Actual results:
Interface with dns settings varies every run
Expected results:
dns settings are set on all active interfaces and not on disabled interfaces (or at least one active interface)
I'm not entirely sure this is the correct behavior, but based on the structure of the yaml this is what I expected.
Additional info:
This was encountered during an OCP installation with assisted installer.
The install failed because /etc/resolv.conf was missing.
I'm not entirely sure this was the root cause (dns settings being set on a disabled interface), but it seems suspicious.
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:2190
Created attachment 1910738 [details] nmstate yaml Description of problem: Running nmstatectl gc with the attached yaml sets dns settings on a seemingly random interface every run. Sometimes including disabled interfaces leading to the following NetworkManager warning: Sep 06 21:59:27 localhost NetworkManager[1740]: <warn> [1662501567.3995] keyfile: load: "/etc/NetworkManager/system-connections/ens6.nmconnection": failed to load connection: invalid connection: ipv4.dns: this property is not allowed for 'method=disabled' Version-Release number of selected component (if applicable): 2.1.4 How reproducible: 100% Steps to Reproduce: 1. run `nmstatectl gc` using the provided config several times 2. observe output Actual results: Interface with dns settings varies every run Expected results: dns settings are set on all active interfaces and not on disabled interfaces (or at least one active interface) I'm not entirely sure this is the correct behavior, but based on the structure of the yaml this is what I expected. Additional info: This was encountered during an OCP installation with assisted installer. The install failed because /etc/resolv.conf was missing. I'm not entirely sure this was the root cause (dns settings being set on a disabled interface), but it seems suspicious.