← Back to team overview

sws team mailing list archive

[Bug 908556] Re: vncproxy returns hostname instead of hostip

 

*** This bug is a duplicate of bug 918451 ***
    https://bugs.launchpad.net/bugs/918451

** This bug has been marked a duplicate of bug 918451
   VNC proxy target host should be configurable

-- 
You received this bug notification because you are a member of SWS,
which is a bug assignee.
https://bugs.launchpad.net/bugs/908556

Title:
  vncproxy returns hostname instead of hostip

Status in OpenStack Compute (Nova):
  New

Bug description:
  Currently the VNC console functionality on Horizon needs a work around
  since VNCNovaAuthMiddleware is returning the hostname instead of the
  host IP to websocket.js.

  The reason is because the 'host' column in the 'instances' table
  defaults to socket.gethostname() if the --host flag is an empty
  string.

  If the server which is running vncproxy has a alias of hostnames in
  its /etc/hosts file, it works fine.

  Without the alias, the vncproxy cannot forward the browser to the
  compute node which the vm instance is running.

  You could set the --host to the compute node IP in every conf file but
  it would be better if 'host' could default to $my_ip when deploying to
  many machines.

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