Created attachment 1427985 [details] installation log with inventory file embedded Description of problem: see the following details Version-Release number of the following components: openshift-ansible-3.10.0-0.30.0.git.0.4f02952.el7.noarch How reproducible: Always Steps to Reproduce: 1. launch an instance, its hostname is "test" 2. prepare inventory file, setting openshift_hostname="aa.bb.com" to overwrite its hostname for this node, which is resolved to this instance's IP. 3. trigger installation Actual results: After installation, run `oc get node`, the node is registered as "test", but not "aa.bb.com". # grep -i nodename /etc/origin/node/node-config.yaml Expected results: node should be registered as "aa.bb.com" Additional info: I track down a bit for this issue, node start script is located at /usr/local/bin/openshift-node, in which there are the following line: flags=$( /usr/bin/openshift start node --write-flags "--config=${config}" --loglevel=${DEBUG_LOGLEVEL:-2} ) seem like the command never prints out "nodeName" flag, even if I manually added "nodeName" into node-config file.
nodeName is no longer configurable, what problems arrise from the new behavior?
If nodeName is no longer configurable, node host will use its hostname to registry itself, if node's hostname is not resolvable, that would lead to the node can not succeed to registry itself. Such as: master + node1: hostname is "test" node2: hostname is "test1" "test" and "test1" is not resolvable between hosts, only resolvable on node itself. Then after installation, run `oc get node`, only "test" is listed there, "test1" is missing. BTW, if nodeName is no longer configurable, doc also have to be updated accordingly.
see https://bugzilla.redhat.com/show_bug.cgi?id=1566455#c10
*** This bug has been marked as a duplicate of bug 1566455 ***
I do not think this is not a dup of bug 1566455, this bug is tracking for openshift_hostname overwrite issue which is irrelevant to any cloud provider, bug 1566455 is tracking for openshift cloudprovider issue. Just like the scenario what I mentioned in comment 2, if we insist nodeName is no longer configurable, to make the installation mentioned in comment 2 move on, user have to change system hostname to some resolvable fdqn. This bug should be move to a doc bug to explain such scenario and remove all the occurrence where mention "nodeName" and ""openshift_hostname".
Docs PR: https://github.com/openshift/openshift-docs/pull/9744
Seem like no update for nodeName in the doc, now nodeName is not configurable and not shown in node config yaml file.
Updated to remove nodeName from node-config.yaml as well: https://github.com/openshift/openshift-docs/pull/9744
Search cross the whole doc, seem like still have some place using reference to "openshift_hostname", such as: https://github.com/openshift/openshift-docs/search?q=openshift_hostname&unscoped_q=openshift_hostname
Also some place using reference to "nodeName", such as: https://github.com/openshift/openshift-docs/blob/fc7e0480b0c305f560f6f2d9e48a4e99071ae8da/install_config/configuring_openstack.adoc https://github.com/openshift/openshift-docs/blob/42162d76800d78969754566ea6f02d795fc92fec/install_config/configuring_vsphere.adoc https://github.com/openshift/openshift-docs/blob/fc7e0480b0c305f560f6f2d9e48a4e99071ae8da/install_config/configuring_gce.adoc https://github.com/openshift/openshift-docs/blob/fc7e0480b0c305f560f6f2d9e48a4e99071ae8da/install_config/configuring_aws.adoc
@Alex - I am closing this in favor of the new one that was reported - and is being worked on by Kathryn. *** This bug has been marked as a duplicate of bug 1613765 ***