nagios-charmers team mailing list archive
-
nagios-charmers team
-
Mailing list archive
-
Message #00803
[Bug 1860584] Re: nagios-relation-change hook failed
Thanks a lot for the bug report! I couldn't reproduce it with Juju 2.7.1
unfortunately. Steps:
0. I have an LXD undercloud on top of which I deployed an OpenStack overcloud with juju.
1. Create an OpenStack instance manually ('openstack server create ...')
2. Add that machine manually to juju ('juju add-machine ssh:ubuntu@<ip>')
3. Deploy nagios (Rev. 35) to that machine.
4. Deploy nrpe (Rev. 61) to the undercloud and relate it to ceph-mon.
5. In the model where nagios is running do 'juju offer nagios:monitors' (Note: the 'nagios' and 'monitors' interfaces are doing the exact same under the hood, so it doesn't matter here if we try to reproduce the bug with nagios-relation-changed or monitors-relation-changed)
6. In the undercloud model do 'juju relate nrpe admin/default.nagios'
Everything went well, i.e. monitors-relation-changed ran successfully.
Also I can see that private-address is set:
```
$ juju run -a nagios-on-manual -- relation-get -r0 - remote-31d07078810849ae8856fdb203fc9c9d/3
egress-subnets: 10.0.8.114/32
ingress-address: 10.0.8.114
machine_id: "3"
monitors: '{''monitors'': {''remote'': {''nrpe'': {''ceph'': {''command'': ''check_ceph''},
''check_disk_root'': ''check_disk_root'', ''check_load'': ''check_load'', ''check_swap'':
''check_swap'', ''check_swap_activity'': ''check_swap_activity'', ''check_mem'':
''check_mem'', ''check_conntrack'': ''check_conntrack''}}}, ''version'': ''0.3''}'
private-address: 10.0.8.114
target-id: juju-ceph-mon-2
```
I'm also in favor of closing this issue for now and re-opening in case
this reoccurs. Thanks!
** Changed in: nagios-charm
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Nagios
Charm developers, which is subscribed to Nagios Charm.
https://bugs.launchpad.net/bugs/1860584
Title:
nagios-relation-change hook failed
Status in Nagios Charm:
Won't Fix
Bug description:
we are using a manual provider for OpenStack instances. All hostname
points to floating ip address and dure to security reasons we can not
use OpenStack provider here.
Once we add machines manually using floating and run lma stack gets the error
Nagios-relation-changed key error: 'private-address'
As can not send log files due to a restricted environment so attaching
a screenshot of the error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nagios-charm/+bug/1860584/+subscriptions
References