Repository navigation
role with expungeVirtualMachine #14674
Replies: 1 comment 1 reply
|
There is an additional capability check in the current UI, beyond allowing the API in the role. In DestroyVM.vue,
That capability is exposed by Check If you mean the separate Expunge action after destruction, its The setting permits recovery as well as expunge, so its effective scope should match your account |

There is an additional capability check in the current UI, beyond allowing the API in the role.
In DestroyVM.vue,
the Expunge option in the destroy dialog requires both:
expungeVirtualMachinein the user's available APIs; andallowuserexpungerecovervmcapability.That capability is exposed by
listCapabilities. Have an administrator check the effectiveallow.user.expunge.recover.vmconfiguration for the affected account. Itsconfiguration definition
defaults to
falseand supports account scope. Allowing the API through a custom role does not itselfenable that configuration.
Check
listCapabilitieswhile signed in as the affected user, rather than comparing only …