status gets stuck on maintenance: NRPE configured after relating to nrpe subordinate
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Jenkins CI Agent Charm |
Fix Released
|
High
|
Haw Loeung | ||
Bug Description
When deployed jenkins-slave is as expected in active state and shows useful info on the master_url being used:
jenkins-slave/0* active idle 1 10.42.84.154 ready - using jenkins http://
When you relate to nrpe subordinate for nagios checks, the unit seemingly get's stuck in maintenance state forever:
jenkins-slave/0* maintenance idle 1 10.42.84.154 NRPE configured
nrpe/0* active idle 10.42.84.154 icmp,5666/tcp Ready (source version/commit cs-nrpe-...)
Expected state, jenkins should return to active state, as being stuck in maintenance can cause timeouts from various deploy tooling such as mojo that checks for a healthy stable juju status before continuing with a deployment.
Related branches
- Gareth Woolridge: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 33 lines (+3/-2)2 files modifiedreactive/jenkins_slave.py (+2/-1)
tox.ini (+1/-1)
| Changed in jenkins-slave-charm: | |
| status: | New → In Progress |
| assignee: | nobody → Haw Loeung (hloeung) |
| importance: | Undecided → High |
| Haw Loeung (hloeung) wrote | #1 |
| Changed in jenkins-slave-charm: | |
| status: | In Progress → Fix Released |
https:/