novncproxy doesn't seem to proxy when configured in ha

Bug #1531041 reported by james beedy
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Nova Cloud Controller Charm
Invalid
Undecided
OpenStack Charmers
nova-cloud-controller (Juju Charms Collection)
Invalid
Undecided
OpenStack Charmers
nova-cloud-controller (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Openstack release: kilo
Ubuntu series: trusty

I can't seem to get a novnc console through hacluster. Also, there is no configuration for port 6080 in haproxy.cfg.
Not sure if I have something wrong, or if I have been going about it wrong all along, but I have never been able to get novnc console to work when nova-cloud-controller is deployed in ha/used in conjunction with hacluster.

haproxy.cfg: http://paste.ubuntu.com/14406962/

Revision history for this message
james beedy (jamesbeedy) wrote :
Revision history for this message
Bilal Baqar (bbaqar) wrote :

I hit something like this aswell. Which revision of nova-cloud-controller are you deploying and with what config?

Refreshing the page does the solved the problem for me but I am not sure what the real issue is.

Revision history for this message
Junaid Ali (junaidali) wrote :

this is a token issue, using memcached charm helped me out. https://bugs.launchpad.net/charms/+source/nova-cloud-controller/+bug/1550422

Ryan Beisner (1chb1n)
Changed in nova-cloud-controller (Ubuntu):
status: New → Invalid
James Page (james-page)
Changed in charm-nova-cloud-controller:
assignee: nobody → OpenStack Charmers (openstack-charmers)
Changed in nova-cloud-controller (Juju Charms Collection):
status: New → Invalid
Revision history for this message
James Page (james-page) wrote :

novnc proxy connections are not load balanced in the same way as API requests; they always go via the VIP so are routed through a single unit.

Revision history for this message
James Page (james-page) wrote :

Junaid's suggestion to use memcached in conjuction with nova-cloud-controller for token caching is valid as the backend token auth for the console still runs active/active/active on all units.

Revision history for this message
James Page (james-page) wrote :

On the assumption that this was related to the lack of use of memcached (which has the symptom of sometimes working and sometimes not) I'm going to mark this bug as 'Invalid'.

Changed in charm-nova-cloud-controller:
status: New → Invalid
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.