-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.13, 4.11
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
None
-
CCXDEV Sprint 88
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The insight operator will revert automaticlly even if spec.overrides.unmanaged = true is added in the clusterVersion
Version-Release number of selected component (if applicable):
4.11.38 4.13.0-0.nightly-2023-04-21-084440
How reproducible:
Always
Steps to Reproduce:
1.Use command to make sure insight operator is un-manage by CVO
$ oc patch clusterversion version --type=json -p \[\{\"op\":\ \"add\",\ \"path\":\ \"/spec/overrides\",\ \"value\":\ \[\{\"kind\":\ \"Deployment\",\ \"name\":\ \"insights-operator\",\ \"namespace\":\ \"openshift-insights\",\ \"unmanaged\":\ true,\ \"group\":\ \"apps/v1\"\}\]\}\]
2.Login OCP, and navigate to insights-operator deployment details page
/k8s/ns/openshift-insights/deployments/insights-operator/
3. Decrease the Pod count , make sure 0 pod is availiable for the insight-operator
4. Wait for a momnet (3-5mins), check if the pod for the operator will be re-created automatically
Actual results:
The pod will be recreated for the insights-operator even if it is unmanage by the CVO, but the revert progress will be triggred which is incorrect
Expected results:
If the insight-operator no longer managed by CVO, the correct status should be shown to the users, the revert status should not triggered automatically
Additional info:
Use below code, and make sure the Clusterversion file did not be rewitten during the upon steps, which means the revert is not trigger by CVO $ while true; do oc get clusterversion version -o json | jq .spec; oc get insightsoperators.operator.openshift.io cluster -o json | jq .spec.managementState; sleep 5; done