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 I generate nmconnection files with "nmstatectl gc" and apply them to a node, the bridge is not correctly created. When I apply the same configuration using the kubernetes-nmstate operator, the bridge is created as expected. I find very few differences between the generated nmconnection files. The main difference seems to be that the files applied directly via nmstatectl define their master devices by UUID, whereas the ones generated by gc define masters by name.
It looks like there may be a conflict between the applied configuration and the default connection that just DHCPs all interfaces, but I haven't found a way to keep the default connection from overriding the one I apply.
Version-Release number of selected component (if applicable): 1.0.2
How reproducible: Always
Steps to Reproduce:
1. Create configuration files for ovs-bridge (see below) using nmstatectl gc
2. Apply those files to OCP node
Actual results:
Bridge br-ey
Port br-ey
Interface br-ey
type: internal
Expected results:
Bridge br-ey
Port br-ey
Interface br-ey
type: internal
Port enp3s0
Interface enp3s0
type: system
Additional info:
nmstate-config for bridge
interfaces:
- name: enp3s0
type: ethernet
state: up
ipv4:
enabled: false
ipv6:
enabled: false
- name: br-ey
type: ovs-bridge
state: up
bridge:
port:
- name: enp3s0
- name: br-ey
- name: br-ey
type: ovs-interface
state: up
ipv4:
enabled: true
dhcp: true
auto-dns: true
auto-gateway: true
auto-routes: true
ipv6:
enabled: false
dhcp: false
I was able to get this working by adding a config file to NetworkManager with the following contents:
[device-enp3s0]
match-device=interface-name:enp3s0
keep-configuration=no
allowed-connections=except:origin:nm-initrd-generator
I don't know if there's any way to do the same thing with pure connection profiles, but if not that might be a good feature request.
Hi Ben,
I am not able to reproduce this issue in my VM. Base on my guessing, could you try rpm from this copr repo?
dnf copr enable packit/nmstate-nmstate-1933
Thank you!
This is very strange. With the copr build I can see that the nmconnection files generated by gc match in basically every way except the specific UUIDs now, but on my standalone VM it still doesn't configure correctly unless I use "nmstatectl apply". I even tried saving off the nmconnection profiles from an apply call, and if I manually copy those into place they have the same problem as the gc ones.
One note is that we use "ip=dhcp" on the kernel command line of our nodes. Maybe that's why you don't see it in your VM?
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-2022:7465
Description of problem: When I generate nmconnection files with "nmstatectl gc" and apply them to a node, the bridge is not correctly created. When I apply the same configuration using the kubernetes-nmstate operator, the bridge is created as expected. I find very few differences between the generated nmconnection files. The main difference seems to be that the files applied directly via nmstatectl define their master devices by UUID, whereas the ones generated by gc define masters by name. It looks like there may be a conflict between the applied configuration and the default connection that just DHCPs all interfaces, but I haven't found a way to keep the default connection from overriding the one I apply. Version-Release number of selected component (if applicable): 1.0.2 How reproducible: Always Steps to Reproduce: 1. Create configuration files for ovs-bridge (see below) using nmstatectl gc 2. Apply those files to OCP node Actual results: Bridge br-ey Port br-ey Interface br-ey type: internal Expected results: Bridge br-ey Port br-ey Interface br-ey type: internal Port enp3s0 Interface enp3s0 type: system Additional info: nmstate-config for bridge interfaces: - name: enp3s0 type: ethernet state: up ipv4: enabled: false ipv6: enabled: false - name: br-ey type: ovs-bridge state: up bridge: port: - name: enp3s0 - name: br-ey - name: br-ey type: ovs-interface state: up ipv4: enabled: true dhcp: true auto-dns: true auto-gateway: true auto-routes: true ipv6: enabled: false dhcp: false