search

ManageIQ / manageiq-providers-openstack

ManageIQ plugin for the OpenStack provider.
https://www.openstack.org/
Apache License 2.0
12 stars 92 forks source link

Support setting the 'force' flag when creating a new Instance snapshot #499

Open miq-bot opened 5 years ago

miq-bot commented 5 years ago

This request completes via Horizon, but in ManageIQ it fails with the error message: "Unable to create snapshot for Cloud Volume "xyz_volume": Invalid volume: Volume xyz_volume status must be available, but current status is: in-use."

This issue was moved to this repository from https://github.com/ManageIQ/manageiq/issues/18995, originally opened by @lodgenbd

mansam commented 5 years ago

The error message you are seeing is a message from Cinder. You don't see that message in Horizon because it automatically applies the force flag if the volume is in use, which is not a safe operation.

lodgenbd commented 5 years ago

Gotcha, thanks for the reply. My question, then, is whether the implementation of features such as snapshotting are expected to emulate the same functionality as the original provider intended (in this case, openstack) or would ManageIQ intend to make their own decisions on what types of flags like that should be acceptable? I'm purely asking so I can set my own expectations, as my expectations currently were at a level of expecting functionality within Horizon to be available in ManageIQ. Similar to how I would expect snapshotting within the VMware provider to work the same way it does in ESXi/vCenter. I'm definitely not implying that my expectations are appropriate, simply trying to level-set.

mansam commented 5 years ago

We aim to support the functionality of Openstack but we don't set out to emulate the idiosyncrasies of the Horizon dashboard. Having a checkbox to set the force flag here would be ideal since that's available in the the CLI and API, but we wouldn't want to default to unsafe behavior the user doesn't know about because Horizon does it.

lodgenbd commented 5 years ago

I'm with ya there. I do see that the force checkbox is available on the backup functionality. It, too, gives a failure message if the volume is "in-use" and you don't check the box, but succeeds if you do check force. Maybe we can mirror that code for snapshots.

miq-bot commented 4 years ago

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!