juju upgrade --upload-tools tries to upload tools agents that are not permitted by the state server

Bug #1510689 reported by Aaron Bentley
10
This bug affects 2 people
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-173-237-220.compute-1.amazonaws.com
    instance-id: i-3ac3e285
    instance-state: running
    series: trusty
    hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
    state-server-member-status: has-vote
services: {}

# upgrade-juju --upload-tools fails
$ juju upgrade-juju -e peril --upload-tools --version 1.24.7
ERROR tools upload failed: 400 ({"Tools":null,"DisableSSLHostnameVerification":false,"Error":{"Message":"cannot get environment config: invalid series \"wily\"","Code":""}})

There is a similar bug for sync-tools, bug #1510688; ideally they would be fixed at the same time.

Revision history for this message
Aaron Bentley (abentley) wrote :
Aaron Bentley (abentley)
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
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta1 → 2.0-beta2
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta2 → 2.0-beta3
Curtis Hovey (sinzui)
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
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Both upload-tools and the logic around agent validity has been changed on master.

Please re-test as the issue may have been fixed.

Changed in juju-core:
status: Triaged → Incomplete
milestone: 2.0.1 → none
Revision history for this message
Aaron Bentley (abentley) wrote :

AIUI, upgrade-juju is not yet supported in 2.x. Is it even possible to test?

Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Aaron

Good point, I'll add it to 2.1.0 backlog as we are more likely to have some form of upgrade there.

Changed in juju-core:
status: Incomplete → Triaged
milestone: none → 2.1.0
affects: juju-core → juju
Changed in juju:
milestone: 2.1.0 → none
milestone: none → 2.1.0
Curtis Hovey (sinzui)
affects: juju → juju-core
Changed in juju-core:
milestone: 2.1.0 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Marking as "Won't Fix" for Juju 1.x as not a critical bug.
Re-targeting for Juju 2.x.

@Aaron,
Please re-word using Juju 2.x terminology.

Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.2.0
Changed in juju-core:
status: Triaged → Won't Fix
Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Aaron,

Could you please re-test? functional test may be of great benefit here, especially now that we are several Juju 2.x...

Changed in juju:
status: Triaged → Incomplete
milestone: 2.2.0 → none
Revision history for this message
Aaron Bentley (abentley) wrote :

The specific case I've observed was with juju 1.20 as the server. Since Juju can't upgrade from 1.x at the moment, I can't test that. I understand there are plans to support upgrading juju from 1.x, but I don't think upgrading from 1.20 is an important case.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Aaron,

Since this is only applicable to upgrades from Juju 1.x to Juju 2.x, I am putting it against 2.2 in order to keep track of it when we get to this upgrade story.

Thank you for clarification!

Changed in juju:
status: Incomplete → Triaged
milestone: none → 2.2.0
Revision history for this message
Anastasia (anastasia-macmood) wrote :

As upgrade from Juju 1.x to 2.x will be done by external tool, this specific case will no longer be applicable.
Marking as Invalid.

Changed in juju:
status: Triaged → Invalid
milestone: 2.2.0 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.