Required model config options not propagated from controller to new models by default
Bug #1648426 reported by
Michael Foord
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
See bug #1642609 for back story.
By default, when adding a new model, config options are not propagated from the controller model. Some config options may be *required* in order for a new model to provision machines. Those options, at least, should propagate by default. These include "agent-stream", "agent-
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| status: | New → Invalid |
| Changed in juju: | |
| status: | Invalid → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.2.0 |
| tags: | added: oil oil-2.0 |
| Changed in juju: | |
| milestone: | 2.2-beta1 → 2.2-beta2 |
| Changed in juju: | |
| milestone: | 2.2-beta2 → 2.2-beta3 |
| Changed in juju: | |
| milestone: | 2.2-beta3 → 2.2-beta4 |
| Changed in juju: | |
| milestone: | 2.2-beta4 → 2.2-rc1 |
| tags: | added: config model-config |
| Changed in juju: | |
| importance: | High → Medium |
| milestone: | 2.2-rc1 → none |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
We have a notion of model-default config options. These are inherited by any model within the controller and can be specified at bootstrap time or set on a running controller by running similarly named command.
I would be reluctant to recommend that the config options you've listed are *always* inherited by default.