Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[release-4.14] OCPBUGS-42285: Add AWS r8g to arm tested instance types #9050

Merged
merged 1 commit into from
Oct 12, 2024
Merged

[release-4.14] OCPBUGS-42285: Add AWS r8g to arm tested instance types #9050

merged 1 commit into from
Oct 12, 2024

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #9040

/assign lwan-wanglin

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Sep 23, 2024
Merged
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-42180 has been cloned as Jira Issue OCPBUGS-42285. Will retitle bug to link to clone.
/retitle [release-4.14] OCPBUGS-42285: Add AWS r8g to arm tested instance types

In response to this:

This is an automated cherry-pick of #9040

/assign lwan-wanglin

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 changed the title [release-4.14] OCPBUGS-42180: Add AWS r8g to arm tested instance types [release-4.14] OCPBUGS-42285: Add AWS r8g to arm tested instance types Sep 23, 2024
@openshift-ci-robot openshift-ci-robot added 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 Sep 23, 2024
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-42285, which is invalid:

  • expected dependent Jira Issue OCPBUGS-42180 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

In response to this:

This is an automated cherry-pick of #9040

/assign lwan-wanglin

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.

@lwan-wanglin
Copy link
Contributor

@r4f4 @patrickdillon PTAL,thanks!

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Sep 23, 2024

@openshift-cherrypick-robot: 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/e2e-aws-ovn-shared-vpc-localzones 397aa9b link false /test e2e-aws-ovn-shared-vpc-localzones
ci/prow/okd-scos-e2e-aws-upgrade 397aa9b link false /test okd-scos-e2e-aws-upgrade
ci/prow/e2e-vsphere-static-ovn 397aa9b link false /test e2e-vsphere-static-ovn
ci/prow/e2e-aws-ovn-localzones 397aa9b link false /test e2e-aws-ovn-localzones
ci/prow/e2e-azure-ovn-resourcegroup 397aa9b link false /test e2e-azure-ovn-resourcegroup
ci/prow/okd-e2e-aws-ovn-upgrade 397aa9b link false /test okd-e2e-aws-ovn-upgrade

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.

r4f4
r4f4 reviewed Sep 23, 2024
View reviewed changes
Copy link
Contributor

@r4f4 r4f4 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 OpenShift CI
Copy link
Contributor

openshift-ci bot commented Sep 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: r4f4

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 Sep 23, 2024
@lwan-wanglin
Copy link
Contributor

@sadasu could you help to add backport-risk-assessed label for the pr? the customer want it to land in OCP 4.14 doc, thanks!

@sadasu
Copy link
Contributor

sadasu commented Oct 11, 2024

/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 Oct 11, 2024
@sadasu
Copy link
Contributor

sadasu commented Oct 11, 2024

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Oct 11, 2024

/jira-refresh

@sadasu
Copy link
Contributor

sadasu commented Oct 11, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 11, 2024
@gpei
Copy link
Contributor

gpei commented Oct 12, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 12, 2024
@lwan-wanglin
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: This pull request references Jira Issue OCPBUGS-42285, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Won't Do) 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.

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.

@lwan-wanglin
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 12, 2024
@openshift-ci-robot
Copy link
Contributor

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-42180 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-42180 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

Requesting review from QA contact:
/cc @gpei

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 openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 12, 2024
@openshift-ci openshift-ci bot requested a review from gpei October 12, 2024 04:15
@openshift-merge-bot openshift-merge-bot bot merged commit b6457e9 into openshift:release-4.14 Oct 12, 2024
10 of 16 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-42285: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #9040

/assign lwan-wanglin

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

[ART PR BUILD NOTIFIER]

Distgit: ose-installer
This PR has been included in build ose-installer-container-v4.14.0-202410120808.p0.gb6457e9.assembly.stream.el8.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.14.0-202410120808.p0.gb6457e9.assembly.stream.el8.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.14.0-202410120808.p0.gb6457e9.assembly.stream.el8.
All builds following this will include this PR.

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

@r4f4 r4f4 r4f4 left review comments

@mtulio mtulio Awaiting requested review from mtulio

@patrickdillon patrickdillon Awaiting requested review from patrickdillon

@gpei gpei Awaiting requested review from gpei

Assignees

@sadasu sadasu

@lwan-wanglin lwan-wanglin

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@openshift-cherrypick-robot @openshift-ci-robot @lwan-wanglin @sadasu @gpei @openshift-bot @r4f4