yahoo-eng-team team mailing list archive

[norman shen <2092465@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
Reboot nova-compute service while instance is still live migrating will leave instance state inconsistent.

Steps to reproduce
==================

1. boot an BFV instance
2. create a memory bound service in instance
3. disable post-live-migration  setting
4. do live migration
5. reboot nova-compute service

Expected result
===============
Live migration is aborted and the instance state (eg, BDM) is consistent.

Actual result
=============
BDM still stores BDM with connection info pointing to dest compute node.

Environment
===========

stable/victoria branch but should be reproduced in other release as
well.

** 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/2092465

Title:
  reboot nova-compute service while live migration could left instance
  state inconsistent

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Reboot nova-compute service while instance is still live migrating will leave instance state inconsistent.

  Steps to reproduce
  ==================

  1. boot an BFV instance
  2. create a memory bound service in instance
  3. disable post-live-migration  setting
  4. do live migration
  5. reboot nova-compute service

  Expected result
  ===============
  Live migration is aborted and the instance state (eg, BDM) is consistent.

  Actual result
  =============
  BDM still stores BDM with connection info pointing to dest compute node.

  Environment
  ===========

  stable/victoria branch but should be reproduced in other release as
  well.

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