yahoo-eng-team team mailing list archive

[Loganathan Parthipan <1425178@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The novncproxy.py was refactored and baseproxy was introduced sometime
back in patch https://review.openstack.org/#/c/119396/.

But because the config files are not resolved in novncproxy anymore, the
baseproxy is passed with default values for novncproxy_host and
novncproxy_port. Overrides in config files such as nova.conf will not
have any effects.

This is not good if you want to make novnc listen on different
interfaces/port, a specific use-case being stunnel TLS termination.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1425178

Title:
  novncproxy refactoring removes configurability of host and port

Status in OpenStack Compute (Nova):
  New

Bug description:
  The novncproxy.py was refactored and baseproxy was introduced sometime
  back in patch https://review.openstack.org/#/c/119396/.

  But because the config files are not resolved in novncproxy anymore,
  the baseproxy is passed with default values for novncproxy_host and
  novncproxy_port. Overrides in config files such as nova.conf will not
  have any effects.

  This is not good if you want to make novnc listen on different
  interfaces/port, a specific use-case being stunnel TLS termination.

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