Bug 1784322
Summary: | Subdomain validation does not match Azure domain rule | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Yang Yang <yanyang> |
Component: | Installer | Assignee: | Patrick Dillon <padillon> |
Installer sub component: | openshift-installer | QA Contact: | Yang Yang <yanyang> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | jiajliu, scuppett |
Version: | 4.3.0 | ||
Target Milestone: | --- | ||
Target Release: | 4.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: installer displayed wrong validation rule in message which said beginning with a number was ok
Consequence: specifying cluster name beginning with number would fail even though message says it was ok
Fix: fix the displayed message to display proper rule
Result: message is consistent with validation check
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-04 11:20:19 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
Yang Yang
2019-12-17 08:54:34 UTC
Setting target release to 4.4 to perform investigation on the active development branch (will be re-set/cloned where fixes & backports, if any, are required). Looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1777232 Verified with 4.4.0-0.nightly-2020-02-07-012035 Installing a cluster on Azure using 123456 as cluster name and got the below error level=fatal msg="failed to fetch Terraform Variables: failed to load asset \"Install Config\": invalid \"install-config.yaml\" file: metadata.name: Invalid value: \"123456\": Azure requires cluster name to match regular expression [a-z][a-z0-9-]{1,61}[a-z0-9]" Cluster name validation is as expected hence moving it to verified state. 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, 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/RHBA-2020:0581 |