Juju recommends incorrect command for enabling operation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Hello, while testing out the disable-command functionality, I found that Juju will sometimes recommend an incorrect action to enable a command:
$ juju disabled-commands
Disabled commands Message
all
$ juju remove-unit ubuntu/0
ERROR the operation has been blocked (operation is blocked)
All operations that remove machines, applications, units or
relations have been disabled for the current model.
To enable removal, run
juju enable-command remove-object
$ juju enable-command remove-object
$ juju remove-unit ubuntu/0
ERROR the operation has been blocked (operation is blocked)
All operations that remove machines, applications, units or
relations have been disabled for the current model.
To enable removal, run
juju enable-command remove-object
I'll create a separate bug for the granular control, but for this, I believe Juju's recommendation shouldn't suggest remove-object, because it's blocked by the "all" option. Additionally, if the enable-command doesn't work as expect, Juju should surface that to the operator.
Thanks for your time!
Changed in juju: | |
milestone: | none → 2.9.28 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.9.28 → 2.9.29 |
Changed in juju: | |
milestone: | 2.9.29 → 2.9.30 |
Changed in juju: | |
milestone: | 2.9.30 → 2.9.31 |
Changed in juju: | |
milestone: | 2.9.31 → none |
I think this and bug 1960943 could possibly be combined into the one issue.