RFE: verify specific sequence of monitoring events

Bug #1621592 reported by Sridhar Ramaswamy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
In Progress
Low
tamil vanan

Bug Description

Follow up to the comment left in [1].

Monitoring func tests currently just verifies the presence of this events like ACTION and DEAD. This needs to be enhanced to the exact timestamp sorted sequence of events like ACTIVE -> DEAD -> ACTIVE.

[1] https://review.openstack.org/#/c/366226/5/tacker/tests/functional/vnfm/test_vnf_monitoring.py@52

Tags: rfe
Changed in tacker:
importance: Undecided → Low
tamil vanan (tamilhce)
Changed in tacker:
assignee: nobody → tamil vanan (tamilhce)
Revision history for this message
tamil vanan (tamilhce) wrote :

Hi Sridhar, we need to add timestamp to check the event sequence in the below function

https://github.com/openstack/tacker/blob/master/tacker/tests/functional/base.py#L133

right ?

tamil vanan (tamilhce)
Changed in tacker:
status: New → In Progress
Revision history for this message
tamil vanan (tamilhce) wrote :

when i sort the timestamp against resource_state, I am getting following o/ps ( some portion of actual output)

2016-09-09 11:40:36 PENDING_CREATE
2016-09-09 11:40:36 PENDING_CREATE
2016-09-09 11:40:37 PENDING_CREATE
2016-09-09 11:40:37 PENDING_CREATE
2016-09-09 11:41:14 PENDING_CREATE
2016-09-09 11:41:14 ACTIVE
2016-09-09 11:41:17 PENDING_DELETE
2016-09-09 11:41:23 PENDING_CREATE
2016-09-09 11:41:23 ACTIVE
2016-09-09 11:41:24 PENDING_CREATE
2016-09-09 11:41:24 ACTIVE
2016-09-09 11:41:24 PENDING_DELETE
2016-09-09 11:41:25 PENDING_DELETE
2016-09-09 11:41:30 PENDING_DELETE
2016-09-09 11:41:30 PENDING_CREATE
2016-09-09 11:41:30 ACTIVE
2016-09-09 11:41:34 PENDING_CREATE
2016-09-09 11:41:34 PENDING_DELETE
2016-09-09 11:41:43 PENDING_DELETE
2016-09-09 11:41:43 PENDING_DELETE
2016-09-09 11:41:44 PENDING_CREATE
2016-09-09 11:41:44 PENDING_CREATE
2016-09-09 11:41:46 PENDING_DELETE
2016-09-09 11:41:48 PENDING_CREATE
2016-09-09 11:42:01 PENDING_CREATE
2016-09-09 11:42:01 ACTIVE
2016-09-09 11:42:03 PENDING_DELETE
2016-09-09 11:42:27 PENDING_DELETE
2016-09-09 11:42:30 PENDING_CREATE
2016-09-09 11:42:35 PENDING_CREATE
2016-09-09 11:42:35 ACTIVE
2016-09-09 11:42:40 PENDING_DELETE
2016-09-09 11:42:52 PENDING_CREATE
2016-09-09 11:42:52 ACTIVE
2016-09-09 11:42:53 PENDING_DELETE
2016-09-09 11:42:57 PENDING_CREATE
2016-09-09 11:42:57 ACTIVE
2016-09-09 11:43:00 PENDING_DELETE
2016-09-09 11:43:04 PENDING_DELETE
2016-09-09 11:43:04 PENDING_CREATE
2016-09-09 11:43:07 PENDING_DELETE
2016-09-09 11:43:08 PENDING_CREATE
2016-09-09 11:43:26 PENDING_CREATE
2016-09-09 11:43:26 ACTIVE
2016-09-09 11:43:28 PENDING_DELETE
2016-09-09 11:43:30 PENDING_DELETE
2016-09-09 11:43:32 PENDING_CREATE
2016-09-09 11:43:35 PENDING_CREATE
2016-09-09 11:43:35 ACTIVE
2016-09-09 11:43:35 ACTIVE
2016-09-09 11:43:41 PENDING_DELETE
2016-09-09 11:43:42 PENDING_CREATE
2016-09-09 11:43:55 PENDING_CREATE
2016-09-09 11:43:55 ACTIVE
2016-09-09 11:43:56 PENDING_CREATE
2016-09-09 11:43:56 ACTIVE
2016-09-09 11:43:56 ACTIVE
2016-09-09 11:43:58 PENDING_DELETE
2016-09-09 11:44:16 PENDING_DELETE
2016-09-09 11:44:34 PENDING_CREATE
2016-09-09 11:44:34 ACTIVE
2016-09-09 11:44:34 ACTIVE
2016-09-09 11:46:01 DEAD

I have few doubts,
The flow should be PENDING_CREATE --> ACTIVE --> PENDING_DELETE --> DEAD
I could see following state in timestamp that PENDING_DELETE followed by PENDING_CREATE, there is No DEAD state in between

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.