state/watcher: panic: runtime error: invalid memory address or nil pointer dereference

[Dave Cheney]

Reported by a customer, ppc64, juju 1.17.7

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x48]

goroutine 17 [running]:
state.$nested17
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/state/watcher.go:213
launchpad.net_juju_core_state_watcher.sync.pN45_launchpad.net_juju_core_state_watcher.Watcher
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/state/watcher/watcher.go:407
launchpad.net_juju_core_state_watcher.loop.pN45_launchpad.net_juju_core_state_watcher.Watcher
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/state/watcher/watcher.go:220
watcher.$nested0
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/state/watcher/watcher.go:118
created by launchpad.net_juju_core_state_watcher.New
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/state/watcher/watcher.go:117

goroutine 1 [chan receive]:
launchpad.net_tomb.Wait.pN23_launchpad.net_tomb.Tomb
 /build/buildd/juju-core-1.17.7/src/launchpad.net/tomb/tomb.go:110
launchpad.net_juju_core_worker.Wait.pN37_launchpad.net_juju_core_worker.runner
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/worker/runner.go:124
main.Run.pN17_main.MachineAgent
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/jujud/machine.go:166
launchpad.net_juju_core_cmd.Run.pN40_launchpad.net_juju_core_cmd.SuperCommand
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/supercommand.go:298
launchpad.net_juju_core_cmd.Main
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/cmd.go:244
main.jujuDMain
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/jujud/main.go:107
main.Main
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/jujud/main.go:122
main.main
 /build/buildd/juju-core-1.17.7/src/launchpad.net/juju-core/cmd/jujud/main.go:139

[John A Meinel (jameinel)]

I know the review for the previous was bumped, do we have an ETA on when an alternative fix will be available?