Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1562389

Summary: [RFE] support snapshot create/delete/rollback within gwcli
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Jason Dillaman <jdillama>
Component: iSCSIAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Manohar Murthy <mmurthy>
Severity: medium Docs Contact: John Brier <jbrier>
Priority: medium    
Version: 3.0CC: agunn, ceph-eng-bugs, ceph-qe-bugs, jbrier, kdreyer, tchandra
Target Milestone: rcKeywords: FutureFeature
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-iscsi-cli-2.7-6.el7cp Doc Type: Enhancement
Doc Text:
.iSCSI gateway command-line utility (`gwcli`) supports snapshot create, delete, and rollback capabilities Previously, to manage the snapshots of RBD-backed LUN images the `rbd` command line utility was utilized for this purpose. The `gwcli` utility now includes built-in support for managing LUN snapshots. With this release, all snapshot related operations can now be handled directly within the `gwcli` utility.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-26 18:19:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1584264    

Description Jason Dillaman 2018-03-30 13:43:27 UTC
Description of problem:
An operator should be able to create, delete, and rollback image snapshots using the gwcli instead of the rbd CLI.

Comment 3 Mike Christie 2018-04-11 17:22:51 UTC
Link to more upstream info:

https://github.com/ceph/ceph-iscsi-cli/projects/2#card-7468504

Comment 18 errata-xmlrpc 2018-09-26 18:19:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2819