← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1240584] Re: instance migration action shouldn't be allowed when there are existed VNC sessions

 

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
       Status: Confirmed => Expired

-- 
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/1240584

Title:
  instance migration action shouldn't be allowed when there are existed
  VNC sessions

Status in OpenStack Compute (nova):
  Expired

Bug description:
  instance migration action shouldn't be allowed when there are existed VNC sessions .
  when doing a migration, all vnc tokens will become invalid from the source server. this breaks the existed VNC session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1240584/+subscriptions