yahoo-eng-team team mailing list archive

[Thiago Martins <thiagocmartinsc@xxxxxxxxx>]

Public bug reported:

Guys,

The vncserver_listen doesn't work anymore in a dual-stack setup, error:

2015-10-19 21:22:03.180 2737 ERROR nova.compute.manager [instance:
9fc58e29-41a0-44a8-aa31-1773d5cdea13] 2015-10-20T01:22:02.895921Z qemu-
system-x86_64: -vnc [::]:0: Failed to start VNC server on `(null)':
address resolution failed for [::]:5900: Name or service not known

Line in /etc/nova/nova.conf, group [vnc]:

---
vncserver_listen = ::
---

However, this very same line works on Kilo.

I'm running Liberty on Trusty, using Ubuntu Cloud Archive.

Thanks!
Thiago

** 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/1507834

Title:
  Liberty: vncserver_listen doesn't bind anymore in a dual-stack setup

Status in OpenStack Compute (nova):
  New

Bug description:
  Guys,

  The vncserver_listen doesn't work anymore in a dual-stack setup,
  error:

  2015-10-19 21:22:03.180 2737 ERROR nova.compute.manager [instance:
  9fc58e29-41a0-44a8-aa31-1773d5cdea13] 2015-10-20T01:22:02.895921Z
  qemu-system-x86_64: -vnc [::]:0: Failed to start VNC server on
  `(null)': address resolution failed for [::]:5900: Name or service not
  known

  Line in /etc/nova/nova.conf, group [vnc]:

  ---
  vncserver_listen = ::
  ---

  However, this very same line works on Kilo.

  I'm running Liberty on Trusty, using Ubuntu Cloud Archive.

  Thanks!
  Thiago

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