tools migration fails when upgrading 1.20.14 to 1.24.1 on ec2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Unassigned | ||
1.24 |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
When upgrading from 1.20.14 to 1.24.1 on AWS, I found that only machine 0 was upgrading and none of the others. After looking through the logs, I found the following:
2015-06-26 06:56:19 ERROR juju.cmd.jujud upgrade.go:359 upgrade from 1.20.14 to 1.24.1.1 for "machine-0" failed (will retry): migrate tools into environment storage: cannot find tools in provider storage: cannot read product data, invalid URL "https:/
Turning up logging revealed the reason: "The request signature we calculated does not match the signature you provided. Check your key and signing method."
We made some changes to move everything over to AWS' V4 signing method recently, which may be the cause here.
This can be worked around by upgrading twice. The first upgrade will upgrade machine 0; the second upgrade will upload tools into state/gridfs, so the upgrade step won't get in the way.
Changed in juju-core: | |
milestone: | 1.24.2 → 1.25.0 |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
See lp:1466969 for some additional context.