Check alarm state just after the PUT
This reduces the chance to have Aodh evaluator to changing our alarm
state between our PUT and GET.
Change-Id: I6ceeb9b605c50a54116ff3bfdd9673bfd5beeccf
diff --git a/telemetry_tempest_plugin/integration/gabbi/gabbits-live/aodh-gnocchi-threshold-alarm.yaml b/telemetry_tempest_plugin/integration/gabbi/gabbits-live/aodh-gnocchi-threshold-alarm.yaml
index 65b00e9..9349295 100644
--- a/telemetry_tempest_plugin/integration/gabbi/gabbits-live/aodh-gnocchi-threshold-alarm.yaml
+++ b/telemetry_tempest_plugin/integration/gabbi/gabbits-live/aodh-gnocchi-threshold-alarm.yaml
@@ -218,6 +218,15 @@
response_strings:
- "ok"
+ - name: get alarm state for 'gabbi-gnocchi-threshold-resource-alarm'
+ desc: get state for alarm
+ GET: $URL
+ request_headers:
+ content-type: application/json
+ status: 200
+ response_strings:
+ - "ok"
+
- name: search 'gabbi-gnocchi-threshold-resource-alarm' alarm exist
desc: search for alarm using user_id, project_id, alarm_name
GET: $ENVIRON['AODH_SERVICE_URL']/v2/alarms
@@ -252,15 +261,6 @@
$.gnocchi_resources_threshold_rule.resource_type: "ceph_account"
$.user_id: c8ecb587-d38c-426f-a58d-22b8d4a9a1d3
- - name: get alarm state for 'gabbi-gnocchi-threshold-resource-alarm'
- desc: get state for alarm
- GET: $ENVIRON['AODH_SERVICE_URL']/v2/alarms/$RESPONSE['$.alarm_id']/state
- request_headers:
- content-type: application/json
- status: 200
- response_strings:
- - "ok"
-
#
# Teardown
#