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

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

Open
wants to merge 1 commit into
base: release-4.14
Choose a base branch
from

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #9040

/assign lwan-wanglin

@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!

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.

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

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!

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants