Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI
@Duncan: I tried with lvmdriver-1, fails with error: ImageCopyFailure: Failed to copy image to volume: qemu-img: /dev/mapper/stack--volumes--lvmdriver--1-volume--e8323fc5--8ce4--4676--bbec--0a85efd866fc: error while converting raw: Could not open device: Permission denied It's been configured with 2 drivers (ours, and lvmdriver), but our driver works, so not sure where it fails. Eduard On Mon, Mar 2, 2015 at 8:23 AM, Eduard Matei eduard.ma...@cloudfounders.com wrote: Thanks @Duncan: I'll try with the lvm driver. @Avishay, i'm not trying to delete a volume created from a snapshot, i'm trying to delete a snapshot that has volumes created from it (actually i need to prevent this action and properly report the cause of the failure: SnapshotIsBusy). Eduard On Mon, Mar 2, 2015 at 7:57 AM, Avishay Traeger avis...@stratoscale.com wrote: Deleting a volume created from a snapshot is permitted. Performing operations on a volume created from snapshot should have the same behavior as volumes created from volumes, images, or empty (no source). In all of these cases, the volume should be deleted, regardless of where it came from. Independence from source is one of the differences between volumes and snapshots in Cinder. The driver must take care to ensure this. As to your question about propagating errors without changing an object's state, that is unfortunately not doable in Cinder today (or any other OpenStack project as far as I know). The object's state is currently the only mechanism for reporting an operation's success or failure. On Sun, Mar 1, 2015 at 6:07 PM, Duncan Thomas duncan.tho...@gmail.com wrote: 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 -- *Avishay Traeger* *Storage RD* Mobile: +972 54 447 1475 E-mail: avis...@stratoscale.com Web http://www.stratoscale.com/ | Blog http://www.stratoscale.com/blog/ | Twitter https://twitter.com/Stratoscale | Google+
Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI
Thanks Avishay. In our case the middle layer (our storage appliance) doesn't allow a snapshot to be deleted if it has clones due to an internal implementation that tries to optimize storage by using a Dependency tree where the base volume is the root of the tree and snapshots or clones are nodes and their clones are leaves of. So deleting a middle point (node) is impossible without deleting all the children. Eduard On Mon, Mar 2, 2015 at 8:10 PM, Avishay Traeger avis...@stratoscale.com wrote: Sorry, I meant to say that the expected behavior is that volumes are independent entities, and therefore you should be able to delete a snapshot even if it has volumes created from it (just like you should be able to delete a volume that has clones from it). The exception is that Cinder will not permit you to delete a volume that has snapshots. On Mon, Mar 2, 2015 at 3:22 PM, Eduard Matei eduard.ma...@cloudfounders.com wrote: @Duncan: I tried with lvmdriver-1, fails with error: ImageCopyFailure: Failed to copy image to volume: qemu-img: /dev/mapper/stack--volumes--lvmdriver--1-volume--e8323fc5--8ce4--4676--bbec--0a85efd866fc: error while converting raw: Could not open device: Permission denied It's been configured with 2 drivers (ours, and lvmdriver), but our driver works, so not sure where it fails. Eduard On Mon, Mar 2, 2015 at 8:23 AM, Eduard Matei eduard.ma...@cloudfounders.com wrote: Thanks @Duncan: I'll try with the lvm driver. @Avishay, i'm not trying to delete a volume created from a snapshot, i'm trying to delete a snapshot that has volumes created from it (actually i need to prevent this action and properly report the cause of the failure: SnapshotIsBusy). Eduard On Mon, Mar 2, 2015 at 7:57 AM, Avishay Traeger avis...@stratoscale.com wrote: Deleting a volume created from a snapshot is permitted. Performing operations on a volume created from snapshot should have the same behavior as volumes created from volumes, images, or empty (no source). In all of these cases, the volume should be deleted, regardless of where it came from. Independence from source is one of the differences between volumes and snapshots in Cinder. The driver must take care to ensure this. As to your question about propagating errors without changing an object's state, that is unfortunately not doable in Cinder today (or any other OpenStack project as far as I know). The object's state is currently the only mechanism for reporting an operation's success or failure. On Sun, Mar 1, 2015 at 6:07 PM, Duncan Thomas duncan.tho...@gmail.com wrote: 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
Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI
Sorry, I meant to say that the expected behavior is that volumes are independent entities, and therefore you should be able to delete a snapshot even if it has volumes created from it (just like you should be able to delete a volume that has clones from it). The exception is that Cinder will not permit you to delete a volume that has snapshots. On Mon, Mar 2, 2015 at 3:22 PM, Eduard Matei eduard.ma...@cloudfounders.com wrote: @Duncan: I tried with lvmdriver-1, fails with error: ImageCopyFailure: Failed to copy image to volume: qemu-img: /dev/mapper/stack--volumes--lvmdriver--1-volume--e8323fc5--8ce4--4676--bbec--0a85efd866fc: error while converting raw: Could not open device: Permission denied It's been configured with 2 drivers (ours, and lvmdriver), but our driver works, so not sure where it fails. Eduard On Mon, Mar 2, 2015 at 8:23 AM, Eduard Matei eduard.ma...@cloudfounders.com wrote: Thanks @Duncan: I'll try with the lvm driver. @Avishay, i'm not trying to delete a volume created from a snapshot, i'm trying to delete a snapshot that has volumes created from it (actually i need to prevent this action and properly report the cause of the failure: SnapshotIsBusy). Eduard On Mon, Mar 2, 2015 at 7:57 AM, Avishay Traeger avis...@stratoscale.com wrote: Deleting a volume created from a snapshot is permitted. Performing operations on a volume created from snapshot should have the same behavior as volumes created from volumes, images, or empty (no source). In all of these cases, the volume should be deleted, regardless of where it came from. Independence from source is one of the differences between volumes and snapshots in Cinder. The driver must take care to ensure this. As to your question about propagating errors without changing an object's state, that is unfortunately not doable in Cinder today (or any other OpenStack project as far as I know). The object's state is currently the only mechanism for reporting an operation's success or failure. On Sun, Mar 1, 2015 at 6:07 PM, Duncan Thomas duncan.tho...@gmail.com wrote: 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 __
Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI
Deleting a volume created from a snapshot is permitted. Performing operations on a volume created from snapshot should have the same behavior as volumes created from volumes, images, or empty (no source). In all of these cases, the volume should be deleted, regardless of where it came from. Independence from source is one of the differences between volumes and snapshots in Cinder. The driver must take care to ensure this. As to your question about propagating errors without changing an object's state, that is unfortunately not doable in Cinder today (or any other OpenStack project as far as I know). The object's state is currently the only mechanism for reporting an operation's success or failure. On Sun, Mar 1, 2015 at 6:07 PM, Duncan Thomas duncan.tho...@gmail.com wrote: 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 -- *Avishay Traeger* *Storage RD* Mobile: +972 54 447 1475 E-mail: avis...@stratoscale.com Web http://www.stratoscale.com/ | Blog http://www.stratoscale.com/blog/ | Twitter https://twitter.com/Stratoscale | Google+ https://plus.google.com/u/1/b/108421603458396133912/108421603458396133912/posts | Linkedin https://www.linkedin.com/company/stratoscale __ 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
Re: [openstack-dev] [cinder][horizon]Proper error handling/propagation to UI
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
[openstack-dev] [cinder][horizon]Proper error handling/propagation to UI
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
