Bug 1461895 - lsmcli fs-snap-restore fail with INVALID_ARGUMENT(101): Invalid parameter combination with correct parameters
lsmcli fs-snap-restore fail with INVALID_ARGUMENT(101): Invalid parameter com...
Status: POST
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libstoragemgmt (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Gris Ge
Jakub Krysl
:
Depends On:
Blocks: 1469559
  Show dependency treegraph
 
Reported: 2017-06-15 10:22 EDT by Jakub Krysl
Modified: 2017-08-02 03:00 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jakub Krysl 2017-06-15 10:22:43 EDT
Description of problem:
Trying to restore snapshot on NetApp ONTAP through iSCSI using libstoragemgmt fails with: 
INVALID_ARGUMENT(101): Invalid parameter combination
This happens despite the fact, both snap_id and fs_id are correct.

Version-Release number of selected component (if applicable):
libstoragemgmt-1.4.0-3.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. create volume (lsmcli fs-create --name <FS_NAME> --size <SIZE> --pool <POOL_ID>)
2. get ID of that volume (lsmcli list --type FS)
3. create snapshot on that volume (lsmcli fs-snap-create --name <SNAP_NAME> --fs <FS_ID>
4. get ID of that snapshot (lsmcli list --type SNAPSHOTS)
5. try to restore volume from that snapshot (lsmcli fs-snap-restore --snap <SNAP_ID> --fs <FS_ID>)

Actual results:
error saying INVALID_ARGUMENT(101): Invalid parameter combination

Expected results:
Volume successfully restored from snapshot
Comment 2 Gris Ge 2017-06-15 10:33:12 EDT
Patch has been sent to upstream to review:
https://github.com/libstorage/libstoragemgmt/pull/272

Note You need to log in before you can comment on or make changes to this bug.