Status panicks during juju-upgrade

Bug #1339931 reported by Curtis Hovey
6
This bug affects 1 person
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-precise-amd64 gc]
2014-07-09 23:11:43 INFO juju.conn api.go:270 connecting to API addresses: [ec2-54-209-79-1.compute-1.amazonaws.com:17070 ip-172-31-8-248.ec2.internal:17070 54.209.79.1:17070 172.31.8.248:17070]
2014-07-09 23:11:43 INFO juju.state.api apiclient.go:242 dialing "wss://ec2-54-209-79-1.compute-1.amazonaws.com:17070/environment/47853f21-6d0e-4da7-8b4b-5b3827b1a2ce/api"
2014-07-09 23:11:43 INFO juju.state.api apiclient.go:176 connection established to "wss://ec2-54-209-79-1.compute-1.amazonaws.com:17070/environment/47853f21-6d0e-4da7-8b4b-5b3827b1a2ce/api"
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.panic(0xcc1300, 0x19ed7c8)
 /usr/lib/go/src/pkg/runtime/panic.c:266 +0xb6
main.newStatusFormatter(0x0, 0xc210000010)
 /home/ubuntu/juju-build/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/status.go:245 +0x92
main.(*StatusCommand).Run(0xc2101ca640, 0xc2100dd0a0, 0x0, 0x0)
 /home/ubuntu/juju-build/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/status.go:97 +0x395
github.com/juju/juju/cmd/envcmd.(*environCommandWrapper).Run(0xc2101cb940, 0xc2100dd0a0, 0xb27740, 0xc2101dc460)
 /home/ubuntu/juju-build/juju-core-1.20.1/src/github.com/juju/juju/cmd/envcmd/environmentcommand.go:1 +0x3d
main.(*envCmdWrapper).Run(0xc2101cb960, 0xc2100dd0a0, 0x0, 0x0)
 /home/ubuntu/juju-build/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/addmachine.go:1 +0x3d
github.com/juju/cmd.(*SuperCommand).Run(0xc2101ac0b0, 0xc2100dd0a0, 0xc2100dd0a0, 0x0)
 /home/ubuntu/juju-build/juju-core-1.20.1/src/github.com/juju/cmd/supercommand.go:321 +0x3ca
github.com/juju/cmd.Main(0x7f492ebc43d0, 0xc2101ac0b0, 0xc2100dd0a0, 0xc21000a010, 0x4, ...)
 /home/ubuntu/juju-build/juju-core-1.20.1/src/github.com/juju/cmd/cmd.go:247 +0x283
main.Main(0xc21000a000, 0x5, 0x5)
 /home/ubuntu/juju-build/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/main.go:77 +0xada
main.main()
 /home/ubuntu/juju-build/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/main.go:174 +0x44

goroutine 3 [syscall]:
os/signal.loop()
 /usr/lib/go/src/pkg/os/signal/signal_unix.go:21 +0x1e
created by os/signal.init��1
 /usr/lib/go/src/pkg/os/signal/signal_unix.go:27 +0x31

goroutine 12 [syscall]:
runtime.goexit()
 /usr/lib/go/src/pkg/runtime/proc.c:1394

Curtis Hovey (sinzui)
tags: added: panic
Curtis Hovey (sinzui)
Changed in juju-core:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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