Bug 1725526 - m4.xlarge is not supported in ap-northeast-2b
Summary: m4.xlarge is not supported in ap-northeast-2b
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.2.0
Assignee: Abhinav Dahiya
QA Contact: sheng.lao
URL:
Whiteboard:
Depends On:
Blocks: 1725524
TreeView+ depends on / blocked
 
Reported: 2019-07-01 03:33 UTC by sheng.lao
Modified: 2019-10-16 06:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:32:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:32:57 UTC

Description sheng.lao 2019-07-01 03:33:54 UTC
Description of problem:
m4.xlarge is not supported in ap-northeast-2b

Version-Release number of selected component (if applicable):
./openshift-install v4.2.0-201906282120-dirty
built from commit 8daaee2f61f127abb96786f2eb6d141fe336be09
release image registry.svc.ci.openshift.org/ocp/release@sha256:46ff10e0129161dafb0da9ab2edc0c1e664e0d03fc45ffe06ab81eb2fb503d1c

How reproducible:
always get error when creating cluster in ap-northeast-2

Steps to Reproduce:
1../openshift-install create cluster --dir test1
? Platform aws
? Region ap-northeast-2

Actual results:
ERROR                                              
ERROR Error: Error launching source instance: Unsupported: Your requested instance type (m4.xlarge) is not supported in your requested Availability Zone (ap-northeast-2b). Please retry your request by not specifying an Availability Zone or choosing ap-northeast-2a, ap-northeast-2c. 


Expected results:
Successfully create cluster in region ap-northeast-2 

Additional info:

Comment 1 Abhinav Dahiya 2019-07-10 22:20:07 UTC
https://github.com/openshift/installer/pull/1935

Comment 3 sheng.lao 2019-07-11 10:24:29 UTC
Fixed in version 4.2.0-0.nightly-2019-07-11-071248

Comment 4 errata-xmlrpc 2019-10-16 06:32:46 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, 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/RHBA-2019:2922


Note You need to log in before you can comment on or make changes to this bug.