Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #1071

/assign Leo6Leo

@openshift-ci-robot
Copy link
Contributor

@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-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
@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

@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

@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

@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.

@sdodson
Copy link
Member

sdodson commented Jan 6, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 6, 2026
@openshift-ci-robot
Copy link
Contributor

@sdodson: This pull request references Jira Issue OCPBUGS-69960, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-65880 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-65880 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @yapei

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.

@openshift-ci openshift-ci bot requested a review from yapei January 6, 2026 14:31
@sdodson sdodson added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 6, 2026
@sdodson
Copy link
Member

sdodson commented Jan 6, 2026

@Leo6Leo @jhadvig Can we get lgtm added to this please if it's OK to move forward? It seems like JIRA automation failed to move the upstream bug to verified and I've gone ahead and done that based on QE marking the PR verified.

@sdodson
Copy link
Member

sdodson commented Jan 6, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 6, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-cherrypick-robot, sdodson

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

The pull request process is described 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

@sdodson
Copy link
Member

sdodson commented Jan 6, 2026

/override ci/prow/e2e-aws-console ci/prow/e2e-aws-operator ci/prow/e2e-azure-ovn-upgrade ci/prow/e2e-gcp-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 6, 2026

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-console, ci/prow/e2e-aws-operator, ci/prow/e2e-azure-ovn-upgrade, ci/prow/e2e-gcp-ovn

Details

In response to this:

/override ci/prow/e2e-aws-console ci/prow/e2e-aws-operator ci/prow/e2e-azure-ovn-upgrade ci/prow/e2e-gcp-ovn

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.

@sdodson sdodson merged commit ac81d03 into openshift:release-4.20 Jan 6, 2026
9 of 10 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-69960
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-69960 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants