-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.15
-
None
-
No
-
False
-
Description of problem:
When upgrading from 4.15.0-0.nightly-2023-12-07-041003 to 4.15.0-0.nightly-2023-12-07-225558, wait 10 minutes, the Completion and Available in Operator Status is not correct.
Version-Release number of selected component (if applicable):
4.15
How reproducible:
Always.
Steps to Reproduce:
1. Upgrade from 4.15.0-0.nightly-2023-12-07-041003 to 4.15.0-0.nightly-2023-12-07-225558 2. Wait 10 minutes when there is operator is progressing 3. Run *oc adm upgrade status* to check control plane status
Actual results:
[root@preserve-yangyangmerrn-1 415]# ./oc get clusteroperator | grep -E 'True\s+True' network 4.15.0-0.nightly-2023-12-07-041003 True True False 103m DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... [root@preserve-yangyangmerrn-1 415]# ./oc adm upgrade status An update is in progress for 16m10s: Working towards 4.15.0-0.nightly-2023-12-07-225558: 722 of 873 done (82% complete), waiting on network = Control Plane = Assessment: Progressing Completion: 94% Duration: 16m9.774276344s Operator Status: 33 Total, 33 Available, 1 Progressing, 0 Degraded [root@preserve-yangyangmerrn-1 415]#
Expected results:
Completion should not so large, it should be able reflect the finished percentage. Available should be 32 since there is one operator in progressing. Available + Progressing + Degraded should equal to Totle
Additional info: