inconsistent juju status from cli vs api
Bug #1467690 reported by
JuanJo Ciarlante
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Ian Booth | ||
1.24 |
Fix Released
|
Critical
|
Ian Booth |
Bug Description
juju version: 1.24.0-trusty-amd64 (agent-version: 1.24.0.1)
We have an environment showing a clean 'juju status': no
'error' string found at its output, excerpt for the failing
'landscape-
http://
but using a python script fetch status via API [0]
shows the unit erroring with:
agent-state-info: 'hook failed: "leader-elected"':
http://
Changed in juju-core: | |
importance: | Undecided → High |
status: | New → Triaged |
milestone: | none → 1.25.0 |
Changed in juju-core: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
BTW we found this issue from juju-deployer failing as per above, client/ 1" is not in an error state
note that trying to resolve it fails:
$ juju resolved -r landscape-client/1
ERROR unit "landscape-
i.e. this issue leaves the environment inoperable by juju-deployer.