juju upgrade --upload-tools tries to upload tools agents that are not permitted by the state server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
High
|
Unassigned | ||
juju-core |
Won't Fix
|
High
|
Unassigned |
Bug Description
# Juju client is 1.24.7
$ juju version
1.24.7-wily-amd64
# Juju state server is 1.20.14
$ juju status -e peril
environment: peril
machines:
"0":
agent-state: started
agent-version: 1.20.14
dns-name: ec2-54-
instance-id: i-3ac3e285
instance-state: running
series: trusty
hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
state-
services: {}
# upgrade-juju --upload-tools fails
$ juju upgrade-juju -e peril --upload-tools --version 1.24.7
ERROR tools upload failed: 400 ({"Tools"
There is a similar bug for sync-tools, bug #1510688; ideally they would be fixed at the same time.
tags: | added: bug-squad |
Changed in juju-core: | |
milestone: | 1.25.1 → 1.26.0 |
Changed in juju-core: | |
milestone: | 1.26.0 → 2.0-beta1 |
Changed in juju-core: | |
milestone: | 2.0-beta1 → 2.0-beta2 |
Changed in juju-core: | |
milestone: | 2.0-beta2 → 2.0-beta3 |
Changed in juju-core: | |
milestone: | 2.0-beta3 → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0.1 |
tags: | added: simplestreams |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
affects: | juju → juju-core |
Changed in juju-core: | |
milestone: | 2.1.0 → none |
Both upload-tools and the logic around agent validity has been changed on master.
Please re-test as the issue may have been fixed.