Upgraded juju to 1.24 dies shortly after starting
Bug #1466565 reported by
Adam Collard
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
Undecided
|
Unassigned | ||
1.23 |
Won't Fix
|
High
|
Menno Finlay-Smits | ||
1.24 |
Invalid
|
High
|
Menno Finlay-Smits |
Bug Description
On a local provider that was upgraded from 1.23.3.1 to 1.24, jujud comes up briefly but then dies.
1.24.0-
machine-0.log after "sudo restart juju-agent-
http://
juju status just hangs, failing to connect to the websocket
2015-06-18 15:54:00 DEBUG juju.api apiclient.go:337 error dialing "wss://
I haven't tested it on different providers, as generally I deploy from scratch.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.24.1 |
Changed in juju-core: | |
assignee: | nobody → Katherine Cox-Buday (cox-katherine-e) |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | Invalid → Confirmed |
tags: | added: cts sts |
Changed in juju-core: | |
assignee: | Katherine Cox-Buday (cox-katherine-e) → nobody |
milestone: | 1.24.1 → 1.25.0 |
Changed in juju-core: | |
status: | Incomplete → Triaged |
Changed in juju-core: | |
assignee: | nobody → Menno Smits (menno.smits) |
no longer affects: | juju-core |
Changed in juju-core: | |
status: | New → Invalid |
tags: | added: kanban-cross-team |
To post a comment you must log in.
Note that the upgrade itself was ... a little tricky. I think I ended up running "juju upgrade-juju --version=1.24.0" a few times after having changed agent-stream to proposed (before 1.24.0 hit the mainstream)