Unable to delete a service after deployment failed

[Fabrice Matrat]

Add Test Charms in Canvas
Assign it to a machine
Click deploy
Deploy is failing
Try to remove the service
Removing failed.

[Fabrice Matrat (fabricematrat)]

In MV
testcharm/0 will be destroyed once you have committed your changes but there is nothing to commit

[Jeff Pihach (hatch)]

I believe what you're seeing is an intentional functionality of Juju. You cannot destroy a service which has units that are in an error'd state.

[Fabrice Matrat (fabricematrat)]

The strange part is that when I do a full refresh of the page the unit is gone. This seems understandable as it was never even deployed.

[Kyle Adams (kadams54)]

Yeah, it seems like something is definitely funky here. If we don't allow destroying services with units that are in error state, than we need a notification to that effect. As it is, the service changes to an uncommitted state (blue border) in the canvas and the unit is never actually removed from MV, despite everything seeming to go well (unit removal shows up in deploy summary, no error notifications post-commit).

Here's what I did to replicate in an EC2 env:

1) Drag the "test" charm (cs:~hloeung/precise/test-1) to the canvas and deploy.
2) Hopefully it will fail on deploy?
3) Switch to machine view.
4) Destroy the service in the inspector.
5) Commit changes (note the service and the unit both show up in deploy summary).
6) Switch back to the service view. Note that the service now shows up as uncommitted.

I've also tried removing just the unit first (using the "Destroy" link in its more menu in MV) and that also does not work.