-
Bug
-
Resolution: Unresolved
-
Normal
-
4.20.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
when installing TNF the command wait-for-install-complete falsely returns 0 even though some operators are still progressing (for the next 10-20 mins) the reason for that is these operators actually gets marked as available and not progressing but then flips back one or two times to progressing true the mainly affected operators (with an example output) image-registry, openshift-apiserver, kube-apiserver NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE authentication 4.20.0-0.nightly-2025-10-14-200816 True False False 4m39s baremetal 4.20.0-0.nightly-2025-10-14-200816 True False False 17m cloud-controller-manager 4.20.0-0.nightly-2025-10-14-200816 True False False 19m cloud-credential 4.20.0-0.nightly-2025-10-14-200816 True False False 28m cluster-api 4.20.0-0.nightly-2025-10-14-200816 True False False 17m cluster-autoscaler 4.20.0-0.nightly-2025-10-14-200816 True False False 17m config-operator 4.20.0-0.nightly-2025-10-14-200816 True False False 18m console 4.20.0-0.nightly-2025-10-14-200816 True False False 6m19s control-plane-machine-set 4.20.0-0.nightly-2025-10-14-200816 True False False 17m csi-snapshot-controller 4.20.0-0.nightly-2025-10-14-200816 True False False 17m dns 4.20.0-0.nightly-2025-10-14-200816 True False False 17m etcd 4.20.0-0.nightly-2025-10-14-200816 True False False 5m36s image-registry 4.20.0-0.nightly-2025-10-14-200816 True True False 13s Progressing: The deployment has not completed... ingress 4.20.0-0.nightly-2025-10-14-200816 True False False 8m17s insights 4.20.0-0.nightly-2025-10-14-200816 True False False 17m kube-apiserver 4.20.0-0.nightly-2025-10-14-200816 True True False 11m NodeInstallerProgressing: 2 nodes are at revision 4; 0 nodes have achieved new revision 5 kube-controller-manager 4.20.0-0.nightly-2025-10-14-200816 True False False 12m kube-scheduler 4.20.0-0.nightly-2025-10-14-200816 True False False 15m kube-storage-version-migrator 4.20.0-0.nightly-2025-10-14-200816 True False False 18m machine-api 4.20.0-0.nightly-2025-10-14-200816 True False False 13m machine-approver 4.20.0-0.nightly-2025-10-14-200816 True False False 17m machine-config 4.20.0-0.nightly-2025-10-14-200816 True False False 15m marketplace 4.20.0-0.nightly-2025-10-14-200816 True False False 17m monitoring 4.20.0-0.nightly-2025-10-14-200816 True False False 3m24s network 4.20.0-0.nightly-2025-10-14-200816 True False False 18m node-tuning 4.20.0-0.nightly-2025-10-14-200816 True False False 17m olm 4.20.0-0.nightly-2025-10-14-200816 True False False 17m openshift-apiserver 4.20.0-0.nightly-2025-10-14-200816 True True False 9m11s APIServerDeploymentProgressing: deployment/apiserver.openshift-apiserver: 1/2 pods have been updated to the latest generation and 1/2 pods are available openshift-controller-manager 4.20.0-0.nightly-2025-10-14-200816 True False False 7m11s openshift-samples 4.20.0-0.nightly-2025-10-14-200816 True False False 8m44s operator-lifecycle-manager 4.20.0-0.nightly-2025-10-14-200816 True False False 17m operator-lifecycle-manager-catalog 4.20.0-0.nightly-2025-10-14-200816 True False False 17m operator-lifecycle-manager-packageserver 4.20.0-0.nightly-2025-10-14-200816 True False False 9m11s service-ca 4.20.0-0.nightly-2025-10-14-200816 True False False 18m storage 4.20.0-0.nightly-2025-10-14-200816 True False False 17m
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.install a fresh TNF cluster
2.wait for insall-complete
3.watch "oc get co"
Actual results:
co are still progressing
Expected results:
none should be progressing
Additional info:
