juju-core client panics with juju set empty string

Bug #1348829 reported by Simon Davy
40
This bug affects 5 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Jorge Niedbalski
1.20
Fix Released
High
Jorge Niedbalski

Bug Description

Juju 1.20.1.1 from stable ppa, trusty amd64

$ juju deploy postgresql
$ juju set postgresql fsync=
panic: runtime error: index out of range

goroutine 1 [running]:
runtime.panic(0xcc1300, 0x19ec9b7)
        /usr/lib/go/src/pkg/runtime/panic.c:266 +0xb6
main.(*SetCommand).Run(0xc21011ad00, 0xc2100dd0f0, 0x0, 0x0)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/set.go:92 +0x62d
github.com/juju/juju/cmd/envcmd.(*environCommandWrapper).Run(0xc21011bee0, 0xc2100dd0f0, 0xb27740, 0xc21012d430)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/juju/cmd/envcmd/environmentcommand.go:1 +0x3d
main.(*envCmdWrapper).Run(0xc21011bf00, 0xc2100dd0f0, 0x0, 0x0)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/addmachine.go:1 +0x3d
github.com/juju/cmd.(*SuperCommand).Run(0xc2100fc2c0, 0xc2100dd0f0, 0xc2100dd0f0, 0x0)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/cmd/supercommand.go:321 +0x3ca
github.com/juju/cmd.Main(0x7f975c2863c0, 0xc2100fc2c0, 0xc2100dd0f0, 0xc21000a010, 0x3, ...)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/cmd/cmd.go:247 +0x283
main.Main(0xc21000a000, 0x4, 0x4)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/main.go:77 +0xada
main.main()
        /build/buildd/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
$ juju set postgresql fsync
error: invalid option: "fsync"

This was fixed in 1.15 I think (https://bugs.launchpad.net/juju-core/+bug/1194945), so looks like a regression.

Revision history for this message
Matt Bruzek (mbruzek) wrote :

I am also seeing this problem with Juju 1.20.1-trusty-amd64 on local provider.

mbruzek@workhorse:~/workspace/charms/precise/nfs$ juju set nfs storage_root=
panic: runtime error: index out of range

goroutine 1 [running]:
runtime.panic(0xcc1300, 0x19ec9b7)
        /usr/lib/go/src/pkg/runtime/panic.c:266 +0xb6
main.(*SetCommand).Run(0xc210142180, 0xc2100e0000, 0x0, 0x0)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/set.go:92 +0x62d
github.com/juju/juju/cmd/envcmd.(*environCommandWrapper).Run(0xc210141c80, 0xc2100e0000, 0xb27740, 0xc210151410)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/juju/cmd/envcmd/environmentcommand.go:1 +0x3d
main.(*envCmdWrapper).Run(0xc210141ca0, 0xc2100e0000, 0x0, 0x0)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/addmachine.go:1 +0x3d
github.com/juju/cmd.(*SuperCommand).Run(0xc210121580, 0xc2100e0000, 0xc2100e0000, 0x0)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/cmd/supercommand.go:321 +0x3ca
github.com/juju/cmd.Main(0x7f84c73a11f0, 0xc210121580, 0xc2100e0000, 0xc21000a010, 0x3, ...)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/cmd/cmd.go:247 +0x283
main.Main(0xc21000a000, 0x4, 0x4)
        /build/buildd/juju-core-1.20.1/src/github.com/juju/juju/cmd/juju/main.go:77 +0xada
main.main()
        /build/buildd/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)
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → next-stable
tags: added: config
Curtis Hovey (sinzui)
tags: added: charmers ci
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Still happens with 1.20.5

juju set someservicedoesntmatter somevalue=
panic: runtime error: index out of range
(...)

Curtis Hovey (sinzui)
tags: added: set
Revision history for this message
Jorge Niedbalski (niedbalski) wrote :
Changed in juju-core:
status: Triaged → Fix Committed
Revision history for this message
Ian Booth (wallyworld) wrote :

Setting back to In progress because PR hasn't merged yet

Changed in juju-core:
status: Fix Committed → In Progress
assignee: nobody → Jorge Niedbalski (niedbalski)
Ian Booth (wallyworld)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: next-stable → 1.21-alpha1
Curtis Hovey (sinzui)
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.

Other bug subscribers

Remote bug watches

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