Created attachment 1318341 [details] Firefox "secure connection failed" snapshot Description of problem: Get the error Version-Release number of selected component (if applicable): OSP 10, 11, 12 How reproducible: Use a browser on Mac OS X El Capitan (10.11.6) Browsers used were (1) Chrome 54.0.2840.98 (64-bit) (2) Firefox 52.3.0 Firefox Extended Support Release ESR Try to open URL for undercloud install Steps to Reproduce: 1. 2. 3. Actual results: See attachments below from Chrome and Firefox - with certificate error messages Expected results: Additional info:
Created attachment 1318344 [details] Chrome "Your connection is not secure" screenshot
From dtrainor "I was looking at the SSL certificate used[0] and it doesn't have a Subject Alternative Name for the system, which I understand Chrome on OSX now requires. That's what is going to prevent this from working. As it is right now, however, it does work on other browsers on other platforms - for example, I have no problems with this using Chrome 60 on Fedora - weird. When you open a bug, you can reference this link[1] for more information. We need to add an additional value (the VIP, or 8.43.87.242), to the SubjectAltName value of the certificate. This needs to happen automatically as part of the Undercloud install. Since the Undercloud won't know what this IP should be, it probably needs to be specified as an install-time parameter, perhaps in the undercloud.conf file prior to 'openstack undercloud install'. " --- [0] http://paste.openstack.org/show/619087/ [1] https://www.thesslstore.com/blog/security-changes-in-chrome-58/
Well, the autogenerated certificate has been using a subjectaltname for a while. Checking it, it seems to be in OSP10 as well. What is this error reported for? the undercloud or the overcloud? If it's the overcloud, we do expect folks to generate their own certificates; perhaps what should be fixed is the documentation where it gives an example of how to generate a certificate, and we should include setting up a SubjectAltName there.
Uhm... If it's the undercloud, I think it might be related to this bug https://bugzilla.redhat.com/show_bug.cgi?id=1445580
The error occurred in the undercloud
Closing this as a duplicate or RHBZ#1445580[1]. [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1445580 *** This bug has been marked as a duplicate of bug 1445580 ***