Comment 2 for bug 1805506

Revision history for this message
Lisa Li (lisali) wrote :

From http://logs.openstack.org/87/609587/11/check/tempest-multinode-full/d4ec462/testr_results.html.gz
It calls restore_volume, and checks status of backup to finish in 196s.

Details: backup a52fcd04-469a-4995-bba8-15bba439756a failed to reach available status (current restoring) within the required time (196 s).

Actual results: The restore tasks took about 4 minutes.
Nov 28 06:36:39.667634 ubuntu-xenial-ovh-bhs1-0000752678 cinder-backup[1888]: INFO cinder.backup.manager [None req-b6bfaf94-4142-40bb-a0f6-f6ddc850a921 tempest-VolumesBackupsTest-1683650084 None] Restore backup started, backup: a52fcd04-469a-4995-bba8-15bba439756a volume: 814cfd25-5d78-43ba-a987-af392587eb2b.
Nov 28 06:40:31.185456 ubuntu-xenial-ovh-bhs1-0000752678 cinder-backup[1888]: INFO cinder.backup.manager [None req-b6bfaf94-4142-40bb-a0f6-f6ddc850a921 tempest-VolumesBackupsTest-1683650084 None] Finished restoring backup a52fcd04-469a-4995-bba8-15bba439756a to volume 814cfd25-5d78-43ba-a987-af392587eb2b.