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.
Description of problem:
In recent version, when there is no any port mentioned, nmstate will automatically create an internal port whose name is same with the ovs bridge.
Now this self-created port cannot be easily removed.
Version-Release number of selected component (if applicable):
Verified with:
nmstate-2.2.3-3.el9.x86_64
nispor-1.2.9-1.el9.x86_64
NetworkManager-1.41.7-2.el9.x86_64
openvswitch2.15-2.15.0-79.el9fdp.x86_64
DISTRO=RHEL-9.2.0-20230111.33
How reproducible:
100%
Steps to Reproduce:
# step 1
echo "
interfaces:
- name: ovsbr0
state: up
type: ovs-bridge
" | nmstatectl apply
# step 2
echo "
interfaces:
- name: ovsbr0
state: up
type: ovs-bridge
bridge:
port:
- name: ovs0
" | nmstatectl apply
Actual results:
[2023-01-13T09:14:40Z INFO nmstate::iface] Include interface ovsbr0 to edit as its controller required so
[2023-01-13T09:14:40Z INFO nmstate::iface] Interface ovsbr0 cannot live without controller, marking as absent as it has been detached from its original controller ovsbr0
[2023-01-13T09:14:40Z INFO nmstate::ifaces::inter_ifaces_controller] Creating new OVS internal interface ovs0 to edit as its controller ovsbr0 required so
NmstateError: InvalidArgument: Interface ovs0 cannot be in up state as its parent ovsbr0 has been marked as absent
Expected results:
No failure
Internal port(type: ovs-interface) ovsbr0 is removed, internal port ovs0 is created
Additional info:
Explicitly marking it as absent doesn't work neither:
interfaces:
- name: ovsbr0
state: up
type: ovs-bridge
bridge:
port:
- name: ovs0
- name: ovsbr0
state: absent
type: ovs-interface
- name: ovs0
state: up
type: ovs-interface
But in step 2, if adding a *system* interface without any internal interface, it can work:
interfaces:
- name: ovsbr0
state: up
type: ovs-bridge
bridge:
port:
- name: veth0 # a system interface
Patch posted to upstream: https://github.com/nmstate/nmstate/pull/2203
The key reproducer is replace ovs internal interface of a bridge holding same name ovs interface.
The root cause is nmstate incorrect think newly created ovs internal interface is depending the orphan ovs interface(because they are the same name).
Additional fix for this patch is VLAN over ethernet will not be auto-absent when ethernet been marked as absent, because absent ethernet still exists
in kernel, VLAN can still work. This also apply to veth as nmstate cannot tell whether veth will be delete from kernel or not by absent action.
The reason we do that is because nmstate is supporting VLAN over unmanager interface, hence VLAN should not be impacted by its ethernet parent.
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-2023:2190
Description of problem: In recent version, when there is no any port mentioned, nmstate will automatically create an internal port whose name is same with the ovs bridge. Now this self-created port cannot be easily removed. Version-Release number of selected component (if applicable): Verified with: nmstate-2.2.3-3.el9.x86_64 nispor-1.2.9-1.el9.x86_64 NetworkManager-1.41.7-2.el9.x86_64 openvswitch2.15-2.15.0-79.el9fdp.x86_64 DISTRO=RHEL-9.2.0-20230111.33 How reproducible: 100% Steps to Reproduce: # step 1 echo " interfaces: - name: ovsbr0 state: up type: ovs-bridge " | nmstatectl apply # step 2 echo " interfaces: - name: ovsbr0 state: up type: ovs-bridge bridge: port: - name: ovs0 " | nmstatectl apply Actual results: [2023-01-13T09:14:40Z INFO nmstate::iface] Include interface ovsbr0 to edit as its controller required so [2023-01-13T09:14:40Z INFO nmstate::iface] Interface ovsbr0 cannot live without controller, marking as absent as it has been detached from its original controller ovsbr0 [2023-01-13T09:14:40Z INFO nmstate::ifaces::inter_ifaces_controller] Creating new OVS internal interface ovs0 to edit as its controller ovsbr0 required so NmstateError: InvalidArgument: Interface ovs0 cannot be in up state as its parent ovsbr0 has been marked as absent Expected results: No failure Internal port(type: ovs-interface) ovsbr0 is removed, internal port ovs0 is created Additional info: Explicitly marking it as absent doesn't work neither: interfaces: - name: ovsbr0 state: up type: ovs-bridge bridge: port: - name: ovs0 - name: ovsbr0 state: absent type: ovs-interface - name: ovs0 state: up type: ovs-interface But in step 2, if adding a *system* interface without any internal interface, it can work: interfaces: - name: ovsbr0 state: up type: ovs-bridge bridge: port: - name: veth0 # a system interface