Description of problem: SSL enabled undercloud doesn't configure https protocol for the ironic-inspector endpoint Version-Release number of selected component (if applicable): instack-undercloud-4.0.0-2.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy undercloud with ssl 2. openstack catalog show ironic-inspector 3. Actual results: +-----------+----------------------------------------+ | Field | Value | +-----------+----------------------------------------+ | endpoints | regionOne | | | publicURL: http://192.168.0.1:5050 | | | internalURL: http://192.168.0.1:5050 | | | adminURL: http://192.168.0.1:5050 | | | | | name | ironic-inspector | | type | baremetal-introspection | +-----------+----------------------------------------+ Expected results: publicURL: https://192.168.0.1:5050 Additional info:
I can work on this. for what releases should this be done? OSP9 and 10 or should I also backport it to OSP8?
I was finally able to reproduce this issue. And it turns out we uncovered an issue with Mistral. I have submitted a fix [1] for the mistral issue which should finally unblock this for Newton. Mitaka didn't have this issue. [1] https://review.openstack.org/#/c/349968/
Ozz - I believe that you have fixed this upstream. Has the fix been pulled into a downstream build yet? If so, please set the package N-V-R in the "Fixed In Version" field and set this bug to MODIFIED.
It hasn't been pulled downstream. It is fixed upstream, however.
[stack@undercloud-0 ~]$ openstack catalog show ironic-inspector +-----------+----------------------------------------+ | Field | Value | +-----------+----------------------------------------+ | endpoints | regionOne | | | publicURL: https://192.168.0.2:13050 | | | internalURL: http://192.168.0.1:5050 | | | adminURL: http://192.168.0.1:5050 | | | | | name | ironic-inspector | | type | baremetal-introspection | +-----------+----------------------------------------+
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2948.html