can't read environment file no hint of actual yaml error
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
Medium
|
Unassigned | ||
Bug Description
i made a trivial edit to my environments.yaml file, and then discovered that juju could no longer read the file.
all juju commands now fail with an inscrutable error message
$ juju env --debug
2014-05-16 12:49:01 INFO juju.cmd supercommand.go:301 running juju-1.
2014-05-16 12:49:01 ERROR juju.cmd supercommand.go:304 couldn't read the environment
i've verified that the file is valid yaml with the expected structure.
after some debugging the underlying cause was 'default' environment no longer pointed to a valid environment name ( i had renamed it, it was not active) and this inspite of current-environment pointing to a different environment.
at min a nicer error message would be nice, at most ignoring resolution of default unless it was actually needed.
| Curtis Hovey (sinzui) wrote : | #1 |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: config ui |
| summary: |
- can't read environment file no hint of actual error + can't read environment file no hint of actual yaml error |
| tags: | added: bitesized |
| tags: |
added: bitesize removed: bitesized |
| Sidharth Nandury (nsidharth1991) wrote : | #2 |
the same error affected me today. Any solutions?
| Anastasia (anastasia-macmood) wrote : | #3 |
We no longer have environments.yaml on Juju 2.
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
As an aside, This happened to me 2 days ago.