[R3.2 #19]Alarm service reports as active with rabbit inacccessible
Bug #1672506 reported by
Jeff Fischer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
Medium
|
Sundaresan Rajangam | |||
R3.0.2.x |
Won't Fix
|
Medium
|
Sundaresan Rajangam | |||
R3.0.3.x |
Fix Committed
|
Medium
|
Sundaresan Rajangam | |||
R3.1 |
Fix Committed
|
Medium
|
Sundaresan Rajangam | |||
R3.1.1.x |
Fix Committed
|
Medium
|
Sundaresan Rajangam | |||
R3.2 |
Fix Committed
|
Medium
|
Sundaresan Rajangam | |||
Trunk |
Fix Committed
|
Medium
|
Sundaresan Rajangam |
Bug Description
Contrail status is reporting the alarm service as active even though it is non-functional. It was not functioning because the correct rabbitmq_user and rabbitmq_password were not configured in contrail-
tags: | added: analytics |
Changed in juniperopenstack: | |
importance: | Undecided → Medium |
assignee: | nobody → Sundaresan Rajangam (srajanga) |
To post a comment you must log in.
Fixed in mainline by https:/ /github. com/Juniper/ contrail- controller/ commit/ 8e176a09a0a32da 39a7de0f18c7bf1 863565b2cf