test_reboot_server_hard fails sporadically in swift check jobs

Bug #1258319 reported by Peter Portante
This bug report is a duplicate of:  Bug #1014647: Tempest has no test for soft reboot. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
New
Undecided
Unassigned

Bug Description

test_reboot_server_hard fails sporadically in swift check jobs

I believe this has been reported before, but I was not able to find it.

See: http://logs.openstack.org/43/60343/1/gate/gate-tempest-dsvm-full/c92d206/console.html

2013-12-05 21:29:18.174 | ======================================================================
2013-12-05 21:29:18.183 | FAIL: tempest.api.compute.servers.test_server_actions.ServerActionsTestXML.test_reboot_server_hard[gate,smoke]
2013-12-05 21:29:18.186 | tempest.api.compute.servers.test_server_actions.ServerActionsTestXML.test_reboot_server_hard[gate,smoke]
2013-12-05 21:29:18.200 | ----------------------------------------------------------------------
2013-12-05 21:29:18.206 | _StringException: Empty attachments:
2013-12-05 21:29:18.206 | stderr
2013-12-05 21:29:18.207 | stdout
2013-12-05 21:29:18.207 |
2013-12-05 21:29:18.207 | pythonlogging:'': {{{

.
.
.

2013-12-05 21:29:19.174 | Traceback (most recent call last):
2013-12-05 21:29:19.175 | File "tempest/api/compute/servers/test_server_actions.py", line 83, in test_reboot_server_hard
2013-12-05 21:29:19.175 | self.client.wait_for_server_status(self.server_id, 'ACTIVE')
2013-12-05 21:29:19.175 | File "tempest/services/compute/xml/servers_client.py", line 369, in wait_for_server_status
2013-12-05 21:29:19.175 | extra_timeout=extra_timeout)
2013-12-05 21:29:19.176 | File "tempest/common/waiters.py", line 82, in wait_for_server_status
2013-12-05 21:29:19.176 | raise exceptions.TimeoutException(message)
2013-12-05 21:29:19.176 | TimeoutException: Request timed out
2013-12-05 21:29:19.177 | Details: Server f313af9a-8ec1-4f77-b63f-76d9317d6423 failed to reach ACTIVE status within the required time (196 s). Current status: HARD_REBOOT.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.