Upgrades broken in 1.22 tip
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
High
|
Unassigned | ||
| | 1.22 |
Critical
|
Unassigned | ||
Bug Description
As seen at
http://
2015-10-28 07:14:56 ERROR juju.cmd supercommand.go:430 no matching tools available
Juju cannot upgrade after the commit of
https:/
The commit can be backed put or fixed.
| Changed in juju-core: | |
| status: | Triaged → Incomplete |
| Curtis Hovey (sinzui) wrote : | #1 |
| Curtis Hovey (sinzui) wrote : | #2 |
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 "toolsversionch
| description: | updated |
| Cheryl Jennings (cherylj) wrote : | #3 |
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.
| Changed in juju-core: | |
| status: | Incomplete → Won't Fix |


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.