Skip to content

NO-ISSUE: co/kube-storage-version-migrator reports Available=False in a non-upgrade job#30740

Open
hongkailiu wants to merge 1 commit intoopenshift:release-4.21from
hongkailiu:cp-3f541bc00bd138ea4fc9675c6bf4d22882260bf0
Open

NO-ISSUE: co/kube-storage-version-migrator reports Available=False in a non-upgrade job#30740
hongkailiu wants to merge 1 commit intoopenshift:release-4.21from
hongkailiu:cp-3f541bc00bd138ea4fc9675c6bf4d22882260bf0

Conversation

@hongkailiu
Copy link
Member

This one picks up 3f541bc

It impacts 4.21 component readiness. This exception will give the component team some air to bring its fix.

co/console seems alright on Sippy and thus 37d20ef was left there.

/cc @dgoodwin @sanchezl

@openshift-ci-robot
Copy link

@hongkailiu: This pull request explicitly references no jira issue.

Details

In response to this:

This one picks up 3f541bc

It impacts 4.21 component readiness. This exception will give the component team some air to bring its fix.

co/console seems alright on Sippy and thus 37d20ef was left there.

/cc @dgoodwin @sanchezl

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 30, 2026
@openshift-ci openshift-ci bot requested review from dgoodwin and sanchezl January 30, 2026 04:21
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2026

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

@dgoodwin
Copy link
Contributor

/lgtm
/label backport-risk-assessed

@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 Jan 30, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, hongkailiu

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 30, 2026
@hongkailiu
Copy link
Member Author

It is a backport for a reception on a test case. The risk should be low enough.

/verify by @hongkailiu

@hongkailiu
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link

@hongkailiu: This pull request explicitly references no jira issue.

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.

@hongkailiu
Copy link
Member Author

/verified by @hongkailiu

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 1, 2026
@openshift-ci-robot
Copy link

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

Details

In response to this:

/verified by @hongkailiu

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