Skip to content

OCPNODE-1619: Bump 4.13 minor_min to 4.12.15#3531

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
petr-muller:ocpnode-1619-bump-min-4.13-to-4.12.15
Apr 27, 2023
Merged

OCPNODE-1619: Bump 4.13 minor_min to 4.12.15#3531
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
petr-muller:ocpnode-1619-bump-min-4.13-to-4.12.15

Conversation

@petr-muller
Copy link
Copy Markdown
Member

Avoid OCPBUGS-11409:

The minimally viable upgrade path to 4.13 would have to be 4.12.15 or later.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 24, 2023
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 24, 2023

@petr-muller: This pull request references OCPNODE-1619 which is a valid jira issue.

Details

In response to this:

Avoid OCPBUGS-11409:

The minimally viable upgrade path to 4.13 would have to be 4.12.15 or later.

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/test-infra repository.

@openshift-ci openshift-ci Bot requested review from PratikMahajan and wking April 24, 2023 19:19
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 24, 2023
@petr-muller
Copy link
Copy Markdown
Member Author

/hold

...but 4.12.15 is not a thing yet :P

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 24, 2023
Copy link
Copy Markdown
Member

@wking wking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4.12.15 includes openshift/kubernetes#1478 for OCPBUGS-7589. I'm a bit fuzzy on the relationship between OCPBUGS-7589 and OCPBUGS-11409, but I'll pull the hold, and we can always follow up with later changes if I'm misunderstanding:

/hold cancel
/lgtm

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 27, 2023
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 27, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller, wking

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 2023

@petr-muller: 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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 9f72682 into openshift:master Apr 27, 2023
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants