-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
If the manisfests of a ABI cluster contain an invalid hostname the installer is able to create the image but later the installation will not start for `forbidden hostname` the allowed pattern is `^[a-z0-9][a-z0-9-]{0,62}(?:[.][a-z0-9-]{1,63})*$`
Version-Release number of selected component (if applicable):
seen in 4.19 and 4.18
How reproducible:
always
Steps to Reproduce:
1. Prepare install-config.yaml and agent-config.yaml with invalid hostname, for example with capital letters. 2. Create the ISO and confirm no errors or warning shown. 3. Start the installation and verify it stuck on validating the hosts.
Actual results:
Image is created but installation will not start causing time to troubleshoot something that can be prevented from the beginning.
Expected results:
The installer should fail in advance.
Additional info:
- relates to
-
OCPBUGS-57870 The documentation for ABI installation should mention the allowed pattern for hostnames
-
- New
-
- links to