[Bug 1782008] Re: Unable to force delete a volume
peter.matulis at canonical.com
Thu Dec 5 20:44:20 UTC 2019
I see this in /etc/cinder/policy.json:
Is that what fixed this? Wouldn't this constitute an override of the
default? Don't we want to actually fix the default?
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Ubuntu.
Unable to force delete a volume
Status in OpenStack cinder charm:
Status in OpenStack nova-compute charm:
Status in cinder package in Ubuntu:
By default, a project user cannot force delete a cinder volume, as may
be necessary if a volume is stuck in a bad state for whatever
reason/malfunction of the underlying cloud or storage.
A volume is stuck in a 'creating' state.
| 7b3cbee8-fad5-4f35-8c81-c794cdcb494f | juju-404c2e-auto-osci-
sv04-volume-1 | creating | 40 |
ubuntu at osci-bastion:~/git/charm-test-infra$ openstack volume delete --force 9efe89e2-6d2e-474d-b570-0657944af8de
Failed to delete volume with name or ID '9efe89e2-6d2e-474d-b570-0657944af8de': Policy doesn't allow volume_extension:volume_admin_actions:force_delete to be performed. (HTTP 403) (Request-ID: req-b97d3bf7-aac9-42a7-89e0-c3e1306b3b04)
1 of 1 volumes failed to delete.
Force deleting as admin succeeds.
To manage notifications about this bug go to:
More information about the Ubuntu-openstack-bugs