nova-novncproxy not uses memcached in HA deployment
Bug #1343951 reported by
Roman Sokolkov
This bug report is a duplicate of:
Bug #1323705: Instance VNC console can't connect on the first attempt.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
VNC console not working within HA deployment, because multiple copies of nova-noconsoleauth started without memcache.
Environment:
- Fuel 5.0
- HA on Ubuntu
How to reproduce:
- Create HA environment on Ubuntu (Was on CentOS also)
- Create instance in OpenStack
- Try to open VNC console via Horizon
Expected result:
- VNC console working
Actual result:
- VNC console fails with error
Solution:
Add to nova.conf (all controllers)
memcached_
Restart nova-consoleauth
| Changed in fuel: | |
| milestone: | none → 5.0.1 |
| status: | New → Fix Committed |
To post a comment you must log in.
