-
Bug
-
Resolution: Done-Errata
-
Major
-
4.12.z
This is a clone of issue OCPBUGS-24356. The following is the description of the original issue:
—
Description of problem:
After updating the cluster to 4.12.42 (from 4.12.15), the customer noticed some issues for the scheduled PODs to start on the node.
The initial thought was a multus issue, and then we realised that the script /usr/local/bin/configure-ovs.sh was modified and reverting the modification fixed the issue.
Modification:
> if nmcli connection show "$vlan_parent" &> /dev/null; then > # if the VLAN connection is configured with a connection UUID as parent, we need to find the underlying device > # and create the bridge against it, as the parent connection can be replaced by another bridge. > vlan_parent=$(nmcli --get-values GENERAL.DEVICES conn show ${vlan_parent}) > fi
Reference:
Version-Release number of selected component (if applicable):
4.12.42
How reproducible:
Should be reproducible by setting inactive nmcli connections with the same names as the active once
Steps to Reproduce:
Not tested, but this should be something like
1. create inactive same nmcli connections
2. run the script
Actual results:
Script failing
Expected results:
Script should manage the connection using the UUID instead of using the Name.
Or maybe it's an underline issue how nmcli is managing the relationship between objects.
Additional info:
The issue may be related to the way that nmcli is working, as it should use the UUID to match the `vlan.parent` as it does with the `connection.master`
- blocks
-
OCPBUGS-33590 [4.14] configure-ovs.sh fails to correctly bring up "br-ex" connection during upgrade of OpenShift from 4.12.15 to 4.12.42
- Closed
- clones
-
OCPBUGS-24356 configure-ovs.sh fails to correctly bring up "br-ex" connection during upgrade of OpenShift from 4.12.15 to 4.12.42
- Closed
- is blocked by
-
OCPBUGS-24356 configure-ovs.sh fails to correctly bring up "br-ex" connection during upgrade of OpenShift from 4.12.15 to 4.12.42
- Closed
- is cloned by
-
OCPBUGS-33590 [4.14] configure-ovs.sh fails to correctly bring up "br-ex" connection during upgrade of OpenShift from 4.12.15 to 4.12.42
- Closed
- links to
-
RHSA-2024:1210 OpenShift Container Platform 4.15.z security update