contrail status/alarm checks need to be wrapped around retry and time limit avoid timing error
Bug #1735880 reported by
wenqing liang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.0 |
Fix Committed
|
High
|
Senthilnathan Murugappan | |||
R4.1 |
Fix Committed
|
High
|
Senthilnathan Murugappan | |||
Trunk |
Fix Committed
|
High
|
Senthilnathan Murugappan |
Bug Description
Tests such as test_analytics_
2017-12-01 20:50:57,991 - INFO - start contrail-
2017-12-01 20:51:08,317 - INFO - Executing 'contrail-status' on host 10.87.118.194
2017-12-01 20:51:33,089 - INFO - Failed services are :
Host: 10.87.118.193 Container: analytics Role: analytics Service: contrail-collector: State: initializing
2017-12-01 20:51:33,089 - ERROR - All the contrail services are not up
tags: | added: sanityblocker |
summary: |
- contrail status/alarm check needs to be wrapped around retry and time + contrail status/alarm checks need to be wrapped around retry and time limit avoid timing error |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/38088
Submitter: Senthilnathan Murugappan (<email address hidden>)