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:

After a RHEL7-Atomic installation, LVM or block-level metadata cruft is left on the system.  Trying to reprovision on top of this with RHEL7 will fail, the "fix" is to provision RHEL6.x and -then- RHEL7 Anaconda will not bomb out.

This is a repeatable issue on bare-metal hardware (Dell R620).
RHEL6.x and other EL6-based media (or Anaconda) does not have this issue.


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


How reproducible:

Always


Steps to Reproduce:
1. Install RHEL7-Atomic (via kickstart or other)
2. Try and provision RHEL7
3. Anaconda bombs out.

Actual results:


Expected results:


Additional info:

I was unable to get to the flat file logs (or start and use sshd) from a TTY via the iDRAC interface of the machine we're posting against, only screenshots.

Created attachment 1085592 [details]
provision screenshot

Created attachment 1085593 [details]
additional SELinux errors (may not be related)

Created attachment 1085594 [details]
Anaconda Tracebacks

Yeah, this is a known issue with Anaconda/LVM.  I commented in another bug, but in some cases you may have to drop to a shell and use `wipefs` beforehand.

I'll let the Anaconda team dedup/assign.

Please attach the logs from /tmp/*log as individual text/plain attachments.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.