juju status not being helpful when failing to provision
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned |
Bug Description
If I bootstrap a controller in aws then try to deploy a windows machine:
juju deploy juju deploy cs:~cloudbaseit
The unit will stay in allocating, but according to the controller logs it's never going to work because of mistakes I've made:
2017-01-05 14:33:01 WARNING juju.provisioner provisioner_
2017-01-05 14:33:11 ERROR juju.provisioner provisioner_
It would be nice if juju status showed that there was some problem I needed to look at, rather than just appear to be stuck in allocating.
In addition, when removing the application the machine is still listed in juju status until you run juju remove-machine
summary: |
- juju not being helpful when failing to provision + juju status not being helpful when failing to provision |
tags: | added: status |
description: | updated |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.2.0 |
tags: | added: usability |
Changed in juju: | |
milestone: | 2.1.0 → 2.1-rc1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
This is a pretty serious UX issue, imo.