juju-core 1.20.11 crashes (SIGSEGV) if apiaddresses key is missing from agent.conf
Bug #1392814 reported by
JuanJo Ciarlante
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Ian Booth | ||
1.24 |
Fix Released
|
High
|
Ian Booth | ||
1.25 |
Fix Released
|
High
|
Ian Booth |
Bug Description
While dealing with lp#1392810 (1.18.4 -> 1.19.4), some of the units
got its machine agent.conf missing 'apiaddresses' key, making them
to SIGSEGV.
This is easy to reproduce: on a fresh 1.20.11 deployment, comment out
apiaddresses stanza at /var/lib/
and restart jujud-machine-X => crash, logtail FTR:
http://
affects: | juju-deployer → juju-core |
tags: | added: upgrade-charm |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.20.12 |
milestone: | 1.20.12 → 1.22 |
tags: | added: canonical-bootstack canonical-is |
Changed in juju-core: | |
milestone: | 1.22-alpha1 → 1.23 |
Changed in juju-core: | |
milestone: | 1.23 → none |
importance: | High → Medium |
Changed in juju-core: | |
milestone: | none → 1.26-alpha1 |
Changed in juju-core: | |
importance: | Medium → High |
Changed in juju-core: | |
assignee: | Menno Smits (menno.smits) → Ian Booth (wallyworld) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Still happens with 1.22.8