[4.22] OCPBUGS-91947: maxOpenShiftVersion should be bumped to 5.0

[dobsonj]

https://redhat.atlassian.net/browse/OCPBUGS-91947

This PR allows setting MAX_OCP_VERSION as an environment variable for releases where the default x.y+1 max version is incorrect and pins the release-4.22 branch MAX_OCP_VERSION to 5.0.

• hack/update-metadata.sh: allow MAX_OCP_VERSION override
• Makefile: pin MAX_OCP_VERSION to 5.0

/cc @openshift/storage

[openshift-ci-robot]

@dobsonj: This pull request references Jira Issue OCPBUGS-90151, which is invalid:

• expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "5.0" instead
• 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 Jira Issue OCPBUGS-90151 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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 PR allows setting MAX_OCP_VERSION as an environment variable for releases where the default x.y+1 max version is incorrect and pins the release-4.22 branch MAX_OCP_VERSION to 5.0.

• hack/update-metadata.sh: allow MAX_OCP_VERSION override
• Makefile: pin MAX_OCP_VERSION to 5.0

/cc @openshift/storage

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: fa3e803f-ae7e-4d3b-a198-a3f3ba70c1ce

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

@dobsonj: GitHub didn't allow me to request PR reviews from the following users: openshift/storage.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

This PR allows setting MAX_OCP_VERSION as an environment variable for releases where the default x.y+1 max version is incorrect and pins the release-4.22 branch MAX_OCP_VERSION to 5.0.

• hack/update-metadata.sh: allow MAX_OCP_VERSION override
• Makefile: pin MAX_OCP_VERSION to 5.0

/cc @openshift/storage

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.

[dobsonj]

/jira cherry-pick OCPBUGS-90151

[openshift-ci-robot]

@dobsonj: Jira Issue OCPBUGS-90151 has been cloned as Jira Issue OCPBUGS-91947. Will retitle bug to link to clone.
/retitle OCPBUGS-91947: [4.22] OCPBUGS-90151: maxOpenShiftVersion should be bumped to 5.0

Details

In response to this:

/jira cherry-pick OCPBUGS-90151

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]

@dobsonj: This pull request references Jira Issue OCPBUGS-91947, 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-90151 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead
• expected dependent Jira Issue OCPBUGS-90151 to target a version in 5.0.0, but it targets "5.0" 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 PR allows setting MAX_OCP_VERSION as an environment variable for releases where the default x.y+1 max version is incorrect and pins the release-4.22 branch MAX_OCP_VERSION to 5.0.

• hack/update-metadata.sh: allow MAX_OCP_VERSION override
• Makefile: pin MAX_OCP_VERSION to 5.0

/cc @openshift/storage

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]

@dobsonj: This pull request references Jira Issue OCPBUGS-91947, 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-90151 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST 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:

https://redhat.atlassian.net/browse/OCPBUGS-91947

This PR allows setting MAX_OCP_VERSION as an environment variable for releases where the default x.y+1 max version is incorrect and pins the release-4.22 branch MAX_OCP_VERSION to 5.0.

• hack/update-metadata.sh: allow MAX_OCP_VERSION override
• Makefile: pin MAX_OCP_VERSION to 5.0

/cc @openshift/storage

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]

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

[dobsonj]

/verified by @dobsonj

[openshift-ci-robot]

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

Details

In response to this:

/verified by @dobsonj

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.

[jsafrane]

/lgtm
/approve
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dobsonj, jsafrane

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:

• OWNERS [dobsonj,jsafrane]

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

[dobsonj]

/jira refresh

[openshift-ci-robot]

@dobsonj: This pull request references Jira Issue OCPBUGS-91947, which is invalid:

• expected dependent Jira Issue OCPBUGS-90151 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST 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.

[dobsonj]

/jira refresh

[openshift-ci-robot]

@dobsonj: This pull request references Jira Issue OCPBUGS-91947, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-90151 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-90151 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
• bug has dependents

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-robot]

@dobsonj: Jira Issue OCPBUGS-91947: Some pull requests linked via external trackers have merged:

• openshift/local-storage-operator#636

The following pull request, linked via external tracker, has not merged:

• openshift/csi-operator#572 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-91947 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the PRs merge.

Details

In response to this:

https://redhat.atlassian.net/browse/OCPBUGS-91947

This PR allows setting MAX_OCP_VERSION as an environment variable for releases where the default x.y+1 max version is incorrect and pins the release-4.22 branch MAX_OCP_VERSION to 5.0.

• hack/update-metadata.sh: allow MAX_OCP_VERSION override
• Makefile: pin MAX_OCP_VERSION to 5.0

/cc @openshift/storage

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.