(undercloud) [stack@undercloud-0 ~]$ openstack stack failures list --long overcloud -v START with options: [u'stack', u'failures', u'list', u'--long', u'overcloud', u'-v'] command: stack failures list -> heatclient.osc.v1.stack_failures.ListStackFailures (auth=True) Using auth plugin: password /usr/lib/python2.7/site-packages/requests/packages/urllib3/connection.py:303: SubjectAltNameWarning: Certificate for 192.168.24.2 has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.) SubjectAltNameWarning overcloud.AllNodesDeploySteps.ControllerDeployment_Step3.0: resource_type: OS::Heat::StructuredDeployment physical_resource_id: 0cd02244-9053-4f5f-a022-a01120c35a20 status: CREATE_FAILED status_reason: | CREATE aborted deploy_stdout: | None deploy_stderr: | None END return value: 0 (undercloud) [stack@undercloud-0 ~]$ sudo cat /var/log/messages | grep "SQL connection failed" Sep 4 08:02:13 undercloud-0 ironic-inspector: 2017-09-04 08:02:13.160 1309 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 10 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on '192.168.24.1' ([Errno 111] ECONNREFUSED)") docker-registry.engineering.redhat.com/rhosp12/ v - 2017-08-31.2
The two bugs manifest the same but I don't think the root cause is the identical as in the issue reported upstream in LP#1715029. In your case I can see an error when trying to generate the configuration file for haproxy: 'bind 10.0.0.101:13005' : unable to load SSL private key from PEM file '/etc/pki/tls/private/overcloud_endpoint.pem' I'm leaning toward a duplicate of bug 1486363.
*** This bug has been marked as a duplicate of bug 1486363 ***