Enabling TLS on the Overcloud - IP vs DNS Certificates

Solution Verified - Updated -

Issue

After Overcloud has been deployed, running any OpenStack command with the overcloudrc file sourced results in the following failure

(overcloud) [stack@director ~]$ openstack endpoint list
Certificate did not match expected hostname: 172.40.0.180. Certificate: {'subjectAltName': [], 'subject': ((('commonName', u'openstack.example.com),),)}
Failed to discover available identity versions when contacting https://172.40.0.180:13000//v3. Attempting to parse version from URL.
Could not determine a suitable URL for the plugin

(overcloud) [stack@director ~]$ openstack compute service list
Certificate did not match expected hostname: 172.40.0.180. Certificate: {'subjectAltName': [], 'subject': ((('commonName', u'openstack.example.com'),),)}
Failed to discover available identity versions when contacting https://172.40.0.180:13000//v3. Attempting to parse version from URL.
Could not determine a suitable URL for the plugin

Environment

Red Hat OpenStack Platform 13.0

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