Bug 2041926
Summary: | [IPI on Alibabacloud] Installer ignores public zone when it does not exist | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Matthew Staebler <mstaeble> |
Component: | Installer | Assignee: | aos-install |
Installer sub component: | openshift-installer | QA Contact: | Jianli Wei <jiwei> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | husun |
Version: | 4.10 | ||
Target Milestone: | --- | ||
Target Release: | 4.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-03-10 16:40:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matthew Staebler
2022-01-18 14:41:24 UTC
Setting this as a non-blocker since it does not prevent an installation that would otherwise have succeeded. Fixed it on the PR https://github.com/openshift/installer/pull/5565 $ 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 non-existing.devcluster.openshift.com $ yq e '.platform' work2/install-config.yaml alibabacloud: 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: [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 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" { ERROR ERROR FATAL failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change $ Mark as verified according to the above comment. 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 |