yahoo-eng-team team mailing list archive

[Joe Gordon <1290642@xxxxxxxxxxxxxxxxxx>]

Sounds like a tempest  bug not a nova bug.

** Also affects: tempest
   Importance: Undecided
       Status: New

** No longer affects: nova

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

Title:
  negative "rescue" tempest tests fail, cannot pause/rescue while
  instance is in vm_state building

Status in Tempest:
  New

Bug description:
  
  A tempest run failed several tests with errors like "Cannot 'pause' while instance is in vm_state building".  The other things tempest was trying to do is 'rescue' and 'attach_volume', and they all failed with the same error.

  Also, the error reported was "Conflict: An object with that identifier
  already exists" -- but there wasn't a conflict because an object with
  that identifier exists... it's a conflict with the state.

  Here's the tests that failed, in
  tempest.api.compute.servers.test_server_rescue_negative :

  .ServerRescueNegativeTestXML.test_rescue_paused_instance[gate,negative]
  .ServerRescueNegativeTestXML.test_rescued_vm_attach_volume[gate,negative]
  .ServerRescueNegativeTestXML.test_rescued_vm_detach_volume[gate,negative]

  n-cpu:

  2014-03-10 22:43:00.681 21160 INFO nova.virt.libvirt.driver [-] [instance: f2b64699-afc5-43f1-b3ef-868a92c08fd1] Instance spawned successfully.
  2014-03-10 22:43:00.684 DEBUG nova.compute.manager [req-f546c7d0-c320-4519-b37a-68dcd3a87783 ServerRescueNegativeTestXML-500126247 ServerRescueNegativeTestXML-1828544031] [instance: f2b64699-afc5-43f1-b3ef-868a92c08fd1] Checking state _get_power_state /opt/stack/new/nova/nova/compute/manager.py:986

  n-api:

  2014-03-10 22:43:01.193 INFO nova.api.openstack.wsgi [req-9f3d2f24
  -44af-4e0c-8e44-3289944c19d3 ServerRescueNegativeTestXML-500126247
  ServerRescueNegativeTestXML-1828544031] HTTP exception thrown: Cannot
  'pause' while instance is in vm_state building

  Looks like the request doesn't get from api to cpu, since api thinks
  it's not ready.

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