Skip to content

OCPBUGS-60687: PowerVS: Add lon04 support#9905

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
hamzy:PowerVS-Add-lon04-support
Aug 27, 2025
Merged

OCPBUGS-60687: PowerVS: Add lon04 support#9905
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
hamzy:PowerVS-Add-lon04-support

Conversation

@hamzy
Copy link
Copy Markdown
Contributor

@hamzy hamzy commented Aug 20, 2025

Add the zone lon4 to the PowerVS installer.

Add the zone lon4 to the PowerVS installer.
@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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 20, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hamzy: This pull request references Jira Issue OCPBUGS-60687, which is invalid:

  • expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21" 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:

Add the zone lon4 to the PowerVS installer.

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.

@hamzy
Copy link
Copy Markdown
Contributor Author

hamzy commented Aug 20, 2025

/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 Aug 20, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
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.

@hamzy
Copy link
Copy Markdown
Contributor Author

hamzy commented Aug 20, 2025

/test e2e-aws-ovn

@mjturek
Copy link
Copy Markdown
Contributor

mjturek commented Aug 20, 2025

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 20, 2025
@hamzy
Copy link
Copy Markdown
Contributor Author

hamzy commented Aug 21, 2025

/test e2e-aws-ovn

Copy link
Copy Markdown
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tthvo

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 Aug 25, 2025
@hamzy
Copy link
Copy Markdown
Contributor Author

hamzy commented Aug 25, 2025

/test e2e-aws-ovn

@hamzy
Copy link
Copy Markdown
Contributor Author

hamzy commented Aug 25, 2025

@sadasu Can you please add the acknowledge-critical-fixes-only label?

@hamzy
Copy link
Copy Markdown
Contributor Author

hamzy commented Aug 25, 2025

/assign @sadasu

@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 Aug 26, 2025
@sadasu
Copy link
Copy Markdown
Contributor

sadasu commented Aug 26, 2025

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci Bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Aug 26, 2025
@tthvo
Copy link
Copy Markdown
Member

tthvo commented Aug 26, 2025

/retest-required

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 27, 2025

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

@openshift-merge-bot openshift-merge-bot Bot merged commit 26d807e into openshift:main Aug 27, 2025
18 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hamzy: Jira Issue OCPBUGS-60687: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Add the zone lon4 to the PowerVS installer.

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.

@AshwinHIBM
Copy link
Copy Markdown
Contributor

/cherry-pick release-4.19

@openshift-cherrypick-robot
Copy link
Copy Markdown

@AshwinHIBM: new pull request created: #10540

Details

In response to this:

/cherry-pick release-4.19

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.

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

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants