"juju model-defaults juju-no-proxy=..." fails with network blocks
Bug #1876734 reported by
Alvaro Uria
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
- Steps to reproduce:
1) Bootstrap a lxd controller
2) Run:
$ juju model-defaults juju-no-
ERROR invalid cloud "juju-no-
2.a) If a network block is _not_ provided, command succeeds:
$ juju model-defaults juju-no-
3) Run the same against a model (this succeeds)
juju model-config -m default juju-no-
I was expecting the command on #2 to succeed.
Changed in juju: | |
milestone: | none → 2.8-rc1 |
assignee: | nobody → Ian Booth (wallyworld) |
importance: | Undecided → High |
status: | New → 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.
You do need to specify a cloud name with model-defaults, but only if the controller host more than one cloud. It seems the CLI is confused and is always expecting a cloud name.
For now you can just do
$ juju model-defaults <mycloud> juju-no- proxy=" localhost, 127.0.0. 1,127.0. 0.53,10. 0.8.1"
where <mycloud> is the cloud used to bootstrap the controller, eg "localhost"