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:
Actual 'lvconvert --type' usage for some operation is assigning incorrect command based on passed --type option.
Example:
1. creates raid: 'lvcreate -L10 -m1 -n lv vg'
2. converts region size: 'lvconvert --type raid1 -R512k vg/lv'
resulting into this error message:
Converting the segment type for vg/lv from raid1 to raid1 is not supported yet.
...
However in this case there is no segment type conversion - so the command
should processed as regular --regionsize change.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 2Heinz Mauelshagen
2017-04-05 22:04:17 UTC
Verified.
BEFORE PATCH:
[root@virt-368 ~]# lvcreate -L10 -m1 -n lv vg
Rounding up size to full physical extent 12.00 MiB
Logical volume "lv" created.
[root@virt-368 ~]# lvconvert --type raid1 -R512k vg/lv
Conversion operation not yet supported.
AFTER PATCH:
[root@virt-365 ~]# lvcreate -L10 -m1 -n lv vg
Rounding up size to full physical extent 12.00 MiB
Logical volume "lv" created.
[root@virt-365 ~]# lvconvert --type raid1 -R512k vg/lv
Do you really want to change the region_size 2.00 MiB of LV vg/lv to 512.00 KiB? [y/n]: y
Changed region size on RAID LV vg/lv to 512.00 KiB.
Logical volume vg/lv successfully converted.
3.10.0-671.el7.x86_64
lvm2-2.02.171-2.el7 BUILT: Wed May 24 16:02:34 CEST 2017
lvm2-libs-2.02.171-2.el7 BUILT: Wed May 24 16:02:34 CEST 2017
lvm2-cluster-2.02.171-2.el7 BUILT: Wed May 24 16:02:34 CEST 2017
device-mapper-1.02.140-2.el7 BUILT: Wed May 24 16:02:34 CEST 2017
device-mapper-libs-1.02.140-2.el7 BUILT: Wed May 24 16:02:34 CEST 2017
device-mapper-event-1.02.140-2.el7 BUILT: Wed May 24 16:02:34 CEST 2017
device-mapper-event-libs-1.02.140-2.el7 BUILT: Wed May 24 16:02:34 CEST 2017
device-mapper-persistent-data-0.7.0-0.1.rc6.el7 BUILT: Mon Mar 27 17:15:46 CEST 2017
cmirror-2.02.171-2.el7 BUILT: Wed May 24 16:02:34 CEST 2017
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-2017:2222