Invalid backup: Backup status must be available or error

Bug #1288038 reported by Adam Young
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Invalid
Undecided
Unassigned
tempest
Invalid
Undecided
Unassigned

Bug Description

2014-03-05 02:17:06.828 | 2014-03-05 01:57:47,279 Response Headers: {'content-length': '100', 'date': 'Wed, 05 Mar 2014 01:57:47 GMT', 'content-type': 'application/json; charset=UTF-8', 'connection': 'close', 'x-openstack-request-id': 'req-b3c28fb8-9b6e-4375-af42-5b2258ec8f0a'}
2014-03-05 02:17:06.829 | 2014-03-05 01:57:47,280 Response Body: {"badRequest": {"message": "Invalid backup: Backup status must be available or error", "code": 400}}
2014-03-05 02:17:06.829 | }}}
2014-03-05 02:17:06.829 |
2014-03-05 02:17:06.829 | traceback-1: {{{
2014-03-05 02:17:06.829 | Traceback (most recent call last):
2014-03-05 02:17:06.829 | File "tempest/services/volume/json/backups_client.py", line 62, in delete_backup
2014-03-05 02:17:06.830 | resp, body = self.delete('backups/%s' % (str(backup_id)))
2014-03-05 02:17:06.830 | File "tempest/common/rest_client.py", line 205, in delete
2014-03-05 02:17:06.830 | return self.request('DELETE', url, headers, body)
2014-03-05 02:17:06.830 | File "tempest/common/rest_client.py", line 374, in request
2014-03-05 02:17:06.830 | resp, resp_body)
2014-03-05 02:17:06.830 | File "tempest/common/rest_client.py", line 423, in _error_checker
2014-03-05 02:17:06.830 | raise exceptions.BadRequest(resp_body)
2014-03-05 02:17:06.831 | BadRequest: Bad request
2014-03-05 02:17:06.831 | Details: {u'message': u'Invalid backup: Backup status must be available or error', u'code': 400}
2014-03-05 02:17:06.831 | }}}
2014-03-05 02:17:06.831 |
2014-03-05 02:17:06.831 | Traceback (most recent call last):
2014-03-05 02:17:06.831 | File "tempest/api/volume/admin/test_volumes_backup.py", line 51, in test_volume_backup_create_get_restore_delete
2014-03-05 02:17:06.831 | 'available')
2014-03-05 02:17:06.832 | File "tempest/services/volume/json/volumes_client.py", line 164, in wait_for_volume_status
2014-03-05 02:17:06.832 | raise exceptions.TimeoutException(message)
2014-03-05 02:17:06.832 | TimeoutException: Request timed out
2014-03-05 02:17:06.832 | Details: Volume Volume-838511273 failed to reach available status within the required time (196 s).

Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

This occurred recently also -

 http://logs.openstack.org/88/123688/3/check/check-tempest-dsvm-neutron-full/6427351/logs/screen-c-api.txt

Created backup is not able to goes to 'available' state -

Traceback (most recent call last):
  File "tempest/api/volume/admin/test_volumes_backup.py", line 73, in test_volume_backup_create_get_detailed_list_restore_delete
    'available')
  File "tempest/services/volume/json/backups_client.py", line 101, in wait_for_backup_status
    raise exceptions.TimeoutException(message)
TimeoutException: Request timed out
Details: Volume backup c41d6d6f-35a0-4d2e-aa05-30ba8ecb65b2 failed to reach available status within the required time (196 s).

Needs to be looked from cinder side. I do not think there is anything for tempest.

Changed in tempest:
status: New → Invalid
Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Issue is not reproducible on the current master

Changed in cinder:
status: New → Invalid
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.