Specify 'active' status for deleting situations
The test creates 3 backups with the rotation 2 and checks that
2 backups exist with getting its image list. test_create_backup
fails sometimes due to the existence of 3 backups.
Glance v1 delete_image API changes an image's status to 'deleted'
then the deleted flag to 'true'. If getting a list between the
status change and the delete flag change, we can get a list including
the deleting backup also like the following:
{"images": [
{"status": "deleted", "name": "backup-1-tempest-438772029",
"deleted": false, ..},
{"status": "active", "name": "backup-2-tempest-2111479443",
"deleted": false, ..},
To avoid this situation, this patch adds the status 'active' to the
calls which get the backup list.
Change-Id: I59966534a8eb1430604cada1f64b8c8df46a5f17
Closes-Bug: #1267326
diff --git a/tempest/api/compute/servers/test_server_actions.py b/tempest/api/compute/servers/test_server_actions.py
index 49d8495..fea8dd5 100644
--- a/tempest/api/compute/servers/test_server_actions.py
+++ b/tempest/api/compute/servers/test_server_actions.py
@@ -268,6 +268,7 @@
}
resp, image_list = self.os.image_client.image_list_detail(
properties,
+ status='active',
sort_key='created_at',
sort_dir='asc')
self.assertEqual(200, resp.status)
@@ -292,6 +293,7 @@
oldest_backup_exist = False
resp, image_list = self.os.image_client.image_list_detail(
properties,
+ status='active',
sort_key='created_at',
sort_dir='asc')
self.assertEqual(200, resp.status)