juju-core

panic in cmd/jujud on power

Bug #1496217 reported by Tim Penhey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Critical
Casey Marshall
juju-core 1.25-beta1
Tim Penhey (thumper)
Changed in juju-core:
milestone: none → 1.25-beta1
Revision history for this message
Casey Marshall (cmars) wrote :

@les saw the same panic on amd64 this morning, https://pastebin.canonical.com/139944/. I think we've found a repeatability issue.

Changed in juju-core:
assignee: Tim Penhey (thumper) → Casey Marshall (cmars)
Revision history for this message
Casey Marshall (cmars) wrote :

http://reviews.vapour.ws/r/2677/

I suspect a race condition due to the nature of the panic in the CI log above -- a nil receiver seems to have been dereferenced after a conditional nil check should have executed -- this seems to indicate that it was concurrently modified (if gccgo stack traces can be trusted).

Uniter cleanups are called from a separate goroutine, so this does seem possible. Unfortunately, I cannot personally reproduce the panic on my machine.

Casey Marshall (cmars)
Changed in juju-core:
status: In Progress → Fix Committed
Tim Penhey (thumper)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.