Bug 1928141
| Summary: | kube-storage-version-migrator constantly reporting type "Upgradeable" status Unknown | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | gvanderp <gvanderp> | |
| Component: | kube-storage-version-migrator | Assignee: | Luis Sanchez <sanchezl> | |
| Status: | CLOSED ERRATA | QA Contact: | Rahul Gangwar <rgangwar> | |
| Severity: | high | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 4.6 | CC: | aos-bugs, dramseur, rgangwar, rmarwaha, sanchezl, sdodson, sttts, wking | |
| Target Milestone: | --- | Keywords: | ServiceDeliveryImpact | |
| Target Release: | 4.10.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | tag-ci LifecycleReset | |||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1948011 2016176 (view as bug list) | Environment: | ||
| Last Closed: | 2022-03-10 16:02:37 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2016176 | |||
Adding ServiceDeliveryImpact as this is blurring the view for the ARO team [1] was my attempt to have library-go-based operators who don't care default to Upgradeable=True, but it rotted out to lack of interest. I'm happy to revive if there is renewed interest. [1]: https://github.com/openshift/library-go/pull/802 Trevor, I think reviving might be good call I've revived my library-go PR [1]. Anyone who knows how to get library-go maintainer interest, please pull those levers ;). [1]: https://github.com/openshift/library-go/pull/802#issuecomment-782575095 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. The bug is still active and needs to be resolved. Thanks The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified. 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. This bug is now linked as an exception for origin's guards against other operators behaving similarly [1]. We need to fix the operator so we can drop the exception. [1]: https://github.com/openshift/origin/commit/82542badb16304f3929148304c7a7b4aa6100ad1#diff-b5009437f29876beb3655b1886c06987adca1c8dde9f81cfa7d81716fd4966bbR222 The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified. 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. Still a bug: $ w3m -dump -cols 200 'https://search.ci.openshift.org/search?maxAge=48h&type=junit&context=0&search=clusteroperator/kube-storage-version-migrator.*Upgradeable' | jq -r 'to_entries[].value | to_entries[].value[].context[]' | grep -c '"status":"Unknown","type":"Upgradeable"' 74 Whenever you're tired of this being a bug, feel free to drop the exception mentioned in comment 10, which will break e2e until this gets fixed ;) The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified. The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified. 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. Please assign someone to look into this issue. Thanks! The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified. Still get status unknown
oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.10.0-0.nightly-2021-09-21-181111 True False 5h42m Cluster version is 4.10.0-0.nightly-2021-09-21-181111
oc describe co/kube-storage-version-migrator | grep -B 3 Upgradeable
Last Transition Time: 2021-09-22T03:56:03Z
Reason: NoData
Status: Unknown
Type: Upgradeable
@sanchezl - Please provide an update. This item failed QA. oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.10.0-0.nightly-2021-10-20-193037 True False 7m Cluster version is 4.10.0-0.nightly-2021-10-20-193037
oc get clusteroperators | grep kube-storage
kube-storage-version-migrator 4.10.0-0.nightly-2021-10-20-193037 True False False 22m
oc describe co/kube-storage-version-migrator | grep -B 3 Upgradeable
Message: All is well
Reason: AsExpected
Status: True
Type: Upgradeable
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056 |
Description of problem: We observe that kube-storage-version-migrator is constantly reporting Upgradeable type, Unknown status Version-Release number of selected component (if applicable): Observed in 4.6.15, probably present before How reproducible: 100% of observed cases Steps to Reproduce: 1. Create an OCP cluster 2. describe cluster operator kube-storage-version-migrator Actual results: oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.15 True False 20m Cluster version is 4.6.15 oc get clusteroperators | grep kube-storage kube-storage-version-migrator 4.6.15 True False False 10m oc describe co/kube-storage-version-migrator | grep -B 3 Upgradeable Last Transition Time: 2021-02-12T12:14:01Z Reason: NoData Status: Unknown Type: Upgradeable Expected results: This cluster operator should be reported Upgradeable True (most of the time), False in case of problem but not Unknown Additional info: