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.
+++ This bug was initially created as a clone of Bug #1024076 +++
Originally abrt dinged bug 1021507 with this.
Description of problem: When creating a thinpool LV with the same name as existing, I get a crash; by default for thinpool LV's, the installer isn't checking for existing names and can propose a default name for a new LV for an existing LV of the same name thus running into the crash.
Version-Release number of selected component (if applicable):
anaconda-20.25.4-1
How reproducible:
Always when new name = existing name, but so far only with Thin Provisioning does this happen by default.
Steps to Reproduce:
1. Minimal package set install to single disk, single LVM Thin Provisioning via Guided path.
2. Reboot to installer, custom path.
3. Remove existing fedora-home LV.
4. Reuse existing fedora-swap LV.
5. Create new mount point / without size value.
[I note that it makes the name of the LV "root" which is the same as existing LV.]
6. Begin installation.
Actual results:
Crash.
Expected results:
Error message about the conflicting new and existing names instead of crash.
LVM thin provisioning should check existing name and propose a non-conflicting name, which is how conventional LVM works.
Additional info:
--- Additional comment from David Lehman on 2013-10-28 15:35:03 EDT ---
Here's a link to an updates image that should fix this problem:
http://dlehman.fedorapeople.org/updates/updates-1024076.0.img
Please report back with results.
--- Additional comment from Chris Murphy on 2013-10-28 17:31:02 EDT ---
With updates image applied, adding a new root LV as device LVM Thin Provisioning, the problem doesn't occur in that the new / is named root00. If I try to intentionally change it to root, it snaps back to root00.
--- Additional comment from Chris Murphy on 2013-10-30 19:29:27 EDT ---
Bug is fixed, marking as verified, remaining crash discussed in bug 1024144.
Clarified steps, attempting to reproduce this bug with the updates.img:
1. Minimal package set install to single disk, single LVM Thin Provisioning via Guided path.
2. Reboot to installer, with comment 5 updates.img applied, custom partition path, with Partition Scheme pop-up set to LVM Thin Provisioning.
3. Remove existing fedora-home LV.
4. Reuse existing fedora-swap LV.
4. Reuse existing /boot by reformatting.
6. Create new mount point / without size value.
7. Begin installation.
Succeeds and is bootable.
This bug was about new thinp LV's by default named the same as existing, then crashing, and that's no longer happening with updates.img: new LV is named differently by default, and even if I try to intentionally name it the same as existing, I'm thwarted. Thus, this is fixed.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.