Removal of subordinate in error state is not smooth
Bug #2006968 reported by
Alan Baghumian
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Hello Juju Team!
It would be awesome if the removal of units that contain subordinate units in error state is easier.
Currently we have to constantly run:
$ juju resolve <subordinate unit> --no-retry
And monitor the state to go through every single failed hook before being able to finally remove the unit. A lot of manual intervention that quickly becomes really annoying specially when dealing with multiple units.
Essentially, if Juju runs the above resolve/no-retry command automatically if a subordinate unit is in error state, it would avoid all of this manual process.
Please let me know if you have any questions.
Best,
Alan
Changed in juju: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
To post a comment you must log in.