Bug 1809820
| Summary: | GCP UPI cluster cluster name regex check does not support '.' in cluster name | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Antonio Escalera <aescaler> | |
| Component: | Installer | Assignee: | Jeremiah Stuever <jstuever> | |
| Installer sub component: | openshift-installer | QA Contact: | Yang Yang <yanyang> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | unspecified | CC: | bsmitley, jstuever, mbarrett, sdodson | |
| Version: | 4.2.z | |||
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1811153 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:17:56 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1811153 | |||
(In reply to Antonio Escalera from comment #0) > Description of problem: > > UPI in GCP does not support clusters with '.' in the name > > Version-Release number of the following components: > > 4.3.2 > > How reproducible: > > 100% > > Steps to Reproduce: > > 1. Create `install-config.yaml` with cluster name field containing anything > including a '.' > > Actual results: > > `FATAL failed to fetch Master Machines: failed to load asset "Install > Config": invalid "install-config.yaml" file: metadata.name: Invalid value: > "gcpusc1-h.sbx.xpaas": GCP requires cluster name to match regular expression > (?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?)` I think the error message is clear that we do not support a cluster name with `.` for GCP. I'm not sure what's the bug here? > > Expected results: > > Cluster manifest files are created successfully The bug is not supporting cluster name with '.' for GCP. That's inconvenient for customers and is supported on every other platform I've attempted. The answer "We/the openshift installer don't support cluster names with '.' for GCP" isn't something I can go back to a customer with. I'll at least need to know why it isn't supported. Why aren't clusters with '.' supported? What changes will need to be made to support this? (In reply to Abhinav Dahiya from comment #1) > (In reply to Antonio Escalera from comment #0) > > Description of problem: > > > > UPI in GCP does not support clusters with '.' in the name > > > > Version-Release number of the following components: > > > > 4.3.2 > > > > How reproducible: > > > > 100% > > > > Steps to Reproduce: > > > > 1. Create `install-config.yaml` with cluster name field containing anything > > including a '.' > > > > Actual results: > > > > `FATAL failed to fetch Master Machines: failed to load asset "Install > > Config": invalid "install-config.yaml" file: metadata.name: Invalid value: > > "gcpusc1-h.sbx.xpaas": GCP requires cluster name to match regular expression > > (?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?)` > > > I think the error message is clear that we do not support a cluster name > with `.` for GCP. I'm not sure what's the bug here? > > > > > Expected results: > > > > Cluster manifest files are created successfully The bug is not supporting cluster name with '.' for GCP. That's inconvenient for customers and is supported on every other platform I've attempted. The answer "We/the openshift installer don't support cluster names with '.' for GCP" isn't something I can go back to a customer with. I'll at least need to know why it isn't supported. Why aren't clusters with '.' supported? What changes will need to be made to support this? Here is the validation check: https://github.com/openshift/installer/blob/master/pkg/types/gcp/validation/platform.go#L76-L85 Verified with 4.5.0-0.nightly-2020-03-10-031811 GCP UPI install with cluster name yy.cn passed. From QE perspective, '.' is supported in cluster name 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:2409 |
Description of problem: UPI in GCP does not support clusters with '.' in the name Version-Release number of the following components: 4.3.2 How reproducible: 100% Steps to Reproduce: 1. Create `install-config.yaml` with cluster name field containing anything including a '.' Actual results: `FATAL failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" file: metadata.name: Invalid value: "gcpusc1-h.sbx.xpaas": GCP requires cluster name to match regular expression (?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?)` Expected results: Cluster manifest files are created successfully