[charm] nrpe relation fails when conn-check gets the relation before the primary service.
Bug #1528595 reported by
Guillermo Gonzalez
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
conn-check |
Fix Released
|
Medium
|
Wes Mason |
Bug Description
IMO, looks like a timing issue.
The error is:
2015-12-22 14:28:50 INFO nrpe-external-
2015-12-22 14:28:50 INFO nrpe-external-
and the steps to resolved this are:
juju remove-relation <service> conn-check
juju resolved conn-check
# wait for the hooks to finish
juju add-relation <service> conn-check
Related branches
lp://staging/~wesmason/charms/trusty/conn-check/fix-nrpe-race-condition
- Simon Davy (community): Approve
-
Diff: 11 lines (+1/-1)1 file modifiedplaybook.yaml (+1/-1)
Changed in conn-check: | |
importance: | Undecided → Medium |
assignee: | nobody → Wes Mason (wesmason) |
Changed in conn-check: | |
status: | New → In Progress |
Changed in conn-check: | |
status: | In Progress → Fix Committed |
Changed in conn-check: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Had this bug occur in a recent env during a separate task, so took the oppertunity to debug, finally tracked it down to the config_path env, which is evaluated lazily as part of the checks.0.command in the nrpe call, it needs to be fixed to not rely explicitly on the relation data:
config_path: "{{ relations[ 'conn-check' .0|default( {})['config_ path'] | default( '/srv/conn- check/config. yaml') }}"