Bug 1810663
| Summary: | [IPI Baremetal] Hostname requirements are too restrictive | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ben Nemec <bnemec> |
| Component: | Machine Config Operator | Assignee: | Ben Nemec <bnemec> |
| Status: | CLOSED ERRATA | QA Contact: | Victor Voronkov <vvoronko> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4 | CC: | amurdaca, kgarriso, mnguyen, smilner, vvoronko, wsun |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature: Arbitrary hostnames for master nodes.
Reason: Deployers will often have preferred naming formats for their hosts and will not want to use master-0, master-1, etc.
Result: Master nodes can be named with any valid hostname.
|
Story Points: | --- |
| Clone Of: | 1804944 | Environment: | |
| Last Closed: | 2020-05-04 11:44:56 UTC | Type: | --- |
| 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: | 1804944 | ||
| Bug Blocks: | |||
|
Comment 4
Victor Voronkov
2020-04-20 18:46:06 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, 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 |