Public bug reported:
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-1c69-4cf6-b7ac-c2848e001a3e --nic
net-id=4daeddbd-be21-4a46-b23c-dcc111a3e890 --availability-zone
nova:SBCJshelf2slot13 test-novnc
2.get vnc console
nova get-vnc-console 053763a8-a86b-4779-a8d5-fea2c66e99b4 novnc
3.use novnc url to connect vm.
4.live-migration the vm
nova live-migration 053763a8-a86b-4779-a8d5-fea2c66e99b4
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
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1753880
Title:
Instance live-migration to another host, the old vnc connection can
not continue to use
Status in OpenStack Compute (nova):
New
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-1c69-4cf6-b7ac-c2848e001a3e --nic
net-id=4daeddbd-be21-4a46-b23c-dcc111a3e890 --availability-zone
nova:SBCJshelf2slot13 test-novnc
2.get vnc console
nova get-vnc-console 053763a8-a86b-4779-a8d5-fea2c66e99b4 novnc
3.use novnc url to connect vm.
4.live-migration the vm
nova live-migration 053763a8-a86b-4779-a8d5-fea2c66e99b4
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1753880/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
