-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.18.0
-
Moderate
-
No
-
Rejected
-
False
-
-
N/A
-
Release Note Not Required
-
Done
Description of problem: After upgrade a cluster from non-UDN 4.17 image to 4.18 pre-merge EIP+UDN image, "oc wait UserDefinedNetwork/<udn_name> -n <ns> --for condition=NetworkAllocationSucceeded=True" would hang returning no result
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Build a cluster with non-UDN 4.17 nightly image
2. Upgrade the cluster to a 4.18 UDN image (I used a pre-merge image built from openshift/api#1997, openshift/ovn-kubernetes@2333, that has EIP with UDN enabled)
3. Create a new UDN, check if UDN is successfully applied with oc wait UserDefinedNetwork/<udn_name> -n <ns> --for condition=NetworkAllocationSucceeded=True"
Actual results: The command would hang, does not return any value, this only happens to cluster that was upgraded from non-UDN image to UDN image. A freshly created cluster with UDN image directly does not have such a problem.
Expected results: The command should return value to indicate the UDN is applied successfully or not.
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update