Skip to content

Conversation

@jhadvig
Copy link
Member

@jhadvig jhadvig commented Oct 21, 2025

@yapei creating a testing PR based on our discussion. PTAL

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 21, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 21, 2025

@jhadvig: This pull request references CONSOLE-4666 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

@yapei creating a testing PR based on our discussion. PTAL

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 review from TheRealJon and spadgett October 21, 2025 07:57
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig

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

The pull request process is described here

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 Oct 21, 2025
@yapei
Copy link
Contributor

yapei commented Nov 10, 2025

/retest-required

@yapei
Copy link
Contributor

yapei commented Nov 11, 2025

performed a manual upgrade from OCP 4.19 to 4.21, we can see CRD version v1alpha1 is totally removed

===== at 419
$ oc get clusterversion                                                           
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.19.0-0.nightly-2025-11-07-214657   True        False         49m     Cluster version is 4.19.0-0.nightly-2025-11-07-214657
$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
  "v1",
  "v1alpha1"
]
==== at 420
$ oc get clusterversion                                                                            
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0.nightly-2025-11-07-105814   True        False         132m    Cluster version is 4.20.0-0.nightly-2025-11-07-105814
$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions                                               
[
  "v1"
]
$ oc get crd consoleplugins.console.openshift.io -o json | jq '.spec.versions[] | .name,.storage'
"v1"
true
"v1alpha1"
false

==== at 421
$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2025-11-10-030517-test-ci-ln-5cn1itt-latest   True        False         46m     Cluster version is 4.21.0-0-2025-11-10-030517-test-ci-ln-5cn1itt-latest
$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
  "v1"
]
$ oc get crd consoleplugins.console.openshift.io -o json | jq '.spec.versions[] | .name,.storage'
"v1"
true

/verified by @yapei

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

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

In response to this:

performed a manual upgrade from OCP 4.19 to 4.21, we can see CRD version v1alpha1 is totally removed

===== at 419
$ oc get clusterversion                                                           
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.19.0-0.nightly-2025-11-07-214657   True        False         49m     Cluster version is 4.19.0-0.nightly-2025-11-07-214657
$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
 "v1",
 "v1alpha1"
]
==== at 420
$ oc get clusterversion                                                                            
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0.nightly-2025-11-07-105814   True        False         132m    Cluster version is 4.20.0-0.nightly-2025-11-07-105814
$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions                                               
[
 "v1"
]
$ oc get crd consoleplugins.console.openshift.io -o json | jq '.spec.versions[] | .name,.storage'
"v1"
true
"v1alpha1"
false

==== at 421
$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2025-11-10-030517-test-ci-ln-5cn1itt-latest   True        False         46m     Cluster version is 4.21.0-0-2025-11-10-030517-test-ci-ln-5cn1itt-latest
$ oc get crd consoleplugins.console.openshift.io -o json | jq .status.storedVersions
[
 "v1"
]
$ oc get crd consoleplugins.console.openshift.io -o json | jq '.spec.versions[] | .name,.storage'
"v1"
true

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

@yapei
Copy link
Contributor

yapei commented Nov 11, 2025

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 11, 2025

@jhadvig: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 66e4190 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-console 66e4190 link true /test e2e-aws-console

Full PR test history. Your PR dashboard.

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.

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

Development

Successfully merging this pull request may close these issues.

3 participants