Bootstrap node occasionally panicing with "not a valid unit name"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Frank Mueller | ||
1.24 |
Fix Released
|
High
|
Frank Mueller |
Bug Description
Since upgrading from 1.22.something to 1.23-beta1 on Tuesday, my vivid local provider bootstrap node's jujud is panicing several times a day. It usually happens on destroy-service, but I've seen it on a deploy as well. It is not reliably reproducible.
The tail of the log after a destroy-service panic:
2015-03-26 22:30:49 WARNING juju.lease lease.go:301 A notification timed out after 1m0s.
2015-03-27 00:25:28 ERROR juju.apiserver debuglog.go:110 debug-log handler error: write tcp 127.0.0.1:56076: broken pipe
2015-03-27 01:01:36 ERROR juju.rpc server.go:573 error writing response: write tcp 10.0.3.153:59431: broken pipe
panic: cannot retrieve unit "m#15#n#
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Critical |
importance: | Critical → Medium |
tags: | added: deploy destroy-service |
tags: | added: destroy-machine |
Changed in juju-core: | |
importance: | Medium → High |
Changed in juju-core: | |
milestone: | none → 1.24.0 |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | 1.24-beta2 → 1.24-beta3 |
Changed in juju-core: | |
milestone: | 1.24-beta3 → 1.25.0 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Can you paste some logs (preferably at TRACE level) and explain what commands you've run?