Bug 1461895
Summary: | lsmcli fs-snap-restore fail with INVALID_ARGUMENT(101): Invalid parameter combination with correct parameters | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jakub Krysl <jkrysl> |
Component: | libstoragemgmt | Assignee: | Gris Ge <fge> |
Status: | CLOSED ERRATA | QA Contact: | Jakub Krysl <jkrysl> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.4 | CC: | bgoncalv |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libstoragemgmt-1.5.0-2.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 15:36:35 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: | 1469559 |
Description
Jakub Krysl
2017-06-15 14:22:43 UTC
Patch has been sent to upstream to review: https://github.com/libstorage/libstoragemgmt/pull/272 Fixed in libstoragemgmt-1.5.0-2.el7. Before: # lsmcli -u "ontap://user@address" -P fs-snap-restore --snap 8934c6609a253816dd10acd46a7fd585 --fs c2becf55-e25e-4297-bcb8-5fb481bc7095 Password: Warning: You are about to do an operation that will cause data to be lost! Press [Y|y] to continue, any other key to abort INVALID_ARGUMENT(101): Invalid parameter combination # After: # lsmcli -u "ontap://user@address" -P fs-snap-restore --snap 8934c6609a253816dd10acd46a7fd585 --fs c2becf55-e25e-4297-bcb8-5fb481bc7095 Password: Warning: You are about to do an operation that will cause data to be lost! Press [Y|y] to continue, any other key to abort # 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/RHEA-2018:0864 |