no nagios check for octavia/loadbalancer
Bug #1867722 reported by
Joe Guo
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-openstack-service-checks |
Fix Released
|
High
|
Joe Guo | ||
Bug Description
Currently there is no check for octavia/
We need to add one or a few checks to check lb/amphorae/
Related branches
~canonical-bootstack/charm-openstack-service-checks:check-loadbalancers
Merged
into
~llama-charmers/charm-openstack-service-checks:master
at
revision a3bc3c9b2a2072a63a7f7a5d7e9829144f742560
- Jeremy Lounder (community): Approve
- Alvaro Uria (community): Needs Fixing
- James Hebden (community): Approve
- Jose Guedez (community): Approve
- Celia Wang: Approve
- Joe Guo: Pending requested
-
Diff: 329 lines (+283/-0)4 files modifiedconfig.yaml (+18/-0)
files/plugins/check_octavia.py (+227/-0)
layer.yaml (+2/-0)
lib/lib_openstack_service_checks.py (+36/-0)
~canonical-bootstack/charm-openstack-service-checks:check-loadbalancers
- Jose Guedez (community): Approve
- Jeremy Lounder: Pending requested
- James Hebden: Pending requested
- Joe Guo: Pending requested
-
Diff: 515 lines (+386/-9)9 files modifiedactions.yaml (+3/-0)
actions/actions.py (+75/-0)
actions/refresh-endpoint-checks (+1/-0)
config.yaml (+18/-0)
files/plugins/check_octavia.py (+227/-0)
layer.yaml (+2/-0)
lib/lib_openstack_service_checks.py (+55/-8)
metadata.yaml (+1/-1)
tests/functional/test_deploy.py (+4/-0)
| Changed in charm-openstack-service-checks: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Joe Guo (guoqiao) |
| Changed in charm-openstack-service-checks: | |
| milestone: | none → 20.05 |
| Changed in charm-openstack-service-checks: | |
| status: | In Progress → Fix Committed |
| Changed in charm-openstack-service-checks: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Adam Dyess (addyess) wrote | #1 |
To post a comment you must log in.
new checks should include
* load balancers currently in ERROR
( any of the load balancers marked with ERROR )
* load balancers with amphora in ERROR
( any of the amphora within a load balancer are marked with ERROR )
* amphora that are not backed by a running VM instance
( the amphora has a compute-id which is either in ERROR state or doesn't exist)