Setting localhost region for model-defaults does nothing.
Bug #1888368 reported by
Simon Richardson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
It's possible to set a value in model-defaults for a region. Unbeknown to most the localhost has a region; "localhost". So you can add model-config to a region that does nothing.
juju model-defaults localhost/localhost test-mode=true
This doesn't do anything, but should probably report back to the user that this isn't a valid region for setting config on to.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
Revision history for this message
| Simon Richardson (simonrichardson) wrote | #2 |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| importance: | Undecided → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
You can see what it does like so:
$ juju model-defaults localhost
Attribute Default Controller
test-mode false -
localhost true -
[azure-
Attribute Default Controller
agent-metadata-url "" -
agent-stream released -
apt-ftp-proxy "" -
apt-http-proxy "" -
apt-https-proxy "" -
<snip>
snap-store-
ssl-hostname-
test-mode false -
localhost true -
transmit-
update-
Next time you add a model to that region, its config will include test-mode=true.
You can test by adding a dummy region to a lxd cloud in clouds.yaml and add a model to a region which doesn't have test-mode=true and see that it gets false, whereas a model added to localhost region gets true.