yahoo-eng-team team mailing list archive

[David Kranz <dkranz@xxxxxxxxxx>]

This looks real though there is only one hit in the past 8 days and the
log is not available. The test immediately preceding this failure has an
addCLeanUp that unrescues:

    def _unrescue(self, server_id):
        resp, body = self.servers_client.unrescue_server(server_id)
        self.assertEqual(202, resp.status)
        self.servers_client.wait_for_server_status(server_id, 'ACTIVE')


The only possibility I can see is that somehow even after nova reports ACTIVE, the rescue code thinks the server is still in the powering-off state. I am going to call this a nova issue unless some one claims the above code is not sufficient to allow a follow-on call to rescue.

** Changed in: tempest
       Status: New => Invalid

** Also 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/1361781

Title:
  bogus "Cannot 'rescue' while instance is in task_state powering-off"

Status in OpenStack Compute (Nova):
  New
Status in Tempest:
  Invalid

Bug description:
  tempest.api.compute.servers.test_server_rescue.ServerRescueTestJSON.test_rescued_vm_associate_dissociate_floating_ip
  appears flaky.  For my change that fixes some documentation, sometimes
  this test succeeds and sometimes it fails.  For an example of a
  failure, see http://logs.openstack.org/85/109385/5/check/check-
  tempest-dsvm-full/ab9c111/

  Here is the traceback from the console.html in that case:

  2014-08-26 07:29:18.804 | ==============================
  2014-08-26 07:29:18.804 | Failed 1 tests - output below:
  2014-08-26 07:29:18.805 | ==============================
  2014-08-26 07:29:18.805 | 
  2014-08-26 07:29:18.805 | tempest.api.compute.servers.test_server_rescue.ServerRescueTestJSON.test_rescued_vm_associate_dissociate_floating_ip[gate]
  2014-08-26 07:29:18.805 | --------------------------------------------------------------------------------------------------------------------------
  2014-08-26 07:29:18.805 | 
  2014-08-26 07:29:18.805 | Captured traceback:
  2014-08-26 07:29:18.805 | ~~~~~~~~~~~~~~~~~~~
  2014-08-26 07:29:18.806 |     Traceback (most recent call last):
  2014-08-26 07:29:18.806 |       File "tempest/api/compute/servers/test_server_rescue.py", line 95, in test_rescued_vm_associate_dissociate_floating_ip
  2014-08-26 07:29:18.806 |         self.server_id, adminPass=self.password)
  2014-08-26 07:29:18.806 |       File "tempest/services/compute/json/servers_client.py", line 463, in rescue_server
  2014-08-26 07:29:18.806 |         schema.rescue_server, **kwargs)
  2014-08-26 07:29:18.806 |       File "tempest/services/compute/json/servers_client.py", line 218, in action
  2014-08-26 07:29:18.806 |         post_body)
  2014-08-26 07:29:18.807 |       File "tempest/common/rest_client.py", line 219, in post
  2014-08-26 07:29:18.807 |         return self.request('POST', url, extra_headers, headers, body)
  2014-08-26 07:29:18.807 |       File "tempest/common/rest_client.py", line 431, in request
  2014-08-26 07:29:18.807 |         resp, resp_body)
  2014-08-26 07:29:18.807 |       File "tempest/common/rest_client.py", line 485, in _error_checker
  2014-08-26 07:29:18.807 |         raise exceptions.Conflict(resp_body)
  2014-08-26 07:29:18.807 |     Conflict: An object with that identifier already exists
  2014-08-26 07:29:18.808 |     Details: {u'message': u"Cannot 'rescue' while instance is in task_state powering-off", u'code': 409}
  2014-08-26 07:29:18.808 |     
  2014-08-26 07:29:18.808 | 
  2014-08-26 07:29:18.808 | Captured pythonlogging:
  2014-08-26 07:29:18.808 | ~~~~~~~~~~~~~~~~~~~~~~~
  2014-08-26 07:29:18.808 |     2014-08-26 07:05:12,251 25737 INFO     [tempest.common.rest_client] Request (ServerRescueTestJSON:test_rescued_vm_associate_dissociate_floating_ip): 409 POST http://127.0.0.1:8774/v2/690b69920c1b4a4c8d2b376ba4cb6f80/servers/9a840d84-a381-42e5-81ef-8e7cd95c086e/action 0.211s

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