JUJU_MODEL not being respected
Bug #1693356 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Roger Peppe |
Bug Description
I'm exporting JUJU_MODEL but juju seems to be ignoring it.
http://
If I use -m to pass the model name in, everything works fine. Even juju status -m $JUJU_MODEL is working, so I know my model string is correct.
This is with 2.2-beta4-
tags: | added: cdo-qa cdo-qa-blocker |
Changed in juju: | |
assignee: | nobody → Roger Peppe (rogpeppe) |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I do see this in cmd/modelcmd/ modelcommand. go: (store jujuclient. ClientStore) (string, error) { osenv.JujuModel EnvKey) ; model != "" {
func GetCurrentModel
if model := os.Getenv(
return model, nil
}
currentCont roller, err := store.CurrentCo ntroller( )
...
but its the only place I see an actual reference to JujuModelEnvKey, so its possible some other refactoring broke this support.