Comment 10 for bug 1483434

Revision history for this message
Matt Riedemann (mriedem) wrote :

Different test, similar failure here:

http://logs.openstack.org/55/569055/7/gate/nova-next/2e23975/job-output.txt.gz#_2018-11-13_12_06_04_534310

2018-11-13 12:06:04.534310 | primary | {3} tempest.api.volume.admin.test_volumes_backup.VolumesBackupsAdminTest.test_volume_backup_export_import [267.653158s] ... FAILED
2018-11-13 12:06:04.534400 | primary |
2018-11-13 12:06:04.534442 | primary | Captured traceback:
2018-11-13 12:06:04.534474 | primary | ~~~~~~~~~~~~~~~~~~~
2018-11-13 12:06:04.534534 | primary | Traceback (most recent call last):
2018-11-13 12:06:04.534609 | primary | File "tempest/api/volume/admin/test_volumes_backup.py", line 115, in test_volume_backup_export_import
2018-11-13 12:06:04.534666 | primary | self.backups_client, backup['id'], 'available')
2018-11-13 12:06:04.534725 | primary | File "tempest/common/waiters.py", line 211, in wait_for_volume_resource_status
2018-11-13 12:06:04.534783 | primary | raise lib_exc.TimeoutException(message)
2018-11-13 12:06:04.534838 | primary | tempest.lib.exceptions.TimeoutException: Request timed out
2018-11-13 12:06:04.534939 | primary | Details: backup afcc4b27-ae1a-4de2-a254-2e4ea3debd52 failed to reach available status (current restoring) within the required time (196 s).