Bug 1980557

Summary: kube-storage-version-migrator reports "all is well" while unavailable
Product: OpenShift Container Platform Reporter: Ben Parees <bparees>
Component: kube-storage-version-migratorAssignee: Luis Sanchez <sanchezl>
Status: CLOSED DUPLICATE QA Contact: Ke Wang <kewang>
Severity: unspecified Docs Contact:
Priority: low    
Version: 4.8CC: aos-bugs, sanchezl
Target Milestone: ---Flags: mfojtik: needinfo?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: LifecycleFrozen
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-07 15:29:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben Parees 2021-07-08 20:47:45 UTC
Description of problem:
In this CI run we see that the job failed because the kube-storage-version-migrator did not become available again:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-disruptive-4.8/1412175886651756544

fail [github.com/openshift/origin/test/extended/dr/quorum_restore.go:296]: Jul  6 00:29:44.297: Some cluster operators never became available /kube-storage-version-migrator

but if we look at the clusteroperator status dump from the time the test failed, we see that the "available" condition is set to false, while the message is "all is well".  Those two things seem incompatible w/ each other:


Jul  6 00:29:44.297: INFO: ClusterOperators:
NAMESPACE NAME                     PROGRESSING AVAILABLE VERSION MESSAGE
          authentication           False       True              All is well
          baremetal                False       True              
          cloud-controller-manager False       True              
          cloud-credential         False       True              
          cluster-autoscaler       False       True              
          config-operator          False       True              All is well
          console                  False       True              All is well
          csi-snapshot-controller  False       True              All is well
          dns                      False       True              
          etcd                     False       True              NodeControllerDegraded: All master nodes are ready
EtcdMembersDegraded: No unhealthy members found
 image-registry                           False True   
 ingress                                  False True   The "default" ingress controller reports Degraded=False.
 insights                                 False True   
 kube-apiserver                           False True   NodeControllerDegraded: All master nodes are ready
 kube-controller-manager                  False True   NodeControllerDegraded: All master nodes are ready
 kube-scheduler                           False True   NodeControllerDegraded: All master nodes are ready
 kube-storage-version-migrator            False False  All is well
 machine-api                              False True   
 machine-approver                         False True   
 machine-config                           False True   
 marketplace                              False True   Available release version: 4.8.0-0.ci-2021-06-14-090014
 monitoring                               False True   
 network                                  False True   
 node-tuning                              False True   DaemonSet "tuned" available
 openshift-apiserver                      False True   All is well
 openshift-controller-manager             False True   All is well
 openshift-samples                        False True   
 operator-lifecycle-manager               False True   
 operator-lifecycle-manager-catalog       False True   
 operator-lifecycle-manager-packageserver False True   
 service-ca                               False True   All is well
 storage                                  False True   AWSEBSCSIDriverOperatorCRDegraded: All is well




Version-Release number of selected component (if applicable):
4.8.0-0.ci-2021-06-14-090014

How reproducible:
unknown

Actual results:
operator is unavailable but message implies everything is fine


Expected results:
when operators are unavailable, their message should indicate why not

Comment 1 Michal Fojtik 2021-08-07 20:53:19 UTC
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 2 Ben Parees 2021-08-07 21:45:55 UTC
> The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

i have no reason to think it's been resolved, and i still think it should be fixed.  removing lifecycle stale.

Comment 3 Michal Fojtik 2021-09-06 22:45:22 UTC
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 4 Luis Sanchez 2022-01-07 15:29:27 UTC

*** This bug has been marked as a duplicate of bug 2022844 ***