Nova doesn't update vnc listen address during migration with libvirt
Bug #1262450 reported by
Dmitry Borodaenko
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Solly Ross |
Bug Description
Nova should update VNC listen address in libvirt.xml to the destination node's vncserver_listen setting on completing migration. Without that, the only way to make VMs accessible over VNC after migration is to set vncserver_listen to 0.0.0.0 as recommended in:
which is a suboptimal solution from security standpoint.
Changed in nova: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
you may config vncserver_ listen= 127.0.0. 1 to solve this issue.