| 2015-10-28 13:47:12 |
Aaron Bentley |
bug |
|
|
added bug |
| 2015-10-28 13:47:42 |
Aaron Bentley |
summary |
Only state-server upgrades 1.20 to master |
Only state-server upgrades from 1.20 |
|
| 2015-10-28 13:48:11 |
Aaron Bentley |
nominated for series |
|
juju-core/1.25 |
|
| 2015-10-28 13:48:11 |
Aaron Bentley |
bug task added |
|
juju-core/1.25 |
|
| 2015-10-28 13:48:18 |
Aaron Bentley |
juju-core/1.25: status |
New |
Triaged |
|
| 2015-10-28 13:48:21 |
Aaron Bentley |
juju-core/1.25: importance |
Undecided |
High |
|
| 2015-10-28 13:48:25 |
Aaron Bentley |
juju-core/1.25: milestone |
|
1.25.1 |
|
| 2015-11-11 01:34:15 |
Cheryl Jennings |
juju-core/1.25: milestone |
1.25.1 |
1.25.2 |
|
| 2015-11-11 14:25:28 |
Aaron Bentley |
summary |
Only state-server upgrades from 1.20 |
Devel state server switches to devel streams even when they are not useful |
|
| 2015-11-11 14:36:23 |
Aaron Bentley |
description |
As seen here:
http://reports.vapour.ws/releases/3230/job/xx-aws-upgrade-20-trusty-amd64/attempt/19
This test was performed with very small streams, containing just the source and target agents, but since the state-server was able to upgrade, it seems unlikely that the streams were at fault. Perhaps the small size revealed a timing issue.
ure
The stream releases file is here:
https://s3.amazonaws.com/temp-streams/xx-aws-upgrade-20-trusty-amd64/19/streams/v1/com.ubuntu.juju-released-tools.json
The machine log shows that the uniter contains "upgrade requested from 1.20.11-trusty-amd64 to 1.26-alpha1
... ERROR ... "upgrader": no matching tools available"
http://data.vapour.ws/juju-ci/products/version-3230/xx-aws-upgrade-20-trusty-amd64/build-19/machine-1.log.gz
This does not always happen; an earlier run with the 1.25 branch showed success:
http://juju-ci.vapour.ws/job/xx-aws-upgrade-20-trusty-amd64/15/ |
The true cause is that juju automatically uses devel streams for devel jujus.
When you upgrade a state server from release to devel, and it was previously using released streams, it switches to devel streams. Those devel streams may not contain the agent for that release. If they do not, the remaining juju agents will be unable to upgrade.
Note that it is legitimate for released streams to contain devel agents. Our "devel" URL works that way:
http://streams.canonical.com/juju/devel/tools/streams/v1/com.ubuntu.juju:released:tools.json
http://streams.canonical.com/juju/devel/tools provides only released streams, not devel, so it is potentially subject to this issue.
One way to avoid this issue would be a "fall back" approach. Instead of using devel streams only, devel jujus could fall back to devel streams if the released streams did not contain the desired agent.
ORIGINAL DESCRIPTION
As seen here:
http://reports.vapour.ws/releases/3230/job/xx-aws-upgrade-20-trusty-amd64/attempt/19
This test was performed with very small streams, containing just the source and target agents, but since the state-server was able to upgrade, it seems unlikely that the streams were at fault. Perhaps the small size revealed a timing issue.
ure
The stream releases file is here:
https://s3.amazonaws.com/temp-streams/xx-aws-upgrade-20-trusty-amd64/19/streams/v1/com.ubuntu.juju-released-tools.json
The machine log shows that the uniter contains "upgrade requested from 1.20.11-trusty-amd64 to 1.26-alpha1
... ERROR ... "upgrader": no matching tools available"
http://data.vapour.ws/juju-ci/products/version-3230/xx-aws-upgrade-20-trusty-amd64/build-19/machine-1.log.gz
This does not always happen; an earlier run with the 1.25 branch showed success:
http://juju-ci.vapour.ws/job/xx-aws-upgrade-20-trusty-amd64/15/ |
|
| 2015-11-11 14:36:30 |
Aaron Bentley |
juju-core: importance |
High |
Medium |
|
| 2015-11-11 14:36:33 |
Aaron Bentley |
juju-core/1.25: importance |
High |
Medium |
|
| 2015-11-11 14:36:36 |
Aaron Bentley |
juju-core: milestone |
1.26.0 |
|
|
| 2015-11-11 14:36:39 |
Aaron Bentley |
juju-core/1.25: milestone |
1.25.2 |
|
|
| 2016-04-24 14:54:33 |
Curtis Hovey |
tags |
intermittent-failure upgrade-juju |
intermittent-failure streams upgrade-juju |
|
| 2016-05-09 22:29:58 |
Anastasia |
tags |
intermittent-failure streams upgrade-juju |
intermittent-failure simplestreams streams upgrade-juju |
|
| 2016-08-08 06:16:32 |
Anastasia |
juju-core/1.25: status |
Triaged |
Won't Fix |
|
| 2016-08-23 03:49:36 |
Canonical Juju QA Bot |
affects |
juju-core |
juju |
|
| 2016-08-23 13:31:01 |
Canonical Juju QA Bot |
juju-core: importance |
Undecided |
Medium |
|
| 2016-08-23 13:31:01 |
Canonical Juju QA Bot |
juju-core: status |
New |
Won't Fix |
|
| 2017-10-17 22:47:12 |
Christian Muirhead |
juju: assignee |
|
Christian Muirhead (2-xtian) |
|
| 2017-10-17 22:47:14 |
Christian Muirhead |
juju: status |
Triaged |
In Progress |
|
| 2017-10-17 22:47:23 |
Christian Muirhead |
juju: milestone |
|
2.3-beta2 |
|
| 2017-11-01 22:30:15 |
Canonical Juju QA Bot |
juju: milestone |
2.3-beta2 |
|
|
| 2017-11-21 04:38:20 |
Christian Muirhead |
juju: status |
In Progress |
Fix Committed |
|
| 2017-11-21 04:38:28 |
Christian Muirhead |
juju: status |
Fix Committed |
Fix Released |
|
