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.

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

OCPBUGS-42180: Add AWS r8g to arm tested instance types #9040

Merged

Conversation

lwan-wanglin
Copy link
Contributor

Add AWS r8g to arm tested instance types for 4.15.
QE has tested r8g instance type in 4.15 and 4.14 cluster, the customer need to use it in 4.14 cluster, so updating the doc backport to 4.15 and 4.14

@lwan-wanglin
Copy link
Contributor Author

/jira cherrypick OCPBUGS-41929

@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: Jira Issue OCPBUGS-41929 has been cloned as Jira Issue OCPBUGS-42180. Will retitle bug to link to clone.
/retitle OCPBUGS-42180: Add AWS r8g to arm tested instance types

In response to this:

/jira cherrypick OCPBUGS-41929

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 Add AWS r8g to arm tested instance types OCPBUGS-42180: Add AWS r8g to arm tested instance types Sep 19, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 19, 2024
@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: This pull request references Jira Issue OCPBUGS-42180, 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.15.z) matches configured target version for branch (4.15.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-41929 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-41929 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
  • bug has dependents

Requesting review from QA contact:
/cc @gpei

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Add AWS r8g to arm tested instance types for 4.15.
QE has tested r8g instance type in 4.15 and 4.14 cluster, the customer need to use it in 4.14 cluster, so updating the doc backport to 4.15 and 4.14

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 a review from gpei September 19, 2024 03:04
@lwan-wanglin
Copy link
Contributor Author

@r4f4 @patrickdillon PTAL,thanks!

Copy link
Contributor

openshift-ci bot commented Sep 19, 2024

@lwan-wanglin: 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-vsphere-static-ovn 47f3e8d link false /test e2e-vsphere-static-ovn
ci/prow/okd-scos-e2e-aws-upgrade 47f3e8d link false /test okd-scos-e2e-aws-upgrade
ci/prow/altinfra-e2e-aws-ovn-single-node 47f3e8d link false /test altinfra-e2e-aws-ovn-single-node

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

r4f4 commented Sep 19, 2024

/approve

Copy link
Contributor

openshift-ci bot commented Sep 19, 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 19, 2024
@sadasu
Copy link
Contributor

sadasu commented Sep 20, 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 Sep 20, 2024
@sadasu
Copy link
Contributor

sadasu commented Sep 20, 2024

/lgtm

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

gpei commented Sep 21, 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 Sep 21, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit d71b35b into openshift:release-4.15 Sep 21, 2024
17 of 20 checks passed
@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: Jira Issue OCPBUGS-42180: All pull requests linked via external trackers have merged:

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

In response to this:

Add AWS r8g to arm tested instance types for 4.15.
QE has tested r8g instance type in 4.15 and 4.14 cluster, the customer need to use it in 4.14 cluster, so updating the doc backport to 4.15 and 4.14

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-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.15.0-202409210905.p0.gd71b35b.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.15.0-202409210905.p0.gd71b35b.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.15.0-202409210905.p0.gd71b35b.assembly.stream.el8.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.15.0-202409220759.p0.gd71b35b.assembly.stream.el8.
All builds following this will include this PR.

@lwan-wanglin
Copy link
Contributor Author

/cherry-pick release-4.14

@openshift-cherrypick-robot

@lwan-wanglin: new pull request created: #9050

In response to this:

/cherry-pick release-4.14

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

Successfully merging this pull request may close these issues.

7 participants