| 2015-05-22 14:03:32 |
Curtis Hovey |
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.23-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://gist.github.com/AdamIsrael/0c67c8553bb0a485e9ca
I restarted `juju-agent-vagrant-local`, and there is a short window that I'm able to run `juju status` before it hangs with the same connection refused error. Here's the output of `juju status` in that window: https://gist.github.com/AdamIsrael/b97ef47ebecb82219dce
The machine-0.log: https://gist.github.com/AdamIsrael/aa18a0d651f3f7735dda
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. |
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://gist.github.com/AdamIsrael/0c67c8553bb0a485e9ca
I restarted `juju-agent-vagrant-local`, and there is a short window that I'm able to run `juju status` before it hangs with the same connection refused error. Here's the output of `juju status` in that window: https://gist.github.com/AdamIsrael/b97ef47ebecb82219dce
The machine-0.log: https://gist.github.com/AdamIsrael/aa18a0d651f3f7735dda
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. |
|
