Description of problem: Nova novnc isn't set up to use https, which can cause issues for example when Horizon is set up to use SSL (this causes bug 1102660). When I set CONFIG_HORIZON_SSL=y in Packstack only Horizon gets set up with SSL, novnc doesn't. This causes the console to not be displayed when looking at an instance's details. This only happens when Horizon is on SSL and novnc without. Once I set up Nova to provide the VNC console with SSL (updating the baseurl etc in /etc/nova/nova.conf), it gets displayed correctly in Horizon. Version-Release number of selected component (if applicable): openstack-packstack-2014.1.1-0.13.dev1068 (from the original bug, but I was able to reproduce this with a more recent release a few weeks ago) How reproducible: 100% Steps to Reproduce: 1. Set CONFIG_HORIZON_SSL=y 2. Browse to: https://<FQDN>/dashboard/project/instances/<INSTANCE_UUID>/ Actual results: 3. The console doesn't display Expected results: 3. The console should display, and will if it is set to https Additional info: Rather than changing the component for bug 1102660, I thought it'd be easier to open a new bug to make the actual issue clearer rather than lost in the history.
*** Bug 1116903 has been marked as a duplicate of this bug. ***
Failed QA ========= The console doesn't display openstack-packstack-puppet-2014.1.1-0.41.dev1251.el7ost.noarch
Moving to A2 unless this is a regression?
Agreed, this is not a regression.
The bug reproduced on: openstack-packstack-puppet-2014.2-0.4.dev1266.g63d9c50.el7.centos.noarch Aditional info: =============== When changing the URL from https://<FQDN>/dashboard/project/instances/<INSTANCE_UUID>/ to http://<FQDN>/dashboard/project/instances/<INSTANCE_UUID>/ the console is opend. Is it additional bug? a security bug?
Failed QA ========= The console doesn't display Failed to connect to server (code: 1006)
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Verified ======== openstack-packstack-2014.1.1-0.48.dev1289.el7ost.noarch
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/RHBA-2015-1746.html