yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

This tells me post live migration at destination failed:

http://logs.openstack.org/43/458843/1/check/gate-tempest-dsvm-multinode-
live-migration-ubuntu-
xenial/697a501/logs/subnode-2/screen-n-cpu.txt.gz#_2017-04-21_13_54_10_281

2017-04-21 13:54:10.281 10362 ERROR nova.compute.manager [req-
7ecbf938-9e55-4e4c-b7da-63eef0f8d4a9 tempest-
LiveBlockMigrationTestJSON-208732686 tempest-
LiveBlockMigrationTestJSON-208732686] [instance: 9bf9f268-5242-4b1d-
8fe6-ee348b2b8d3e] Post live migration at destination ubuntu-xenial-2
-node-osic-cloud1-s3500-8527282 failed

Later on, the logs tell me it was successful:

http://logs.openstack.org/43/458843/1/check/gate-tempest-dsvm-multinode-
live-migration-ubuntu-
xenial/697a501/logs/subnode-2/screen-n-cpu.txt.gz#_2017-04-21_13_54_11_080

2017-04-21 13:54:11.080 10362 INFO nova.compute.manager [req-
7ecbf938-9e55-4e4c-b7da-63eef0f8d4a9 tempest-
LiveBlockMigrationTestJSON-208732686 tempest-
LiveBlockMigrationTestJSON-208732686] [instance: 9bf9f268-5242-4b1d-
8fe6-ee348b2b8d3e] Migrating instance to ubuntu-xenial-2-node-osic-
cloud1-s3500-8527282 finished successfully.

That's because we don't stop on the failure because we want to continue
with cleanup, but we don't check if we failed when emitting the success
message.

** Affects: nova
     Importance: High
     Assignee: Matt Riedemann (mriedem)
         Status: Triaged


** Tags: live-migration serviceability

** Changed in: nova
     Assignee: (unassigned) => Matt Riedemann (mriedem)

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

Title:
  compute logs tell me live migration finished successfully when it
  actually failed

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  This tells me post live migration at destination failed:

  http://logs.openstack.org/43/458843/1/check/gate-tempest-dsvm-
  multinode-live-migration-ubuntu-
  xenial/697a501/logs/subnode-2/screen-n-cpu.txt.gz#_2017-04-21_13_54_10_281

  2017-04-21 13:54:10.281 10362 ERROR nova.compute.manager [req-
  7ecbf938-9e55-4e4c-b7da-63eef0f8d4a9 tempest-
  LiveBlockMigrationTestJSON-208732686 tempest-
  LiveBlockMigrationTestJSON-208732686] [instance: 9bf9f268-5242-4b1d-
  8fe6-ee348b2b8d3e] Post live migration at destination ubuntu-xenial-2
  -node-osic-cloud1-s3500-8527282 failed

  Later on, the logs tell me it was successful:

  http://logs.openstack.org/43/458843/1/check/gate-tempest-dsvm-
  multinode-live-migration-ubuntu-
  xenial/697a501/logs/subnode-2/screen-n-cpu.txt.gz#_2017-04-21_13_54_11_080

  2017-04-21 13:54:11.080 10362 INFO nova.compute.manager [req-
  7ecbf938-9e55-4e4c-b7da-63eef0f8d4a9 tempest-
  LiveBlockMigrationTestJSON-208732686 tempest-
  LiveBlockMigrationTestJSON-208732686] [instance: 9bf9f268-5242-4b1d-
  8fe6-ee348b2b8d3e] Migrating instance to ubuntu-xenial-2-node-osic-
  cloud1-s3500-8527282 finished successfully.

  That's because we don't stop on the failure because we want to
  continue with cleanup, but we don't check if we failed when emitting
  the success message.

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