No disable reason defined for new services when "enable_new_services=False"
Bug #1417027 reported by
Belmiro Moreira
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Belmiro Moreira |
Bug Description
When a service is added and "enable_
reason specified.
Services can be disabled by several reasons and the admins can use the API to
specify a reason. However, having services disabled with no reason specified
creates additional checks on the operators side that increases with the
deployment size.
Changed in nova: | |
assignee: | nobody → Belmiro Moreira (moreira-belmiro-email-lists) |
Changed in nova: | |
status: | Triaged → In Progress |
Changed in nova: | |
assignee: | Belmiro Moreira (moreira-belmiro-email-lists) → nobody |
status: | In Progress → Confirmed |
Changed in nova: | |
assignee: | nobody → Belmiro Moreira (moreira-belmiro-email-lists) |
To post a comment you must log in.
I agree with the reporter, we should at least provide some way to differenciate why a service is disabled, especially when it's automatically disabled using the opt above