Instance live-migration to another host, the old vnc connection can not continue to use
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Description
===========
When instance live-migration to another host, the vnc connection will disconnect and can not continue to use.
Steps to reproduce
==================
1.build a vm
nova boot --flavor 777 --image 80c83482-
2.get vnc console
nova get-vnc-console 053763a8-
3.use novnc url to connect vm.
4.live-migration the vm
nova live-migration 053763a8-
5.the old novnc url disconnect and can not continue to use.
Expected result
===============
The old novnc url can continue to use. Users can not perceive vm live-migration.
Actual result
=============
The old novnc url can not continue to use, must to get new vnc console.
Environment
===========
1. Exact version of OpenStack you are running. See the following
Pike
2. Which hypervisor did you use?
Libvirt + KVM
3. Which networking type did you use?
Neutron with OpenVSwitch
| tags: | added: console live-migration |
| sean mooney (sean-k-mooney) wrote | #1 |
| Changed in nova: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
i have seen this several times in horizon but given this has been the case for as long as i have worked on openstack im triaging this as low as its easy to work around and while annoying does not really cause any harm or prevent people form working with guest that have been migrated.