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.

Bug 1571894

Summary: lsmcli [command] --init "wrong" return --init-id "None" in error instead of --init "wrong"
Product: Red Hat Enterprise Linux 7 Reporter: Jakub Krysl <jkrysl>
Component: libstoragemgmtAssignee: Tony Asleson <tasleson>
Status: CLOSED ERRATA QA Contact: Jakub Krysl <jkrysl>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.6CC: tasleson
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 12:40:24 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:

Description Jakub Krysl 2018-04-25 15:44:22 UTC
Description of problem:
When --init is given wrong value, the error message contains "None" instead of this value. Plus the parameter is --init and not --init-id as said in the message.

# lsmcli -u "sim://" access-group-create --name test --sys sim-01 --init "wrong"
lsmcli: error: --init-id None is not a valid WWPN or iSCSI IQN
# lsmcli -u "sim://" access-group-create --name test --sys sim-01 --init 0
lsmcli: error: --init-id None is not a valid WWPN or iSCSI IQN

# lsmcli -u "sim://" access-group-remove --ag AG_ID_00001 --init "wrong"
lsmcli: error: --init-id None is not a valid WWPN or iSCSI IQN


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

How reproducible:
100%

Steps to Reproduce:
1.# lsmcli -u "sim://" access-group-create --name test --sys sim-01 --init "wrong"

Actual results:
lsmcli: error: --init-id None is not a valid WWPN or iSCSI IQN

Expected results:
lsmcli: error: --init "wrong" is not a valid WWPN or iSCSI IQN

Additional info:

Comment 3 Jakub Krysl 2019-01-28 16:58:06 UTC
libstoragemgmt-1.7.2-1.el7.x86_64

# lsmcli -u "sim://" iscsi-chap --init='WRONG'
usage: lsmcli iscsi-chap [-h] [-v] [-u <URI>] [-P] [-H] [-t <SEP>] [-e] [-f]
                         [-w CHILD_WAIT] [--header] [-b] [-s] --init <INIT_ID>
                         [--in-user <IN_USER>] [--in-pass <IN_PASS>]
                         [--out-user <OUT_USER>] [--out-pass <OUT_PASS>]
lsmcli iscsi-chap: error: argument --init: "WRONG" is invalid WWPN or iSCSI IQN

Comment 5 errata-xmlrpc 2019-08-06 12:40:24 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-2019:2064