consoleauth and vncproxy in HA
Bug #1389281 reported by
Ante Karamatić
This bug report is a duplicate of:
Bug #1386271: OpenStack-dashboard consoleauth cannot validate token in HA environments.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nova-cloud-controller (Juju Charms Collection) |
New
|
Undecided
|
Unassigned |
Bug Description
When running in HA, there should be only one consoleauth and vncproxy running. Something like this needs to be present in nova-cloud-
primitive res_consoleauth upstart:
op monitor interval="5s"
primitive res_vncproxy upstart:
op monitor interval="5s"
colocation con_vip inf: res_nova_vip res_consoleauth
colocation vnc_vip inf: res_nova_vip res_vncproxy
tags: | added: cts |
tags: | added: openstack |
tags: | removed: openstack |
tags: | added: openstack |
To post a comment you must log in.
This is related to bug #1386245, the proposed approach to fix it is different though.
https:/ /bugs.launchpad .net/charms/ +source/ nova-cloud- controller/ +bug/1386245