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-3193: [release-4.11] [AWS] Add AWS r6i into tested instance types table #6350

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #6337

/assign yunjiang29

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 15, 2022

@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-fips 15ab500 link false /test e2e-aws-fips
ci/prow/e2e-aws-single-node 15ab500 link false /test e2e-aws-single-node
ci/prow/e2e-aws-upi-proxy 15ab500 link false /test e2e-aws-upi-proxy

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

@yunjiang29
Copy link
Contributor

/assign @patrickdillon

@sadasu
Copy link
Contributor

sadasu commented Sep 22, 2022

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Sep 22, 2022

/lgtm

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

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jstuever

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 22, 2022
@sadasu
Copy link
Contributor

sadasu commented Sep 22, 2022

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Sep 23, 2022

@jstuever would you also be able to add the backport-risk-assessed label?

@sadasu
Copy link
Contributor

sadasu commented Sep 23, 2022

@yunjiang29 could you please provide the cherrypick-approved label?

@yunjiang29
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 26, 2022

@yunjiang29: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/label cherry-pick-approved

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.

@yunjiang29
Copy link
Contributor

@sadasu It looks like I have no permission to add label cherry-pick-approved

@jstuever
Copy link
Contributor

/cc @patrickdillon
/uncc

@openshift-ci openshift-ci bot removed the request for review from jstuever October 12, 2022 16:08
@gpei
Copy link
Contributor

gpei commented Oct 13, 2022

/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 13, 2022
@sadasu
Copy link
Contributor

sadasu commented Oct 19, 2022

/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 19, 2022
@sadasu
Copy link
Contributor

sadasu commented Oct 20, 2022

@yunjiang29 this will not merge without a bug in Jira. And that would in turn depend on a bug in 4.12 for #6337. And the 4.12 bug should be in a verified state for this 4.11 PR to merge.

Please let us know if you have any questions regarding opening these issues in Jira.

@sadasu
Copy link
Contributor

sadasu commented Oct 20, 2022

/retest-required

1 similar comment
@sadasu
Copy link
Contributor

sadasu commented Oct 21, 2022

/retest-required

@yunjiang29
Copy link
Contributor

@sadasu lgtm, let me know if any further actions required

@sadasu
Copy link
Contributor

sadasu commented Oct 24, 2022

@yunjiang29 This 4.11 backport will is not merge without an issue in Jira. Can you open an issue in https://issues.redhat.com in the project OCPBUGS ?

@sadasu
Copy link
Contributor

sadasu commented Oct 24, 2022

/retest-required

1 similar comment
@sadasu
Copy link
Contributor

sadasu commented Oct 27, 2022

/retest-required

@sadasu
Copy link
Contributor

sadasu commented Nov 3, 2022

/retitle OCPBUGS-3193: [release-4.11] [AWS] Add AWS r6i into tested instance types table

@sadasu
Copy link
Contributor

sadasu commented Nov 3, 2022

/jira refresh

@openshift-ci openshift-ci bot changed the title [release-4.11] [AWS] Add AWS r6i into tested instance types table OCPBUGS-3193: [release-4.11] [AWS] Add AWS r6i into tested instance types table Nov 3, 2022
@openshift-ci-robot
Copy link
Contributor

@sadasu: This pull request references Jira Issue OCPBUGS-3193, which is invalid:

  • expected Jira Issue OCPBUGS-3193 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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:

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

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Nov 3, 2022
@openshift-ci-robot
Copy link
Contributor

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

  • expected Jira Issue OCPBUGS-3193 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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:

This is an automated cherry-pick of #6337

/assign yunjiang29

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

openshift-ci bot commented Nov 3, 2022

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-3193: [release-4.11] [AWS] Add AWS r6i into tested instance types table

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.

@sadasu
Copy link
Contributor

sadasu commented Jan 4, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@sadasu: This pull request references Jira Issue OCPBUGS-3193, which is invalid:

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

@sadasu
Copy link
Contributor

sadasu commented Jan 4, 2023

/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. bugzilla/valid-bug Indicates that a referenced Bugzilla 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 Jan 4, 2023
@openshift-ci-robot
Copy link
Contributor

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.11.z) matches configured target version for branch (4.11.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-3191 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-3191 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
  • bug has dependents

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

@openshift-merge-robot openshift-merge-robot merged commit f746e45 into openshift:release-4.11 Jan 4, 2023
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #6337

/assign yunjiang29

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants