null provider panics if storage-key-auth is missing
Bug #1235084 reported by
Andrew Wilkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
I went to test a change in the null provider today, and found that it is panicking in a clean environment. Something must have changed recently.
2013-10-04 06:28:30 INFO juju.environs.
panic: interface conversion: interface is nil, not string
goroutine 1 [syscall]:
syscall.Syscall()
/home/
syscall.
/home/
goroutine 2 [syscall]:
Related branches
lp:~axwalk/juju-core/lp1235100-null-provider-storage
- Juju Engineering: Pending requested
-
Diff: 52 lines (+8/-5)3 files modifiedprovider/null/config.go (+0/-1)
provider/null/config_test.go (+5/-0)
provider/null/environ.go (+3/-4)
description: | updated |
Changed in juju-core: | |
status: | New → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | none → 1.15.1 |
Changed in juju-core: | |
importance: | Undecided → High |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Turns out it was because I had storage-auth-key commented out in my environments.yaml. Clearly this isn't an ideal way to report that, but it's not as dire as I thought.