yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1243614

Title:
  with ssl/tls configured novnc nova doesn't provide a https link
  without editing the config file

Status in OpenStack Compute (nova):
  Expired

Bug description:
  After configuring novnc with ssl/tls with a self-sgined http cert/key with openssl horizon still provides the http link in the novnc session. There is a setting in the config file (nova.conf) "novncproxy_base_url" that contains the full url of the vnc proxy and if it's not changed manually to https, then horizon displays a server not found error. If it is manually updated to https then it works as expected.
  I don't know if it's expected for the user to change the novncproxy_base_url by hand, but it would be convenient if it changes automatically to https when ssl/tls is configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1243614/+subscriptions