bootstrap --config agent-version is ignored
Bug #1674764 reported by
Nicholas Skaggs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Anastasia |
Bug Description
Bootstrapping with --agent-version set results in the controller bootstrapping to the specified agent.
Passing --config agent-version= however will accomplish nothing. It doesn't affect later deployed models, nor is it's valued saved in the defaults or the model-config anywhere. The bootstrap help text intermingles the terms and causes confusion.
description: | updated |
description: | updated |
Changed in juju: | |
status: | New → Incomplete |
Changed in juju: | |
status: | In Progress → Fix Committed |
milestone: | none → 2.3-beta1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Ci tests agent-version all the time. CI and Juju help use
juju bootstrap aws aws-8 --agent-version 2.1.2
It is a bootstrap option, not a config. I see you used --config agent-version= 2.1.2. Does this work when you follow pass the arg directly. model-config will show the agent-version, but I don't believe it can be changed to affect deployments. For example, anging the mode-config does not trigger an upgrade.