nova-spiceproxy ignores spicehtml5proxy_host setting = "::"

Bug #1308418 reported by Thiago Martins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Vladik Romanovsky

Bug Description

Hello Stackers!

I'm trying SPICE Consoles and it is working smoothly! But, I detected a problem, it is ignoring the entry "spicehtml5proxy_host" in nova.conf for Dual-Stacked environment (IPv4 / IPv6).

So, it isn't listening on "::".

The following setup doesn't work....

---
[spice]
enabled = True
spicehtml5proxy_host = ::
html5proxy_base_url = http://controller.yourdomain.com:6082/spice_auto.html
keymap = en-us
---

Unless I patch the following file:

/usr/lib/python2.7/dist-packages/nova/cmd/spicehtml5proxy.py into this:

---
opts = [
    cfg.StrOpt('spicehtml5proxy_host',
               default='::',
               help='Host on which to listen for incoming requests'),
---

As you guys can see, I replaced the default "0.0.0.0" to "::" and now SPICE Proxy listens on both IPv4 and IPv6! But, this is a hack...

I don't know why it is ignoring the "spicehtml5proxy_host = ::" entry at nova.conf.

BTW, the "novncproxy_host = ::" works as expected for NoVNC but, I'm disabling VNC from my cloud in favor of SPICE.

Cheers!
Thiago

Tags: console
Thiago Martins (martinx)
summary: - nova-spiceproxy ignores spicehtml5proxy_host setting
+ nova-spiceproxy ignores spicehtml5proxy_host setting = "::"
Tracy Jones (tjones-i)
tags: added: console
Changed in nova:
assignee: nobody → Vladik Romanovsky (vladik-romanovsky)
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/88607

Changed in nova:
status: New → In Progress
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/88607
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fe02cc830f9c9e1dac234164bc1f0caa0e2072d7
Submitter: Jenkins
Branch: master

commit fe02cc830f9c9e1dac234164bc1f0caa0e2072d7
Author: Vladik Romanovsky <email address hidden>
Date: Fri Apr 18 15:14:46 2014 +0000

    Spice proxy config setting to be read from the spice group in nova.conf

    All spice configuration should be read from the spice group
    in the nova config. As it's currently being done in the nova.spice
    module.
    Renaming spicehtml5proxy_{host, port} parameters to
    html5proxy_{host, port}

    DocImpact
    Change-Id: I36c014c8b8a0796cda494f9450a1fc30104504a1
    Closes-Bug: #1308418

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → juno-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: juno-1 → 2014.2
Revision history for this message
Thiago Martins (martinx) wrote :

Hi!

This problem still exists on Juno 2014.2, look:

---
root@controller-1:~# netstat -natup | grep 6082
tcp 0 0 0.0.0.0:6082 0.0.0.0:* LISTEN 7182/python

root@controller-1:~# sed -i 's/0.0.0.0/::/' /usr/lib/python2.7/dist-packages/nova/cmd/spicehtml5proxy.py

root@controller-1:~# service nova-spiceproxy restart
nova-spiceproxy stop/waiting
nova-spiceproxy start/running, process 7234

root@controller-1:~# netstat -natup | grep 6082
tcp6 0 0 :::6082 :::* LISTEN 7234/python
---

---
root@psuaa-1:~# dpkg -l | grep -i nova-spiceproxy
ii nova-spiceproxy 1:2014.2-0ubuntu1~cloud0 all OpenStack Compute - spice html5 proxy
---

I'm using:

---
add-apt-repository ppa:ubuntu-cloud-archive/juno-staging
---

...with Trusty.

What am I missing?

Tks!
Thiago

Revision history for this message
Thiago Martins (martinx) wrote :

Sorry, I forgot to edit one... s/psuaa/controller/

=P

Revision history for this message
Vladik Romanovsky (vladik-romanovsky) wrote :

Did you add html5proxy_{host, port} under the [Spice] section in the /etc/nova/nova.conf ?

The name of the setting has been changed from spicehtml5proxy_{host, port} to html5proxy_{host, port}

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.