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 1332693

Summary: Installing RHEL 7.3 over 6.7GA, results in error message and quitting install.
Product: Red Hat Enterprise Linux 7 Reporter: Bill Sanford <bsanford>
Component: python-blivetAssignee: Blivet Maintenance Team <blivet-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.3CC: astepano, bsanford, dcantrell, jkoten, tpelka, vbenes
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-29 15:18:17 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:
Attachments:
Description Flags
File 1 of the anaconda logs
none
File 2 of the anaconda logs none

Description Bill Sanford 2016-05-03 19:40:46 UTC
Created attachment 1153558 [details]
File 1 of the anaconda logs

Description of problem:
Installing RHEL 7.3 over 6.7GA, results in error message and quitting install.

It seems like the 7.3 install can't handle the LVM VG from 6.7 and chokes on install.

Once the VG is manually removed, the 7.3 install will continue and not error.

Version-Release number of selected component (if applicable):
RHEL-6.7-20150702.0
RHEL-7.3-20160502.n.0

How reproducible:
100%

Steps to Reproduce:
1. Install 6.7GA
2. Install 7.3
3.

Actual results:


Expected results:


Additional info:

The anaconda-tb-uyC8nH file is here - http://pastebin.test.redhat.com/370862
The anaconda-tb-YpUlGp file is here - http://pastebin.test.redhat.com/370867

Comment 1 Bill Sanford 2016-05-03 19:43:30 UTC
Created attachment 1153560 [details]
File 2 of the anaconda logs

Comment 2 Bill Sanford 2016-05-04 14:52:52 UTC
I am putting Regression in the "Keywords" since I am installing RHEL 7.1 now and it has no bug that is seen in RHEL 7.3.

Comment 3 David Lehman 2016-08-16 15:15:27 UTC
What exactly happens when you run an installation over the problematic lvm layout using 7.1? How about 7.2?

Comment 4 David Lehman 2016-08-16 15:19:39 UTC
It would also be useful if you could run the following commands in the installer environment (after the failure has occurred) and attach the output files:

  lsblk >/tmp/lsblk.out

  udevadm --export-db >/tmp/udevdb


Thanks.

Comment 5 David Lehman 2016-08-16 15:20:23 UTC
That udevadm command should have been:

  udevadm info --export-db >/tmp/udevdb

Comment 6 Bill Sanford 2016-08-24 19:37:26 UTC
I have retested RHEL-6.7-20160427.1 to RHEL-7.3-20160817.1 and will verify this bug to be closed since this worked.