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:
There is a difference between --help and manpage with command lsmcli volume-replicate-range and its parameter --rep-type. Manpage allows only 2 replication types CLONE and COPY but --help allows 4: CLONE, COPY, MIRROR_ASYNC, MIRROR_SYNC.
All 4 of these replication types are allowed on command line, so manpage is probably the wrong one.

Version-Release number of selected component (if applicable):
1.4.0

How reproducible:
100%

Steps to Reproduce:
compare these 2 for 'lsmcli -u XXX volume-replicate-range --rep-type'
1.lsmcli volume-replicate-range --help
2.man lsmcli

Actual results:
Manpage and --help difference.

Expected results:
Both saying the same thing.

Additional info:

Patch has been submitted to upstream for review:
https://github.com/libstorage/libstoragemgmt/pull/314

Manpage and lsmcli volume-replicate-range now list only CLONE and COPY replication type. Trying MIRROR_SYNC or MIRROR_ASYNC is not allowed now:
# lsmcli -u "sim://" volume-replicate-range --src-vol VOL_ID_00001 --dst-vol VOL_ID_00001 --rep-type MIRROR_ASYNC --src-start 0 --dst-start 0 --count 10
usage: lsmcli volume-replicate-range [-h] [-v] [-u <URI>] [-P] [-H] [-t <SEP>]
                                     [-e] [-f] [-w CHILD_WAIT] [--header] [-b]
                                     [-s] --src-vol <SRC_VOL_ID> --dst-vol
                                     <DST_VOL_ID> --rep-type <REP_TYPE>
                                     --src-start <SRC_START_BLK> --dst-start
                                     <DST_START_BLK> --count <BLK_COUNT>
lsmcli volume-replicate-range: error: argument --rep-type: invalid choice: 'MIRROR_ASYNC' (choose from 'CLONE', 'COPY')

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