Version: $ openshift-install version openshift-install 4.10.0-0.ci-2021-12-17-014800 built from commit 2a320fbf90d2a232c19517251ea4f7f5e171682c release image registry.ci.openshift.org/ocp/release@sha256:c04823dfd2d2fd8cc4da4bf63dc4e5d7f34ec9a414746863a350a822423b8c7c release architecture amd64 Platform: alibabacloud Please specify: * IPI (automated install with `openshift-install`. If you don't know, then it's IPI) What happened? The interactive installer would ask for Base Domain every time, without the ability listing existing base domains. $ openshift-install create install-config --dir jiwei-ali01 ? SSH Public Key /home/jiwei/.ssh/openshift-qe.pub ? Platform alibabacloud ? Region us-east-1 ? Base Domain alicloud-qe.devcluster.openshift.com ? Cluster Name jiwei-ali01 ? Pull Secret [? for help] *********** INFO Install-Config created in: jiwei-ali01 $ $ openshift-install create install-config --dir jiwei-ali02 ? SSH Public Key /home/jiwei/.ssh/openshift-qe.pub ? Platform alibabacloud ? Region us-east-1 ? Base Domain [? for help] What did you expect to happen? Existing base domains should be automatically listed with alibabacloud. How to reproduce it (as minimally and precisely as possible)? Always. Anything else we need to know? Existing base domains can be automatically listed with gcp/aws/etc. $ openshift-install create install-config --dir jiwei-gcp01 ? SSH Public Key /home/jiwei/.ssh/openshift-qe.pub ? Platform gcp INFO Credentials loaded from file "/home/jiwei/.gcp/osServiceAccount.json" ? Project ID OpenShift QE (openshift-qe) ? Region us-central1 ? Base Domain [Use arrows to move, type to filter, ? for more help] > qe.gcp.devcluster.openshift.com qe1.gcp.devcluster.openshift.com qe2.qe1.gcp.devcluster.openshift.com quay350.qe.gcp.devcluster.openshift.com quayldap.qe.gcp.devcluster.openshift.com $ gcloud dns managed-zones list --filter="visibility=public" NAME DNS_NAME DESCRIPTION VISIBILITY qe qe.gcp.devcluster.openshift.com. Base Domain for QE clusters public qe1 qe1.gcp.devcluster.openshift.com. public qe2 qe2.qe1.gcp.devcluster.openshift.com. public quay350 quay350.qe.gcp.devcluster.openshift.com. public quayldap quayldap.qe.gcp.devcluster.openshift.com. public $
Tested and the existing base domain does be listed, and pressing Enter directly does get it applied. Mark as verified. $ openshift-install version openshift-install 4.10.0-0.nightly-2022-01-19-050236 built from commit 274a5848e4a85460f9fe367ddd760a597cecd679 release image registry.ci.openshift.org/ocp/release@sha256:a7fd0f26d9a6bc21f1e749bf17b261cd479ea19354d0bda86673c732b53a9b6c release architecture amd64 $ $ openshift-install create install-config --dir work ? SSH Public Key /home/fedora/.ssh/openshift-qe.pub ? Platform alibabacloud ? Region cn-hangzhou ? Base Domain [Use arrows to move, type to filter, ? for more help] > alicloud-qe.devcluster.openshift.com ? Base Domain alicloud-qe.devcluster.openshift.com ? Cluster Name jiwei-302 ? Pull Secret [? for help] *** INFO Install-Config created in: work $
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