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 1710936[details]
verified.log
Verified with versions:
nmstate-0.3.4-10.el8.noarch
NetworkManager-1.26.0-2.el8.x86_64
DISTRO=RHEL-8.3.0-20200728.n.0
Linux dell-r330-15.gsslab.brq.redhat.com 4.18.0-228.el8.x86_64 #1 SMP Mon Jul 27 06:05:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
openvswitch-selinux-extra-policy-1.0-19.el8fdp.noarch
openvswitch2.13-2.13.0-49.el8fdp.x86_64
python3-openvswitch2.13-2.13.0-49.el8fdp.x86_64
Brief of the log in attachment:
1. Always show NM.connection.uuid
2. Edit ovs0, when external-ids was not touched, the previous one would be preserved
3. Be able to add user-defined external-ids, but should provide all key-value pairs, if one key was not mentioned, it would be removed(except for NM.connection.uuid)
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-2020:4696
Description of problem: Missing NM UUID in ovs external_ids on creating Version-Release number of selected component (if applicable): python3-libnmstate-0.3.4-9.el8.noarch nmstate-0.3.4-9.el8.noarch nmstate-plugin-ovsdb-0.3.4-9.el8.noarch NetworkManager-1.26.0-2.el8.x86_64 openvswitch-selinux-extra-policy-1.0-19.el8fdp.noarch openvswitch2.13-2.13.0-49.el8fdp.x86_64 How reproducible: 100% Steps to Reproduce: 1. echo "--- interfaces: - name: ovs0 type: ovs-interface state: up ovs-db: external_ids: abc: def - name: ovs-br0 type: ovs-bridge state: up bridge: port: - name: ovs0" | nmstatectl set 2. nmstatectl show ovs0 3. Actual results: interfaces: - name: ovs0 type: ovs-interface state: up ipv4: enabled: false dhcp: false ipv6: enabled: false autoconf: false dhcp: false lldp: enabled: false mac-address: CA:DE:58:34:F2:7C mtu: 1500 ovs-db: external_ids: abc: def Expected results: Additional info: