yahoo-eng-team team mailing list archive

[Radomir Dopieralski <1536589@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

If during live migration the connection to nova conductor service is
somehow lost (for instance, due to the rabbitmq server becoming
unavailable), the migration status of the nodes never gets updated, and
they end up forever in "migrating" state, with the actual guest already
running on the new host, but the data in the nova database still
pointing at the old host.

This happens in all versions at lest up to Mitaka.

How to reproduce:
1. Create a simple setup with two hosts.
2. Create an instance and start a live migration.
3. Kill the rabbitmq server.
4. Wait for the migration to finish.
5. Bring the rabbitmq server back up.
6. Observe the instance stuck in "migrating" state, with everything migrated to the new host, but Nova thinking it's still on the old host.

** Affects: nova
     Importance: Undecided
     Assignee: Radomir Dopieralski (thesheep)
         Status: New

** Description changed:

  If during live migration the connection to nova conductor service is
  somehow lost (for instance, due to the rabbitmq server becoming
  unavailable), the migration status of the nodes never gets updated, and
  they end up forever in "migrating" state, with the actual guest already
  running on the new host, but the data in the nova database still
  pointing at the old host.
  
  This happens in all versions at lest up to Mitaka.
  
  How to reproduce:
  1. Create a simple setup with two hosts.
  2. Create an instance and start a live migration.
  3. Kill the rabbitmq server.
  4. Wait for the migration to finish.
  5. Bring the rabbitmq server back up.
- 6. Observe the instance stuck in "migrating" state, with everything migrated o the new host, but Nova thinking it's still on the old host.
+ 6. Observe the instance stuck in "migrating" state, with everything migrated to the new host, but Nova thinking it's still on the old host.

** Changed in: nova
     Assignee: (unassigned) => Radomir Dopieralski (thesheep)

** Summary changed:

- Inconsistent state if connection to conductor is lost during live migration
+ Inconsistent state when connection to conductor is lost during live migration

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

Title:
  Inconsistent state when connection to conductor is lost during live
  migration

Status in OpenStack Compute (nova):
  New

Bug description:
  If during live migration the connection to nova conductor service is
  somehow lost (for instance, due to the rabbitmq server becoming
  unavailable), the migration status of the nodes never gets updated,
  and they end up forever in "migrating" state, with the actual guest
  already running on the new host, but the data in the nova database
  still pointing at the old host.

  This happens in all versions at lest up to Mitaka.

  How to reproduce:
  1. Create a simple setup with two hosts.
  2. Create an instance and start a live migration.
  3. Kill the rabbitmq server.
  4. Wait for the migration to finish.
  5. Bring the rabbitmq server back up.
  6. Observe the instance stuck in "migrating" state, with everything migrated to the new host, but Nova thinking it's still on the old host.

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