HARD reboot failed 'operation time out'

Bug #1290081 reported by Attila Fazekas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
New
Undecided
Unassigned

Bug Description

http://logs.openstack.org/43/76643/2/check/check-tempest-dsvm-postgres-full/f0dc486/logs/screen-n-cpu.txt.gz?#_2014-03-07_21_40_48_264
http://logs.openstack.org/43/76643/2/check/check-tempest-dsvm-postgres-full/f0dc486/console.html.gz#_2014-03-07_22_05_12_857

http://logs.openstack.org/43/76643/2/check/check-tempest-dsvm-postgres-full/f0dc486/logs/screen-n-cpu.txt.gz?#_2014-03-07_21_41_20_665
"Cannot reboot instance: Failed to power off instance: operation time out"

http://logs.openstack.org/43/76643/2/check/check-tempest-dsvm-postgres-full/f0dc486/logs/screen-n-cpu.txt.gz?#_2014-03-07_21_41_21_331
"InstancePowerOffFailure: Failed to power off instance: operation time out"

2014-03-07 22:05:12.889 | 2014-03-07 21:41:21,711 State transition "HARD_REBOOT/rebooting_hard" ==> "ERROR/None" after 33 second wait
2014-03-07 22:05:12.889 | }}}
2014-03-07 22:05:12.889 |
2014-03-07 22:05:12.889 | Traceback (most recent call last):
2014-03-07 22:05:12.889 | File "tempest/api/compute/servers/test_server_actions.py", line 332, in test_get_console_output
2014-03-07 22:05:12.890 | self.servers_client.wait_for_server_status(self.server_id, 'ACTIVE')
2014-03-07 22:05:12.890 | File "tempest/services/compute/xml/servers_client.py", line 368, in wait_for_server_status
2014-03-07 22:05:12.890 | raise_on_error=raise_on_error)
2014-03-07 22:05:12.890 | File "tempest/common/waiters.py", line 74, in wait_for_server_status
2014-03-07 22:05:12.890 | raise exceptions.BuildErrorException(server_id=server_id)
2014-03-07 22:05:12.890 | BuildErrorException: Server 74aaf889-1f9f-4f9d-b178-6dc733052ca5 failed to build and is in ERROR status

Logstash Query:
message: "InstancePowerOffFailure" AND filename:"logs/screen-n-cpu.txt"

91% FAILED

Revision history for this message
Darragh O'Reilly (darragh-oreilly) wrote :
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.