`juju upgrade-juju --upload-tools` leaves local environment unusable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
1.24 |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
I've been running the devel releases of juju 1.24. Each upgrade, from beta1 -> beta2, beta2 -> beta3, and beta3-beta4, has left the local environment unusable.
My environment:
Trusty, running inside a Vagrant VM
Juju 1.24-beta3
provider: local
Steps to reproduce:
1) apt-get update && apt-get upgrade
2) verify new version with `juju version`
3) run `juju upgrade-juju --upload-tools`
Once the above steps are run, juju commands become non-responsive. The `juju status --debug` output shows a connection refused: https:/
I restarted `juju-agent-
The machine-0.log: https:/
I've been able to recreate this reliably with each beta upgrade. The only solution I've found is to `juju destroy-environment --force` and re-bootstrap.
Changed in juju-core: | |
milestone: | none → 1.24-beta5 |
importance: | Undecided → High |
Changed in juju-core: | |
status: | New → Triaged |
tags: | added: upgrade-juju vagrant |
description: | updated |
tags: | added: local-provider |
Changed in juju-core: | |
assignee: | nobody → Andrew Wilkins (axwalk) |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
I can repro, but it doesn't happen all the time for me. Looking into it.