OSP Director update fails - Certificate did not match expected hostname

Solution Verified - Updated -

Issue

  • OSP Director update fails with the following error:
2018-05-02 11:53:54,261 INFO: 2018-05-02 11:53:54 - ^[[1;31mError: /Stage[main]/Neutron::Keystone::Auth/Keystone::Resource::Service_identity[neutron]/Keystone_user[neutron]: Could not evaluate: Execution of '/bin/openstack token issue --format value' returned 1: Certificate did not match expected hostname: 0.0.0.0. Certificate: {'subjectAltName': (('DNS', '0.0.0.0'),), 'notBefore': u'May  2 14:58:12 2018 GMT', 'serialNumber': u'D8FAEC41147248F09AB3D5D678B633FF', 'notAfter': 'Dec  8 21:58:10 2018 GMT', 'version': 3L, 'subject': ((('commonName', u'0.0.0.0'),),), 'issuer': ((('commonName', u'Local Signing Authority'),), (('commonName', u'd8faec41-147248f0-9ab3d5d6-78b633fb'),))}
2018-05-02 11:53:54,262 INFO: 2018-05-02 11:53:54 - SSL exception connecting to https://0.0.0.0:13000/v3/auth/tokens: hostname '0.0.0.0' doesn't match '0.0.0.0' (tried 42, for a total of 170 seconds)^[[0m

Environment

  • Red Hat Openstack Platform 10

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content