Creating a 4.6.z clone based on https://issues.redhat.com/browse/RFE-1078?focusedCommentId=16310052&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16310052


+++ This bug was initially created as a clone of Bug #1942706 +++

+++ This bug was initially created as a clone of Bug #1939661 +++

There is an RFE to support the new AWS region in Osaka, ap-northeast-3

https://issues.redhat.com/browse/RFE-1078

The CoreOS team is adding publication of the AMIs to our build pipelines; this BZ can be used to update the boot images + region handling in the Installer

Feel free to assign to me to handle the Installer change.

--- Additional comment from Micah Abbott on 2021-03-22 15:47:26 UTC ---

@Matthew I'm setting this back to the Installer component, so that the Installer QE team can test this new region

I'll make the PR to the installer for the change.

--- Additional comment from Micah Abbott on 2021-03-24 16:53:16 UTC ---

Linked PR is merged; moving to MODIFIED

--- Additional comment from OpenShift Automated Release Tooling on 2021-03-24 18:31:39 UTC ---

Elliott changed bug status from MODIFIED to ON_QA.

--- Additional comment from Micah Abbott on 2021-03-24 18:53:32 UTC ---

RHCOS 4.7 builds are configured to publish to ap-northeast-3, but are currently broken due to build pipeline infrastructure issues.

I'll make the update to the release-4.7 installer branch once the RHCOS build pipeline is up and running again.

--- Additional comment from Katherine Dubé on 2021-03-29 16:00:35 UTC ---

The AWS SDK used in the installer will need to be updated to include endpoints for ap-northeast-3.

% ./openshift-install version
./openshift-install 4.7.4
built from commit 7d4efe10b441e9cb3dda33f81c62fd0eaeb3d6e6
release image quay.io/openshift-release-dev/ocp-release@sha256:999a6a4bd731075e389ae601b373194c6cb2c7b4dadd1ad06ef607e86476b129
katherine@Katherines-MacBook-Pro openshift-install % ./openshift-install create install-config --dir katherine
FATAL failed to fetch Install Config: failed to load asset "Install Config": platform.aws.serviceEndpoints: Invalid value: []aws.ServiceEndpoint(nil): [failed to find endpoint for service "ec2": UnknownEndpointError: could not resolve endpoint
FATAL 	partition: "all partitions", service: "ec2", region: "ap-northeast-3", failed to find endpoint for service "elasticloadbalancing": UnknownEndpointError: could not resolve endpoint
FATAL 	partition: "all partitions", service: "elasticloadbalancing", region: "ap-northeast-3", failed to find endpoint for service "iam": UnknownEndpointError: could not resolve endpoint
FATAL 	partition: "all partitions", service: "iam", region: "ap-northeast-3", failed to find endpoint for service "route53": UnknownEndpointError: could not resolve endpoint
FATAL 	partition: "all partitions", service: "route53", region: "ap-northeast-3", failed to find endpoint for service "s3": UnknownEndpointError: could not resolve endpoint
FATAL 	partition: "all partitions", service: "s3", region: "ap-northeast-3", failed to find endpoint for service "sts": UnknownEndpointError: could not resolve endpoint
FATAL 	partition: "all partitions", service: "sts", region: "ap-northeast-3", failed to find endpoint for service "tagging": UnknownEndpointError: could not resolve endpoint
FATAL 	partition: "all partitions", service: "tagging", region: "ap-northeast-3"]

--- Additional comment from Steve Milner on 2021-03-29 19:11:54 UTC ---

Unfortunately I don't think updating the SDK is as simple as we hoped. It looks like if we update it we will break the terraform plugin.