Tools are automatically upgraded during deploy
Bug #1399504 reported by
Jill Rouleau
This bug report is a duplicate of:
Bug #1455260: Deployments fail when juju implicitly upgrade after bootstrap.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
When deploying via juju-deployer on MaaS, tools are automatically upgraded without warning. Client on MaaS is juju 1.20.11, machine 0 upgrades to 1.20.13 during deploy, subsequent machines get 1.20.13. This caused unexpected introduction of lp:1395908 to the environment.
2014-12-04 21:56:05 ERROR juju.worker runner.go:207 fatal "upgrader": must restart: an agent upgrade is available
2014-12-04 21:56:05 ERROR juju.cmd supercommand.go:323 must restart: an agent upgrade is available
2014-12-04 21:56:05 INFO juju.cmd supercommand.go:37 running jujud [1.20.13-
Deployed tools should match client version unless otherwise specified.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: bootstrap upgrade-juju |
To post a comment you must log in.
By design, the current implementation does look for tools to use based on a major.minor version match. So bootstrapping with a 1.20.11 client will select 1.20.X tools. But I'm confused about the log messages above - I would not expect an upgrade to occur as the 1.20.13 tools would have been selected from the start. Can you provide more information about your set up? What commands are being invoked etc?