discovery: control service not marked down
Bug #1636372 reported by
Senthilnathan Murugappan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.0 |
Fix Committed
|
Medium
|
Senthilnathan Murugappan | |||
| R3.0.3.x |
New
|
Medium
|
Senthilnathan Murugappan | |||
| R3.1 |
Fix Committed
|
Medium
|
Senthilnathan Murugappan | |||
| R3.2 |
Fix Committed
|
Medium
|
Senthilnathan Murugappan | |||
| Trunk |
Fix Committed
|
Medium
|
Senthilnathan Murugappan | |||
Bug Description
Sanity testcase: test_control_
Build: R3.0.3.x-3 (Kilo)
All the three control-node processes were brought down and the services were moved to red but still their oper-state is up.
Please refer attachment for /services output
Revision history for this message
| Senthilnathan Murugappan (msenthil) wrote | #1 |
| Changed in juniperopenstack: | |
| assignee: | nobody → Deepinder Setia (dsetia) |
| tags: | added: discovery sanity |
| information type: | Proprietary → Public |
Revision history for this message
| Senthilnathan Murugappan (msenthil) wrote | #2 |
| tags: |
added: automation removed: discovery |
| summary: |
- discovery: control service not marked down even after 10 mins + discovery: control service not marked down |
To post a comment you must log in.
The hc_miss has been increased from 15 secs to 35 secs in the latest code.
The script has to be updated to reflect it.