overcloud deploy failed in "PLAY [Run Create admin]"

[Noam Angel]

overcloud deploy failed in "PLAY [Run Create admin]"

I use real physical server 3 x Dell PowerEdge R730. ironic indicate the server are active.

ansible task "Run Create admin" failed because node still on the boot up process

task does not validate that the server can be sshable

PLAY [Run Create admin] ********************************************************
11:58
11:58 TASK [Gathering Facts] *********************************************************
11:58 Thursday 16 April 2020 11:55:42 +0300 (0:00:00.153) 0:00:08.583 ********
11:58 [WARNING]: Unhandled error in Python interpreter discovery for host
11:58 192.168.24.21: Failed to connect to the host via ssh: ssh: connect to host
11:58 192.168.24.21 port 22: Connection refused
11:58
11:58 fatal: [192.168.24.21]: UNREACHABLE! => changed=false
11:58 msg: |-
11:58 Data could not be sent to remote host "192.168.24.21". Make sure this host can be reached over ssh: ssh: connect to host 192.168.24.21 port 22: Connection refused
11:58 unreachable: true
11:58 [WARNING]: Unhandled error in Python interpreter discovery for host
11:58 192.168.24.16: Failed to connect to the host via ssh: ssh: connect to host
11:58 192.168.24.16 port 22: No route to host
11:58
11:58 fatal: [192.168.24.16]: UNREACHABLE! => changed=false
11:58 msg: |-
11:58 Data could not be sent to remote host "192.168.24.16". Make sure this host can be reached over ssh: ssh: connect to host 192.168.24.16 port 22: No route to host

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/720459
Committed: https://git.openstack.org/cgit/openstack/tripleo-ansible/commit/?id=e50d06bbd07f9e7ff53cc0f31c048d36f9aad33f
Submitter: Zuul
Branch: master

commit e50d06bbd07f9e7ff53cc0f31c048d36f9aad33f
Author: Kevin Carter <email address hidden>
Date: Thu Apr 16 07:49:46 2020 -0500

    Add connection check before configuring tripleo-admin

    This change adds a connection check to the "Run create admin" playbook
    which will ensure the target host is up and ready to recieve connection
    prior to attempting to execute the rest of the playbook. This is being
    done because there is a chance servers may not be up and available by
    the time this playbook is executed and we dont want to cause a bad
    user experience by failing early, forcing the deployer to rerun a
    deployment for no reason.

    Closes-Bug: #1873246
    Change-Id: I2d2e3bdcaf0a31d8daf90656533ac0f55b70fa26
    Signed-off-by: Kevin Carter <email address hidden>