Bug 2016955

Summary:	m5.large instance type for bootstrap node is hardcoded causing deployments to fail if instance type is not available
Product:	OpenShift Container Platform	Reporter:	Simon Reber <sreber>
Component:	Installer	Assignee:	Patrick Dillon <padillon>
Installer sub component:	openshift-installer	QA Contact:	Yunfei Jiang <yunjiang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	cldavey, mstaeble, openshift-bugs-escalate, padillon
Version:	4.8
Target Milestone:	---
Target Release:	4.10.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Bootstrap node instance type was hard-coded Consequence: if that hard-coded instance type was unavailable in the install region, installation was impossible Fix: set bootstrap instance type to be the same as master instance type Result: bootstrap instance type is now configurable so that if the instance type is unavailable in a region, it can be changed and install will be possible	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:21:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2017985, 2017986

Description Simon Reber 2021-10-25 09:37:26 UTC

Version: OpenShift Container Platform 4.8.13

$ openshift-install version
N/A

Platform: AWS

Please specify: IPI

What happened?

In various AWS region m5.large instances are no longer available and thus can't be provisioned. Since OpenShift Container Platform - Installer for AWS has m5.large hard-coded for the bootstrap instance the installation are currently failing and are not able to process.

This is causing massive project impact as all other instance types required for the OpenShift Container Platform - Cluster are available.

It's therefore required to have a way to either specify the instance type for the bootstrap Node or take the same instance type as defined for either Control-Plane or Worker Nodes.

This is urgent as customers are not able to deploy OpenShift Container Platform 4 at this moment due to this issue.

Comment 1 Matthew Staebler 2021-10-25 14:25:45 UTC

There is a temporary shortage of instances available in specific availability zones.

The workaround is to explicitly specify the availability zones to use for the masters so that the first availability zone is one where there are m5.large instances available.

Comment 7 Yunfei Jiang 2021-10-29 07:23:22 UTC

verified. PASS.
OCP Version: 4.10.0-0.nightly-2021-10-28-211203

Comment 10 errata-xmlrpc 2022-03-10 16:21:40 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056