Skip to content

[release-4.20] OCPBUGS-69960: Reset StorageVersionMigrationDegraded condition #1085

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
openshift-cherrypick-robot wants to merge 1 commit into
base: release-4.20
Choose a base branch
from
Open

[release-4.20] OCPBUGS-69960: Reset StorageVersionMigrationDegraded condition #1085

openshift-cherrypick-robot wants to merge 1 commit into from

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Dec 19, 2025

This is an automated cherry-pick of #1071

/assign Leo6Leo

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Dec 19, 2025
Merged
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 19, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-65880 has been cloned as Jira Issue OCPBUGS-69960. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-69960: Reset StorageVersionMigrationDegraded condition

Details

In response to this:

This is an automated cherry-pick of #1071

/assign Leo6Leo

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.20] OCPBUGS-65880: Reset StorageVersionMigrationDegraded condition [release-4.20] OCPBUGS-69960: Reset StorageVersionMigrationDegraded condition Dec 19, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Dec 19, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 19, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-69960, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-65880 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #1071

/assign Leo6Leo

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 19, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 19, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign therealjon for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 19, 2025

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@yapei
Copy link
Contributor

yapei commented Dec 22, 2025

confirmed StorageVersionMigrationDegraded condition can be re-sync and reset

=== initial status 
oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         6m59s   Cluster version is 4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest

oc get co console
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         False      13m

oc get consoles.operator.openshift.io cluster -o json | jq '.status.conditions[] | select(.type == "StorageVersionMigrationDegraded")'
{
  "lastTransitionTime": "2025-12-22T02:12:24Z",
  "status": "False",
  "type": "StorageVersionMigrationDegraded"
}


=== update `StorageVersionMigrationDegraded` status
$ oc edit consoles.operator.openshift.io cluster --subresource=status
console.operator.openshift.io/cluster edited

$ oc get consoles.operator.openshift.io cluster -o json | jq '.status.conditions[] | select(.type == "StorageVersionMigrationDegraded")'
{
  "lastTransitionTime": "2025-12-22T02:10:24Z",
  "message": "rpc error: code = Unavailable desc = error reading from server",
  "reason": "FailedCheckCRDStoredVersions",
  "status": "True",
  "type": "StorageVersionMigrationDegraded"
}

=== monitor co/console status
while true; do oc get co console; sleep 60; done
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       16m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       17m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       18m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       19m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       20m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       21m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       22m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       23m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       24m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         False      25m
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         False      26m
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         False      27m

/verified by @yapei

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 22, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 22, 2025

@yapei: This PR has been marked as verified by @yapei.

Details

In response to this:

confirmed StorageVersionMigrationDegraded condition can be re-sync and reset

=== initial status 
oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         6m59s   Cluster version is 4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest

oc get co console
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         False      13m

oc get consoles.operator.openshift.io cluster -o json | jq '.status.conditions[] | select(.type == "StorageVersionMigrationDegraded")'
{
 "lastTransitionTime": "2025-12-22T02:12:24Z",
 "status": "False",
 "type": "StorageVersionMigrationDegraded"
}


=== update `StorageVersionMigrationDegraded` status
$ oc edit consoles.operator.openshift.io cluster --subresource=status
console.operator.openshift.io/cluster edited

$ oc get consoles.operator.openshift.io cluster -o json | jq '.status.conditions[] | select(.type == "StorageVersionMigrationDegraded")'
{
 "lastTransitionTime": "2025-12-22T02:10:24Z",
 "message": "rpc error: code = Unavailable desc = error reading from server",
 "reason": "FailedCheckCRDStoredVersions",
 "status": "True",
 "type": "StorageVersionMigrationDegraded"
}

=== monitor co/console status
while true; do oc get co console; sleep 60; done
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       16m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       17m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       18m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       19m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       20m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       21m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       22m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       23m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         True       24m     StorageVersionMigrationDegraded: rpc error: code = Unavailable desc = error reading from server
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         False      25m
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         False      26m
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console   4.20.0-0-2025-12-22-014934-test-ci-ln-gd60tqk-latest   True        False         False      27m

/verified by @yapei

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@jhadvig
Copy link
Member

jhadvig commented Dec 22, 2025

/approved
/label backport-risk-assessed
/jira refresh

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 22, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 22, 2025

@jhadvig: This pull request references Jira Issue OCPBUGS-69960, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-65880 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/approved
/label backport-risk-assessed
/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@Leo6Leo
Copy link
Contributor

Leo6Leo commented Dec 22, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 22, 2025

@Leo6Leo: This pull request references Jira Issue OCPBUGS-69960, which is invalid:

  • expected dependent Jira Issue OCPBUGS-65880 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@spadgett spadgett Awaiting requested review from spadgett

@TheRealJon TheRealJon Awaiting requested review from TheRealJon

Assignees

@yanpzhan yanpzhan

@sanketpathak sanketpathak

@yapei yapei

@Leo6Leo Leo6Leo

Labels

backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@openshift-cherrypick-robot @openshift-ci-robot @yapei @jhadvig @Leo6Leo @yanpzhan @sanketpathak