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.
This bug was created per request in Bug #1660250 Comment 35
Description of problem:
When applying a configuration via nmstatectl, the subsequent connections may be created with duplicate names even though they were previously created with different names.
Version-Release number of selected component (if applicable):
CentOS Stream 9
python3-libnmstate-2.0.0-0.3.alpha2.el9.noarch
nmstate-2.0.0-0.3.alpha2.el9.noarch
How reproducible:
100%
Steps to Reproduce:
nmcli conn add type ovs-bridge conn.interface br-test con-name br-test
nmcli conn add type ovs-port conn.interface br-test master br-test con-name ovs-port-br-test
nmcli conn add type ovs-interface slave-type ovs-port conn.interface br-test master ovs-port-br-test con-name ovs-if-br-test
nmcli conn add type ovs-port conn.interface ens4 master br-test con-name ovs-port-ens4
nmcli c add type ethernet conn.interface ens4 master ovs-port-ens4 con-name ovs-if-ens4
sleep 2
nmcli c
ip a
nmstatectl show > ovs.yaml
nmcli c del ovs-if-ens4
nmcli c del ovs-port-ens4
nmcli c del ovs-if-br-test
nmcli c del ovs-port-br-test
nmcli c del br-test
sleep 2
nmcli c
ip a
nmstatectl apply < ovs.yaml
nmcli c
ip a
Actual results:
[root@multi-0 ~]# nmcli c
NAME UUID TYPE DEVICE
ens3 21d47e65-8523-1a06-af22-6f121086f085 ethernet ens3
ovs-if-br-test 4a6f5baf-1ca6-42bf-be5c-f7ee9a3959af ovs-interface br-test
br-test ff04d669-d9be-4aae-9f39-7a82ddafdad3 ovs-bridge br-test
ovs-if-ens4 434569d3-beb3-443c-b3d7-d0280ce987cb ethernet ens4
ovs-port-br-test 5d08a55f-b838-4f05-ac2a-3567f404b175 ovs-port br-test
ovs-port-ens4 6e6dc015-c27d-4564-a028-a63d80fcc2f8 ovs-port ens4
[root@multi-0 ~]# nmstatectl show > ovs.yaml
<connections deleted>
[root@multi-0 ~]# nmstatectl apply < ovs.yaml
...SNIP...
[root@multi-0 ~]# nmcli c
NAME UUID TYPE DEVICE
ens3 21d47e65-8523-1a06-af22-6f121086f085 ethernet ens3
br-test 6ad48c2d-3369-43bc-8994-5925f56e910f ovs-interface br-test
br-test 2918c4f2-e21b-4f8b-a5cc-726404891aa5 ovs-bridge br-test
ens4 990fff7a-442e-4330-9895-5841aafa5b6c ethernet ens4
ovs-port-br-test 7c120f2d-a5d8-40fe-b671-bbba5d6c872d ovs-port ovs-port-br-test
ovs-port-ens4 dcccd26c-30ee-48c4-9582-810d733fabce ovs-port ovs-port-ens4
Expected results:
The interfaces should not be renamed when applied and should not be duplicated. In this case ens4 was ovs-if-ens4 and the ovs-interface br-test was originally ovs-port-br-test
Comment 1Fernando F. Mancera
2021-09-02 16:14:24 UTC
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 (new packages: nmstate), 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/RHEA-2022:2338