Upgrade fails because product json is renamed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Ian Booth | ||
1.21 |
Fix Released
|
Critical
|
Ian Booth |
Bug Description
Upgrade ci jobs are broken on master at present:
<http://
machine-0: 2014-11-26 23:33:14 ERROR juju.worker.
This is somewhere after revsion f110dd9dc7a172f
This is caused by a change to product file names in the metadata. The old index.json is pointing to the old product file which doesn't match the information in the new product file. The shasum issue will only be seen in volatile streams like testing and weekly. The shasum issue a manifestation that another problem, that we don't have a strategy to preserve upgrade from 1.20 to 1.22. User and enterprises with private streams cannot upgrade with rewriting metadata by hand.
Changed in juju-core: | |
assignee: | nobody → Ian Booth (wallyworld) |
summary: |
- Upgrade fails with tools sha mismatch + Upgrade fails with tools sha mismatch because product json is renamed |
summary: |
- Upgrade fails with tools sha mismatch because product json is renamed + Upgrade fails because product json is renamed |
description: | updated |
description: | updated |
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 |
Caused by the changes for windows filename compatibility:
https:/ /github. com/juju/ juju/pull/ 908
// ProductMetadataPath returns the tools product metadata path for the given stream. Path(stream string) string { "streams/ v1/com. ubuntu. juju:%s: tools.json" , stream) "streams/ v1/com. ubuntu. juju-%s- tools.json" , stream)
func ProductMetadata
- return fmt.Sprintf(
+ return fmt.Sprintf(
}
In the upgrade testing, we end up with both the colon version and the dash version.