I thought that case should be caught well before it gets to the driver. Can you retry with the LVM driver please?
On 27 February 2015 at 10:48, Eduard Matei <eduard.ma...@cloudfounders.com> wrote: > Hi, > > We've been testing our cinder driver extensively and found a strange > behavior in the UI: > - when trying to delete a snapshot that has clones (created volume from > snapshot) and error is raised in our driver which turns into > "error_deleting" in cinder and the UI; further actions on that snapshot are > impossible from the ui, the user has to go to CLI and do cinder > snapshot-reset-state to be able to delete it (after having deleted the > clones) > - to help with that we implemented a check in the driver and now we raise > exception.SnapshotIsBusy; now the snapshot remains available (as it should > be) but no error "bubble" is shown in the UI (only the green one: Success. > Scheduled deleting of...). So the user has to go to c-vol screen and check > the cause of the error > > So question: how should we handle this so that > a. The snapshot remains in state "available" > b. An error bubble is shown in the UI stating the cause. > > Thanks, > Eduard > > -- > > *Eduard Biceri Matei, Senior Software Developer* > www.cloudfounders.com > | eduard.ma...@cloudfounders.com > > > > *CloudFounders, The Private Cloud Software Company* > > Disclaimer: > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you are not the named addressee or an employee or agent responsible for > delivering this message to the named addressee, you are hereby notified that > you are not authorized to read, print, retain, copy or disseminate this > message or any part of it. If you have received this email in error we > request you to notify us by reply e-mail and to delete all electronic files > of the message. If you are not the intended recipient you are notified that > disclosing, copying, distributing or taking any action in reliance on the > contents of this information is strictly prohibited. > E-mail transmission cannot be guaranteed to be secure or error free as > information could be intercepted, corrupted, lost, destroyed, arrive late or > incomplete, or contain viruses. The sender therefore does not accept > liability for any errors or omissions in the content of this message, and > shall have no liability for any loss or damage suffered by the user, which > arise as a result of e-mail transmission. > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Duncan Thomas
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev