Bug 1774074

Summary: Creating vxlan fails with NME_UNSPEC
Product: Red Hat Enterprise Linux 8 Reporter: Quique Llorente <ellorent>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.1CC: atragler, bgalvani, fgiudici, hannsj_uhl, lrintel, pasik, rkhan, sukulkar, thaller, vbenes
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-1.22.0-0.2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:53:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs from failing ci https://travis-ci.com/nmstate/nmstate/jobs/258153028 none

Description Quique Llorente 2019-11-19 14:04:03 UTC 
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:
Comment 1 Beniamino Galvani 2019-11-19 14:52:17 UTC 
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?
Comment 2 Quique Llorente 2019-11-20 10:33:52 UTC 
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
Comment 3 Beniamino Galvani 2019-11-22 09:03:15 UTC 
Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/344
Comment 4 Beniamino Galvani 2019-11-25 08:00:15 UTC 
Should be fixed by:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/a73efb059f5ffdcc200ec30c443d06b6d656fcfe
Comment 5 Beniamino Galvani 2019-11-29 10:16:57 UTC 
*** Bug 1772382 has been marked as a duplicate of this bug. ***
Comment 8 errata-xmlrpc 2020-04-28 16:53:59 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, 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