Addition of new services do not register automatically or provide an action to reconfigure nrpe checks
Bug #1926619 reported by
Steven Parker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-openstack-service-checks |
Opinion
|
Medium
|
Unassigned |
Bug Description
We installed barbican and octavia on an existing cloud.
However, the nrpe checks did not get created.
This is an easy over sight when deploying new services.
I would suggest either querying the keystone service catalog from time to time or provide an action to force nrpe check re configuration when new services are added.
It think we can work around it by removing and re-adding the keystone relation
Thanks,
Steven
summary: |
- addition of new services does not register automatically or provide an + addition of new services do not register automatically or provide an action to reconfigure nrpe checks |
summary: |
- addition of new services do not register automatically or provide an + Addition of new services do not register automatically or provide an action to reconfigure nrpe checks |
Changed in charm-openstack-service-checks: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Work around
Remove keystone relation identity- credentials openstack- service- checks: identity- credentials
juju remove-relation keystone:
Wait for relation to go away
watch 'juju status --relations | fgrep openstack | fgrep keystone'
re-add the relation and identity- credentials openstack- service- checks: identity- credentials
juju add-relation keystone:
Check /etc/nagios/nrpe.d on openstack service check node to confirm new checks are in place.
Checks will show up once nagios resyncs