private address supplied to Nagios, but Nagios public addr set in nrpe.cfg
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NRPE Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
I have two models, both using Openstack instances. Both are in the same Openstack network.
The model with Nagios is connected to nrpe via cross model relation.
When I look at nrpe.cfg, the public (i.e. floating) IP address of the Nagios host is specified as allowed. When I check the host definitions in Nagios, the private (non-floating) address is used. This means that Nagios doesn't have permission to connect to NRPE because it uses it's private address.
This is intermittent - somehow one iteration of config-changed supplied private, and then after reboots etc the other address was used and we were unable to reach nrpe.
This has also been observed with manual machines outside Openstack instances, where the nagios host has multiple addresses and is attempting to use one not listed to connect to the manually added machine.
Related branches
- Xav Paice (community): Disapprove
- Chris Sanders (community): Needs Information
- Wouter van Bommel (community): Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 27 lines (+8/-0)2 files modifiedconfig.yaml (+6/-0)
hooks/nrpe_helpers.py (+2/-0)
| summary: |
- private addresse supplied to Nagios, but Nagios public addr set in + private address supplied to Nagios, but Nagios public addr set in nrpe.cfg |
| Aurelien Lourot (aurelien-lourot) wrote | #1 |
This is a symptom of these two bugs:
1. https:/
2. https:/
Closing as duplicate.