-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.15.z
-
Moderate
-
Yes
-
Rejected
-
False
-
-
N/A
-
Release Note Not Required
-
In Progress
-
Customer Reported
-
Red Hat OpenShift Container Platform
-
-
-
07/22 cu closed the support case; was happy w/workaround. But, the network operator has to stay unmanaged for it to work. Will try to contact the TAM.
-
-
Description of problem:
When upgrading a 4.15.18 cluster to 4.15.19 the Cluster network operator was stuck on the previous version. Cluster is still using Openshift SDN
Version-Release number of selected component (if applicable):
4.15.18 -> 4.15.19
How reproducible:
I have not reproduced.
Steps to Reproduce:
1. Upgrade OpenshiftSDN Cluster from 4.15.18 to 4.15.19
Actual results:
NO never got into progressing state (from oc get co) while dropping the ConnectivityCheckController is waiting for transition to desired vesion (4.15.19) to be completed. Logs can be found in customer case 03877495. I cannot attach files for some reason ;)
Expected results:
NO to update its version
Additional info:
VMWare cluster
Problem resolved by
$ oc patch network.operator.openshift.io cluster --patch '{"spec": {"managementState": "Unmanaged"}}' $ oc annotate daemonset whereabouts-reconciler release.openshift.io/version=4.15.19 -n openshift-multus as in KCS https://access.redhat.com/solutions/7024726
- clones
-
-
- Closed
-
