Bug 1473556 - OpenShift advance installation should check for invalid characters in hostnames
OpenShift advance installation should check for invalid characters in hostnames
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.6.0
Unspecified Unspecified
unspecified Severity medium
: ---
: 3.7.0
Assigned To: Scott Dodson
Johnny Liu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-21 03:29 EDT by Javier Ramirez
Modified: 2017-07-21 08:59 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
ansible-playbook with the -vvv flag (2.26 MB, application/x-gzip)
2017-07-21 03:29 EDT, Javier Ramirez
no flags Details

  None (edit)
Description Javier Ramirez 2017-07-21 03:29:03 EDT
Created attachment 1302185 [details]
ansible-playbook with the -vvv flag

Description of problem:
When using invalid characters in hostnames, such as "-" the installer finishes and it only mention that the node failed once in the RECAP section.

Version-Release number of the following components:
# rpm -q openshift-ansible
openshift-ansible-3.5.91-1.git.0.28b3ddb.el7.noarch
# rpm -q ansible
ansible-2.2.3.0-1.el7.noarch
# ansible --version
ansible 2.2.3.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides


How reproducible:

Always

Steps to Reproduce:
1. Use an invalid character in the hostname of a node/master
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:
Installation to fail with an explicit message and installation not to finish


Additional info:
In the node that fail to register, you can find the following in the atomic-openshift-node logs:
- Jul 21 08:53:15 node35_1.example.com atomic-openshift-node[23719]: E0721 08:53:15.769185   23719 kubelet_node_status.go:98] Unable to register node "node35_1" with API server: Node "node35_1" is invalid: metadata.name: Invalid value: "node35_1": must match the regex [a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)* (e.g. 'example.com')

Note You need to log in before you can comment on or make changes to this bug.