Bug 2033239 - [IPI on Alibabacloud] 'openshift-install' gets the wrong region (‘cn-hangzhou’) selected
Summary: [IPI on Alibabacloud] 'openshift-install' gets the wrong region (‘cn-hangzhou...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: aos-install
QA Contact: Jianli Wei
URL:
Whiteboard:
: 2034578 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-16 10:43 UTC by Jianli Wei
Modified: 2022-03-10 16:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:34:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5490 0 None open Bug 2033239: Alibaba: fix the wrong default region 2022-01-01 00:01:02 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:34:42 UTC

Description Jianli Wei 2021-12-16 10:43:31 UTC
Version:

$ openshift-install version
openshift-install 4.10.0-0.nightly-2021-12-15-151042
built from commit 7485aa4e85231dd09b3b1a693905483edfddf9a8
release image registry.ci.openshift.org/ocp/release@sha256:b4403653c3f3610e64c8334e50c48b018c8dba7d33b0d2d98905ce100e932a52
release architecture amd64

Platform: alibabacloud

Please specify:
* IPI (automated install with `openshift-install`. If you don't know, then it's IPI)

What happened?
Run 'openshift-install' interactively to create install-config (or cluster), if pressing Enter directly on prompting for "Region", although the default selected region is "ap-northeast-1 (Japan (Tokyo))", it'll show "Region cn-hangzhou" then (and also in the generated install-config.yaml). 

$ openshift-install create install-config --dir work2
? SSH Public Key /home/jiwei/.ssh/openshift-qe.pub
? Platform alibabacloud
? Region  [Use arrows to move, type to filter, ? for more help]
> ap-northeast-1 (Japan (Tokyo))
  ap-south-1 (India (Mumbai))
  ap-southeast-1 (Singapore)
  ap-southeast-2 (Australia (Sydney))
  ap-southeast-3 (Malaysia (Kuala Lumpur))
  ap-southeast-5 (Indonesia (Jakarta))
  ap-southeast-6 (Philippines (Manila))
......
$ cat work2/install-config.yaml | grep region
    region: cn-hangzhou
$ 

What did you expect to happen?
The selected region should be "ap-northeast-1".

How to reproduce it (as minimally and precisely as possible)?
Always.

Comment 1 Johnny Liu 2021-12-21 11:52:51 UTC
*** Bug 2034578 has been marked as a duplicate of this bug. ***

Comment 3 Jianli Wei 2022-01-07 08:27:55 UTC
Tested with 4.10.0-0.nightly-2022-01-07-050246, now by default the region 'cn-hangzhou (China (Hangzhou))' is shown as selected and pressing Enter directly would get this region in use. Mark as verified. 

$ openshift-install version
openshift-install 4.10.0-0.nightly-2022-01-07-050246
built from commit 342906e784513271fa0bb4f1bf0e808d0cc2b44b
release image registry.ci.openshift.org/ocp/release@sha256:2e3647d49ef9a49a5f1c97727a4fc4a99210b75e9d737314c6f1a7f8888f2bff
release architecture amd64
$ openshift-install create install-config --dir work
? SSH Public Key /home/fedora/.ssh/openshift-qe.pub
? Platform alibabacloud
? Region  [Use arrows to move, type to filter, ? for more help]
  cn-beijing (China (Beijing))
  cn-chengdu (China (Chengdu))
  cn-guangzhou (China (Guangzhou))
> cn-hangzhou (China (Hangzhou))
  cn-heyuan (China (Heyuan))
  cn-hongkong (China (Hong Kong))
  cn-huhehaote (China (Hohhot))

Comment 7 errata-xmlrpc 2022-03-10 16:34:29 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


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