Destroying containers with units on them gives an error and no way to resolve
Bug #1368585 reported by
Huw Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-gui |
Triaged
|
High
|
Unassigned | ||
Bug Description
To reproduce:
- add a service
- create a machine and a container
- drag the unplaced unit onto the container
- deploy your changes
- using the container's 'more menu' click Destroy
- commit your changes
- you will get an error: "Error destroying machine or container... no machines were destroyed: machine 0/lxc/0 has unit(s) mysql/1 assigned"
- the container will still read "0/lxc/0 will be destroyed once you have committed your changes"
- the destroy options in the units' 'more menus' will be disabled so there's no way to now remove those units if that is the intended way to fix the issue.
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
To post a comment you must log in.
I think the best way for us to move this forward is to work on the feature that's on the todo list that is we should generate a full stack of changes in the ecs for a delete request of an item that has a series of items inside of it.