-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.7
-
NetworkManager-1.53.3-1.el10
-
No
-
Moderate
-
1
-
rhel-net-mgmt
-
ssg_networking
-
3
-
False
-
False
-
-
None
-
NMT SST - 2025Q2
-
Definition of Done:
Please mark each item below with ( / ) if completed or ( x ) if incomplete:
The acceptance criteria defined below are met.Given a system administrator using nmcli to configure OVS,
When they specify port-type after master in nmcli connection add,
Then NetworkManager should still process the command successfully and not reject it due to argument order.
Definition of Done:
- The implementation meets the acceptance criteria
- Integration tests are written and pass
- The code is part of a downstream build attached to an errata
Code changes are included in a downstream build attached to an errata.
All required testing (manual and/or automated) passes successfully.
( ) Related documentation updates (if applicable) have been completed.
Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: The acceptance criteria defined below are met. Given a system administrator using nmcli to configure OVS, When they specify port-type after master in nmcli connection add, Then NetworkManager should still process the command successfully and not reject it due to argument order. Definition of Done: The implementation meets the acceptance criteria Integration tests are written and pass The code is part of a downstream build attached to an errata Code changes are included in a downstream build attached to an errata. All required testing (manual and/or automated) passes successfully. ( ) Related documentation updates (if applicable) have been completed. -
Pass
-
Automated
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
When the OVS interface connection `ovs-if-br-ex` has been created/persisted earlier or left from a previous configuration,
specifying the port type when adding ovs-port in the configure-ovs.sh will not necessitate the OVS port connection being added successfully.
What is the impact of this issue to you?
I got confirmation from OCP team that the fix for specifying the interface type when adding ovs-port https://github.com/openshift/machine-config-operator/pull/4761/commits/2b16d22e5066b8ad2ec78e9ce2ced7dacf8f8ee1 can not address the situation that ovs-configuration failed to start after reboot, https://issues.redhat.com/browse/OCPBUGS-41489 .
Please provide the package NVR for which the bug is seen:
always
Steps to reproduce
1. nmcli connection add type ovs-interface con-name ovs-if-br-ex ifname br-ex master ovs-port-phys0 connection.autoconnect no
2. nmcli connection add type ovs-bridge con-name br-ex ifname br-ex 802-3-ethernet.mtu 1500 connection.autoconnect-slaves 1 connection.autoconnect no
3. nmcli connection add type ovs-port con-name ovs-port-phys0 ifname port1 master br-ex connection.autoconnect-slaves 1 connection.autoconnect no port-type ovs-bridge
Expected results
The OVS port connection `ovs-port-phys0` is added successfully.
Actual results
The following error message is raised:
"Error: failed to modify connection.port-type: 'ovs-interface' not among [bond, bridge, ovs-bridge, ovs-port, team, vrf]."
Notice that if specifying the `port-type` before `master` (using the command below), the OVS port connection `ovs-port-phys0` is added successfully.
3. nmcli connection add type ovs-port con-name ovs-port-phys0 ifname port1 port-type ovs-bridge master br-ex connection.autoconnect-slaves 1 connection.autoconnect no
- is cloned by
-
-
- Closed
-
- links to
-
RHBA-2025:146815
NetworkManager bug fix and enhancement update