Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
If you run the command list with search by argument with not supported type, in few cases it returned listing for type without using search by argument, instead of some Error message. Lower you can find type, which should work with search by and types, that also works, but should not. I also noticed, that in man page is two times option --fs, in first one you require it with type SNAPSHOTS and in second one you declare, that --fs only support type FS, which is confusing.
--sys
should work with: VOLUMES, POOLS, FS, SNAPSHOTS, DISKS, ACCESS_GROUPS
also works with: NFS_CLIENT_AUTH, PLUGINS, TARGET_PORTS, BATTERIES
--pool
should work with: VOLUMES, POOLS, FS
also works with: NFS_CLIENT_AUTH, PLUGINS
--vol
should work with: VOLUMES, ACCESS_GROUPS
also works with: NFS_CLIENT_AUTH, PLUGINS
--disk
should work with: DISK
also works with: NFS_CLIENT_AUTH, PLUGINS
--ag
should work with: ACCESS_GROUPS, VOLUMES
also works with: NFS_CLIENT_AUTH, PLUGINS
--fs
should work with: FS
also works with: EXPORTS, NFS_CLIENT_AUTH, PLUGINS
--xfs-export
should work with: EXPORTS
also works with: NFS_CLIENT_AUTH, PLUGINS
--tgt
should work with: TARGET_PORTS
also works with: NFS_CLIENT_AUTH, PLUGINS
Version-Release number of selected component (if applicable):
1.4.0-3
How reproducible:
100%
Steps to Reproduce:
1.run lsmcli with command "list" using search by argument with wrong type for example: lsmcli -u "sim+ssl://" list --type NFS_CLIENT_AUTH --tgt TGT_PORT_ID_00001
Actual results:
List command with search by argument using wrong type argument passed.
Expected results:
It should return some Error message for example: lsmcli: error: Search key 'volume_id' is not supported by pool listing.
Additional info:
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