juju disable-command all includes run-action
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Wishlist
|
Tim McNamara |
Bug Description
Actions in charms are deemed 'safe' and standard operations, and therefore should not be disabled by disable-command all (or, an exception should be available for them). For example:
jujumanage@
unit-mysql-2:
id: ed06d1cb-
results:
outcome: Success
time-completed: 2018-09-27 23:19:20
status: completed
timing:
completed: 2018-09-27 23:19:10 +0000 UTC
enqueued: 2018-09-27 23:19:01 +0000 UTC
started: 2018-09-27 23:19:02 +0000 UTC
unit: mysql/2
jujumanage@
jujumanage@
ERROR the operation has been blocked (operation is blocked)
jujumanage@
ERROR flag provided but not defined: --force
jujumanage@
ERROR bad command set, valid options: all, destroy-model, remove-object
Changed in juju: | |
milestone: | 2.6-rc1 → 2.6-rc2 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Thanks, this is tough as folks tend to think of locked when the disable all is there. I agree that allowing an opening of things from there for actions is appropriate.