+++ This bug was initially created as a clone of Bug #1765269 +++ User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36 Build Identifier: The ocp 4.2 installer does not list eu-north-1 (Stockholm) in the list of AWS regions. Only options are eu-central (Frankfort), eu-west-1 (Ireland), eu-west-2 (London) and eu-west-3 (Paris) Reproducible: Always Steps to Reproduce: 1. Run openshift-installer create install-config 2. Select 'aws' platform 3. notice the select list of AWS regions does not include eu-north-1 (Stockholm) Actual Results: Can't select desired AWS region Expected Results: Deploy OCP 4.2 cluster in eu-north-1 (Stockholm) AWS region I'm working with a customer who has an OCP 3.11 cluster running in eu-north-1 and wants to run OCP 4.2 in the same region. --- Additional comment from Abhinav Dahiya on 2019-10-24 13:55:25 EDT --- There is no AMI available for RHCOS in that regions. --- Additional comment from Colin Walters on 2019-10-24 14:07:03 EDT --- https://github.com/openshift/installer/blob/e349157f325dba2d06666987603da39965be5319/data/data/rhcos.json#L24 right? But there's installer steps needed too which happened in https://github.com/openshift/installer/pull/2308 and just needs backporting to 4.2 I believe.
@Jianlin, this region was added to 4.2: https://github.com/openshift/installer/pull/2308/files Will you please confirm that this region works and approve docs change here? https://github.com/openshift/openshift-docs/pull/17602
4.2.z PR is still in flight.
But that PR is blocking on getting the 4.3.0 bug 1765269 VERIFIED.
Verified it with 4.2.0-0.nightly-2019-10-27-140004 # openshift-install create cluster --dir bz-1765308 ... ? Region eu-north-1 ? Base Domain [Use arrows to move, type to filter, ? for more help] # export KUBECONFIG=`pwd`/kubeconfig # sh check_cluster_health.sh Passed
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:3303