Upgrades broken in 1.22 tip

Bug #1510952 reported by Curtis Hovey on 2015-10-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
High
Unassigned
1.22
Critical
Unassigned

Bug Description

As seen at
    http://reports.vapour.ws/releases/3232

2015-10-28 07:14:56 ERROR juju.cmd supercommand.go:430 no matching tools available

Juju cannot upgrade after the commit of
    https://github.com/juju/juju/commit/a02fbc8812e40f5754a36bd2252747a98a74d3e2

The commit can be backed put or fixed.

Curtis Hovey (sinzui) on 2015-10-28
Changed in juju-core:
status: Triaged → Incomplete
Curtis Hovey (sinzui) wrote :

This bug might be related to bug1507867. This bug is not limited to canonistack and keystone, but since that bug has mutated, we might find a common reason for no matching agents.

Curtis Hovey (sinzui) wrote :

This bug might be in other branches or a variation of it has merged into master which feature branches merge often.

<stokaboo> reported that --upload-tools didn't work with the lxd-provider branch because "no matching tools available"
machine-0: 2015-10-29 12:22:24 ERROR juju.worker runner.go:223 exited "toolsversionchecker": cannot update tools information: cannot get latest version: canot find available tools: no matching tools available

description: updated
Cheryl Jennings (cherylj) wrote :

That error from toolsversionchecker is spurious and was fixed in bug 1502202 (should be in 1.25.1).

The other reports of "no matching tools" from the various commands is definitely valid and needs investigating.

Tim Penhey (thumper) on 2015-11-23
Changed in juju-core:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers