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 1637704 [details]
logs from failing ci https://travis-ci.com/nmstate/nmstate/jobs/258153028

Description of problem:

Trying to create a vxlan interface with nmstate end with error:
2019-11-19 13:56:23 nmclient.py:180 ERROR NM main-loop aborted: Connection activation failed on connection_id eth1.101: error=nm-device-error-quark: eth1.101 failed to create resources: Failed to create VXLAN interface 'eth1.101' for 'eth1.101': NME_UNSPEC (1)



Version-Release number of selected component (if applicable):

1.20

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

The error reported by kernel is:

  platform-linux: netlink: recvmsg: error message from kernel: File exists (17) "A VXLAN device with the specified VNI already exists" for request 10070

Can you check if a VXLAN with id 101 already exists?

Looks like removing the profile is not enough so we have to force removing the device at nmstate, is similar issue with OVS 

https://github.com/nmstate/nmstate/compare/6aab8598400834dc721345242e595db084315a98..7f8d836c5692937c94e7ca501f16881aa4c939d5#diff-de1f01201a749955840472d0101bf589R189

Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/344

Should be fixed by:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/a73efb059f5ffdcc200ec30c443d06b6d656fcfe

*** Bug 1772382 has been marked as a duplicate of this bug. ***

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, 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:1847