juju upgrade-juju --build-agent allows invalid upgrades
Bug #1732156 reported by
John A Meinel
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Christian Muirhead |
Bug Description
I was testing out some stuff with our betas, and I had done "juju bootstrap" with a 2.3-beta4 build.
I then hacked on some stuff and ended up with a 2.3-beta3 and had done "juju upgrade-juju --build-agent" which it happily uploaded and attempted to switch to, but ultimately all machines failed with:
$ juju show-machine 0
model: controller
machines:
"0":
juju-status:
current: error
message: 'upgrade to 2.3-beta3.1 failed (giving up): cannot sanely upgrade from
2.3-beta4.1 to 2.3-beta3.1'
I'm surprised it even allowed the "upgrade-juju" to pass without telling me that ahead of time.
Changed in juju: | |
assignee: | nobody → Christian Muirhead (2-xtian) |
Changed in juju: | |
milestone: | none → 2.3-rc1 |
Changed in juju: | |
milestone: | 2.3-rc1 → 2.3.1 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.3.1 → none |
Changed in juju: | |
milestone: | none → 2.3.2 |
Changed in juju: | |
milestone: | 2.3.2 → 2.3.3 |
To post a comment you must log in.
It gets worse, trying to build a new agent and then upgrade to it gives me: com/juju/ juju/rpc/ client. go:149: com/juju/ juju/api/ apiclient. go:925: com/juju/ juju/api/ modelconfig/ modelconfig. go:33:
ERROR upgrade in progress (upgrade in progress)
15:12:45 DEBUG cmd supercommand.go:459 error stack:
upgrade in progress (upgrade in progress)
github.
github.
github.
So I can't use upgrade-juju to get back out of this.