Status panicks during juju-upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Status panicked during a test. The test passed though since status is called often to poll the state server. This is upgrade of local lxc precise amd64. Status shouldn't go to pieces while juju is upgrading:
!!! 2014-07-09 23:11:42 INFO juju.cmd supercommand.go:37 running juju [1.20.1-
2014-07-09 23:11:43 INFO juju.conn api.go:270 connecting to API addresses: [ec2-54-
2014-07-09 23:11:43 INFO juju.state.api apiclient.go:242 dialing "wss://
2014-07-09 23:11:43 INFO juju.state.api apiclient.go:176 connection established to "wss://
connection is shut down
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x28 pc=0x41cfe2]
goroutine 1 [running]:
runtime.
/usr/lib/
main.newStatusF
/home/
main.(*
/home/
github.
/home/
main.(*
/home/
github.
/home/
github.
/home/
main.Main(
/home/
main.main()
/home/
goroutine 3 [syscall]:
os/signal.loop()
/usr/lib/
created by os/signal.init��1
/usr/lib/
goroutine 12 [syscall]:
runtime.goexit()
/usr/lib/
tags: | added: panic |
Changed in juju-core: | |
status: | Triaged → Fix Released |