Bug 2041926 - [IPI on Alibabacloud] Installer ignores public zone when it does not exist
Summary: [IPI on Alibabacloud] Installer ignores public zone when it does not exist
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: aos-install
QA Contact: Jianli Wei
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-18 14:41 UTC by Matthew Staebler
Modified: 2022-03-10 16:40 UTC (History)
1 user (show)

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

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5565 0 None open Bug 2041926: [Alibaba] fix creating public record being skipped 2022-01-22 17:14:05 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:40:44 UTC

Description Matthew Staebler 2022-01-18 14:41:24 UTC
If the user chooses a base domain for which there is no zone, the installer does not indicate this issue to the user. Moreover, the terraform that should be creating the A record in the zone is simply skipped rather than raising an error. The installation does not fail until it times out waiting for access to the bootstrap's temporary control plane. At that point, it is difficult to diagnose what the underlying cause of the failure was.

Comment 1 Matthew Staebler 2022-01-18 14:44:14 UTC
Setting this as a non-blocker since it does not prevent an installation that would otherwise have succeeded.

Comment 2 husun 2022-01-24 09:11:35 UTC
Fixed it on the PR https://github.com/openshift/installer/pull/5565

Comment 3 Jianli Wei 2022-01-26 09:25:53 UTC
$ openshift-install version
openshift-install 4.10.0-0.ci-2022-01-26-033956
built from commit 281380228dab000afcf5299a5a8fef6c03958340
release image registry.ci.openshift.org/ocp/release@sha256:26308dd5cde2edbfbafebff6521628779f64e492306a2bc457d973215c4773ae
release architecture amd64
$ yq e '.baseDomain' work2/install-config.yaml 
$ yq e '.platform' work2/install-config.yaml 
  region: cn-hangzhou
$ openshift-install create manifests --dir work2
INFO Consuming Install Config from target directory 
INFO Manifests created in: work2/manifests and work2/openshift 
$ openshift-install create cluster --dir work2 --log-level info
INFO Consuming OpenShift Install (Manifests) from target directory 
INFO Consuming Worker Machines from target directory 
INFO Consuming Common Manifests from target directory 
INFO Consuming Openshift Manifests from target directory 
INFO Consuming Master Machines from target directory 
INFO Creating infrastructure resources...         
ERROR Error: [ERROR] terraform-provider-alicloud/alicloud/resource_alicloud_alidns_record.go:134: Resource alicloud_alidns_record AddDomainRecord Failed!!! [SDK alibaba-cloud-sdk-go ERROR]: 
ERROR SDK.ServerError                              
ERROR ErrorCode: InvalidDomainName.NoExist         
ERROR Recommend: https://error-center.aliyun.com/status/search?Keyword=InvalidDomainName.NoExist&source=PopGw 
ERROR RequestId: F7C01DEC-9179-5BF2-9BB8-A4224F5AEF43 
ERROR Message: The specified domain name does not exist. Refresh the page and try again. 
ERROR   on ../../tmp/openshift-install-cluster-4222579097/dns/privatezone.tf line 13, in resource "alicloud_alidns_record" "dns_public_record": 
ERROR   13: resource "alicloud_alidns_record" "dns_public_record" { 
FATAL failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change 

Comment 4 Jianli Wei 2022-01-26 09:27:37 UTC
Mark as verified according to the above comment.

Comment 7 errata-xmlrpc 2022-03-10 16:40:33 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.


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