juju upgrade connection shutdown unknown series
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Won't Fix
|
High
|
Unassigned | ||
juju-core |
Won't Fix
|
Critical
|
Unassigned | ||
1.25 |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
As seen in
http://
Juju 1.x fails to upgrade when it sees a series it does not know about. The client and or the state-server are checking distro-info-data. The connection is shutdown when the streams have an agent that is not listed in distro-info-data.
Reproduce:
ON a host that does not know about the current juju devel series (zesty). Attempt an upgrade of a state-server.
juju upgrade-juju --version 1.20.10
available tools:
vailable tools:
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
1.25.
ERROR connection is shut down
The log files show nothing after the sync and upload, just the shut down of the connection.
WORK AROUND:
On the client's host run
sudo apt-get install distro-info-data
Changed in juju-core: | |
milestone: | none → 1.26-alpha2 |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju-core: | |
milestone: | 1.26-alpha2 → 1.26-beta1 |
Changed in juju-core: | |
assignee: | nobody → Dave Cheney (dave-cheney) |
Changed in juju-core: | |
assignee: | Dave Cheney (dave-cheney) → nobody |
Changed in juju-core: | |
assignee: | nobody → Cheryl Jennings (cherylj) |
Changed in juju-core: | |
assignee: | Cheryl Jennings (cherylj) → Dave Cheney (dave-cheney) |
Changed in juju-core: | |
milestone: | 1.26-beta1 → 2.0-alpha2 |
tags: | added: upgrade-juju |
summary: |
- juju upgrade-juju after upload-tools fails + juju upgrade-juju can fail if host has outdated distro-info |
summary: |
- juju upgrade-juju can fail if host has outdated distro-info + juju upgrade-juju can fail if client has outdated distro-info |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
milestone: | 2.0-alpha2 → 2.0-alpha3 |
Changed in juju-core: | |
milestone: | 2.0-alpha3 → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0.1 |
Changed in juju-core: | |
assignee: | Cheryl Jennings (cherylj) → nobody |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.1 → none |
milestone: | none → 2.0.1 |
Changed in juju-core: | |
importance: | Undecided → Critical |
status: | New → Won't Fix |
Changed in juju: | |
milestone: | 2.0.1 → none |
summary: |
- juju upgrade-juju can fail if client has outdated distro-info + upgrade-juju connection shutdown unknown series |
summary: |
- upgrade-juju connection shutdown unknown series + juju upgrade connection shutdown unknown series |
description: | updated |
tags: | added: ci regression |
description: | updated |
Some experimentation has shown the following.
$ juju --version
1.25.1-wily-amd64
Start out with agent-stream=debug in environments.yaml
$ juju bootstrap --upload-tools
$ juju upgrade-juju --version 1.26-alpha1
The above works.
However, if we bootstrap without the agent-stream set to debug, and then after bootstrap:
$ juju set-env agent-version=debug
$ juju upgrade-juju --version 1.26-alpha1
ERROR cmd supercommand.go:448 no matching tools available
Looking at the server side logs, we see simplestreams data is being read from /streams. canonical. com/juju/ tools/streams/ v1/index2. sjson"
"https:/
but there's a claim that information is missing:
machine-0: 2015-11-19 05:31:16 DEBUG juju.environs. simplestreams simplestreams. go:429 read metadata index at "https:/ /streams. canonical. com/juju/ tools/streams/ v1/index2. sjson" simplestreams simplestreams. go:433 skipping index "https:/ /streams. canonical. com/juju/ tools/streams/ v1/index2. sjson" because of missing information: "content-download" data not found
machine-0: 2015-11-19 05:31:16 DEBUG juju.environs.
Examining the json data received by Juju shows that the content-download field is not missing and the data is as expected.
Further investigation required.