[release-4.7] bug 1971163: Updating AWS instance types #4992

openshift-cherrypick-robot · 2021-06-12T15:49:35Z

This is an automated cherry-pick of #4990

/assign patrickdillon

As a follow-up to docs bug BZ1878374, it was pointed out that two of the instance types listed in the Cloud Formation templates do not exist. This change corrects the instance types to those proposed on the corresponding docs PR.

openshift-ci · 2021-06-12T15:49:43Z

@openshift-cherrypick-robot: Bugzilla bug 1971068 has been cloned as Bugzilla bug 1971163. Retitling PR to link against new bug.
/retitle [release-4.7] bug 1971163: Updating AWS instance types

In response to this:

[release-4.7] bug 1971068: Updating AWS instance types

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 · 2021-06-12T15:49:49Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1971163, which is invalid:

expected dependent Bugzilla bug 1971068 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.7] bug 1971163: Updating AWS instance types

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.

patrickdillon · 2021-06-14T13:10:10Z

/lgtm

patrickdillon · 2021-06-14T13:11:27Z

/approve

openshift-ci · 2021-06-14T13:11:36Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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:

~~upi/aws/OWNERS~~ [patrickdillon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-bot · 2021-06-14T14:50:03Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-14T15:29:05Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-14T17:46:05Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-14T19:22:24Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-14T21:59:26Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-15T01:00:33Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-06-15T01:00:37Z

@openshift-bot: This pull request references Bugzilla bug 1971163, which is invalid:

expected dependent Bugzilla bug 1971068 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 1971164 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 1971164 to target a release in 4.8.0, but it targets "4.6.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

kalexand-rh · 2021-06-15T19:11:45Z

/bugzilla refresh

openshift-ci · 2021-06-15T19:11:50Z

@kalexand-rh: This pull request references Bugzilla bug 1971163, which is invalid:

expected dependent Bugzilla bug 1971068 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 1971164 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 1971164 to target a release in 4.8.0, but it targets "4.6.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla 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.

kalexand-rh · 2021-06-15T20:17:01Z

@yunjiang29, can you help me get this PR unstuck so I can move openshift/openshift-docs#33358, too?

openshift-bot · 2021-06-15T20:23:37Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-15T23:57:37Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-16T01:00:47Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-06-16T01:00:52Z

@openshift-bot: This pull request references Bugzilla bug 1971163, which is invalid:

expected dependent Bugzilla bug 1971068 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 1971164 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (NOTABUG) instead
expected dependent Bugzilla bug 1971164 to target a release in 4.8.0, but it targets "4.6.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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 · 2021-06-16T13:36:09Z

@patrickdillon: This pull request references Bugzilla bug 1971163, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.7.z) matches configured target release for branch (4.7.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 1971068 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 1971068 targets the "4.8.0" release, which is one of the valid target releases: 4.8.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (yunjiang@redhat.com), skipping review request.

In response to this:

/bugzilla 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.

patrickdillon · 2021-06-16T13:48:43Z

/label bugzilla/severity-urgent

openshift-ci · 2021-06-16T13:48:44Z

@patrickdillon: The label(s) /label bugzilla/severity-urgent cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed

In response to this:

/label bugzilla/severity-urgent

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.

stevekuznetsov · 2021-06-16T13:53:10Z

/bugzilla refresh

openshift-ci · 2021-06-16T13:53:17Z

@stevekuznetsov: This pull request references Bugzilla bug 1971163, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.7.z) matches configured target release for branch (4.7.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 1971068 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 1971068 targets the "4.8.0" release, which is one of the valid target releases: 4.8.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (yunjiang@redhat.com), skipping review request.

In response to this:

/bugzilla 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-bot · 2021-06-16T15:15:30Z

/retest

Please review the full test history for this PR and help us cut down flakes.

patrickdillon · 2021-06-16T15:27:22Z

/skip

kalexand-rh · 2021-06-16T17:07:44Z

/retest

openshift-bot · 2021-06-16T18:16:31Z

/retest

Please review the full test history for this PR and help us cut down flakes.

kalexand-rh · 2021-06-16T18:26:26Z

/retest

kalexand-rh · 2021-06-16T19:20:10Z

/retest

kalexand-rh · 2021-06-16T19:36:36Z

/test e2e-crc

kalexand-rh · 2021-06-16T20:35:48Z

/test e2e-aws-upgrade

openshift-bot · 2021-06-16T20:40:32Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-16T21:04:34Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-16T22:52:31Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-17T07:46:18Z

/retest

Please review the full test history for this PR and help us cut down flakes.

kalexand-rh · 2021-06-17T12:13:38Z

/retest

kalexand-rh · 2021-06-17T15:48:00Z

/retest

openshift-bot · 2021-06-17T15:52:20Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-17T18:04:19Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-17T20:41:18Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-06-17T22:41:43Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-ci · 2021-06-17T23:54:16Z

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-crc	`6b8ed78`	link	`/test e2e-crc`

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.

openshift-bot · 2021-06-18T00:17:19Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-ci · 2021-06-18T01:23:52Z

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

openshift/installer#4992

Bugzilla bug 1971163 has been moved to the MODIFIED state.

In response to this:

[release-4.7] bug 1971163: Updating AWS instance types

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.

Updating AWS instance types

6b8ed78

As a follow-up to docs bug BZ1878374, it was pointed out that two of the instance types listed in the Cloud Formation templates do not exist. This change corrects the instance types to those proposed on the corresponding docs PR.

openshift-cherrypick-robot mentioned this pull request Jun 12, 2021

bug 1971068: Updating AWS instance types #4990

Merged

openshift-ci bot assigned patrickdillon Jun 12, 2021

openshift-ci bot changed the title ~~[release-4.7] bug 1971068: Updating AWS instance types~~ [release-4.7] bug 1971163: Updating AWS instance types Jun 12, 2021

openshift-ci bot requested review from jstuever and patrickdillon June 12, 2021 15:49

openshift-ci bot added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Jun 12, 2021

openshift-ci bot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jun 12, 2021

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 14, 2021

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 14, 2021

kalexand-rh mentioned this pull request Jun 15, 2021

BZ1971068: correcting AWS instances openshift/openshift-docs#33358

Merged

stevekuznetsov removed the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Jun 16, 2021

openshift-ci bot added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Jun 16, 2021

mfojtik added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 16, 2021

openshift-merge-robot merged commit dcf576e into openshift:release-4.7 Jun 18, 2021

[release-4.7] bug 1971163: Updating AWS instance types #4992

[release-4.7] bug 1971163: Updating AWS instance types #4992

Conversation

openshift-cherrypick-robot commented Jun 12, 2021

openshift-ci bot commented Jun 12, 2021

openshift-ci bot commented Jun 12, 2021

patrickdillon commented Jun 14, 2021

patrickdillon commented Jun 14, 2021

openshift-ci bot commented Jun 14, 2021

openshift-bot commented Jun 14, 2021

openshift-bot commented Jun 14, 2021

openshift-bot commented Jun 14, 2021

openshift-bot commented Jun 14, 2021

openshift-bot commented Jun 14, 2021

openshift-bot commented Jun 15, 2021

openshift-ci bot commented Jun 15, 2021

kalexand-rh commented Jun 15, 2021

openshift-ci bot commented Jun 15, 2021

kalexand-rh commented Jun 15, 2021

openshift-bot commented Jun 15, 2021

openshift-bot commented Jun 15, 2021

openshift-bot commented Jun 16, 2021

openshift-ci bot commented Jun 16, 2021

openshift-ci bot commented Jun 16, 2021

patrickdillon commented Jun 16, 2021

openshift-ci bot commented Jun 16, 2021

stevekuznetsov commented Jun 16, 2021

openshift-ci bot commented Jun 16, 2021

openshift-bot commented Jun 16, 2021

patrickdillon commented Jun 16, 2021

kalexand-rh commented Jun 16, 2021

openshift-bot commented Jun 16, 2021

kalexand-rh commented Jun 16, 2021

kalexand-rh commented Jun 16, 2021

kalexand-rh commented Jun 16, 2021

kalexand-rh commented Jun 16, 2021

openshift-bot commented Jun 16, 2021

openshift-bot commented Jun 16, 2021

openshift-bot commented Jun 16, 2021

openshift-bot commented Jun 17, 2021

kalexand-rh commented Jun 17, 2021

kalexand-rh commented Jun 17, 2021

openshift-bot commented Jun 17, 2021

openshift-bot commented Jun 17, 2021

openshift-bot commented Jun 17, 2021

openshift-bot commented Jun 17, 2021

openshift-ci bot commented Jun 17, 2021 • edited Loading

openshift-bot commented Jun 18, 2021

openshift-ci bot commented Jun 18, 2021

openshift-ci bot commented Jun 17, 2021 •

edited

Loading