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 at OVS bridge is created and a vxlan port is attached the "base-iface" appears at nmstatectl show as empty instead of having the ovs-bridge name.



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


How reproducible: Always


Steps to Reproduce:
1. ovs-vsctl add-br br0 
2. ovs-vsctl add-port br0 vx_node1 -- set interface vx_node1 \
  type=vxlan options:remote_ip=192.168.122.174
3. nmstatectl show 



Actual results:
The "base-iface" field is empty

Expected results:
The "base-iface" should point to ovs bridge br0


Additional info:
It also ends with nasty failure in case the vxlan port is up and we try to configure a state, since the parent is empty [1]

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2078573

RHEL 8.6 scratch build is at https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=44959699

To reproduce this problem:

 * ovs-vsctl add-br br0_with_vxlan
 * ovs-vsctl add-port br0_with_vxlan vx_node1 -- \
    set interface vx_node1 type=vxlan options:remote_ip=192.168.122.174 \
    options:dst_port=8472
 * nmcli d set vxlan_sys_8472 managed false
 * Use nmstatectl to apply any state.

Verified with versions:
nmstate-1.3.0-0.alpha.20220505.el8.x86_64
nispor-1.2.3-1.el8.x86_64
NetworkManager-1.39.5-1.el8.x86_64
openvswitch2.15-2.15.0-103.el8fdp.x86_64
Linux hpe-dl380pgen8-02-vm-14.hpe2.lab.eng.bos.redhat.com 4.18.0-393.el8.x86_64 #1 SMP Wed May 18 12:44:50 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
DISTRO=RHEL-8.7.0-20220524.0

Nmstate doens't support ovs vxlan, so the `base-iface: ''` of ovs vxlan is still there, but it doesn't impact applying any other new state.

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