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 1873236

Summary: Anaconda doesn't warn the user of a missing PReP partition
Product: Red Hat Enterprise Linux 8 Reporter: Jiri Kortus <jikortus>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.3CC: bugproxy, hannsj_uhl, jstodola
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.4   
Hardware: ppc64le   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-04 09:11:52 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:
Bug Depends On:    
Bug Blocks: 1796871, 1812825    

Description Jiri Kortus 2020-08-27 16:59:43 UTC
Description of problem:
It's possible to manually create a partitioning without PReP partition, without getting warned by anaconda that such a partitioning is inappropriate. 

Version-Release number of selected component (if applicable):
anaconda-33.16.3.21-1.el8.ppc64le

How reproducible:
unknown

Steps to Reproduce:
1. Start manual graphical installation on a ppc64le machine.
2. Enter partitioning spoke, select drives to be partitioned and enter custom partitioning spoke.
3. Remove existing partitions and create a partitioning  without a PReP partition.
4. Click on 'Done' button.

Actual results:
Anaconda allows for exiting the partitioning spoke with invalid partitioning without showing a warning message.

Expected results:
Anaconda shows a warning message and allows the user to exit the advanced partitioning spoke only after clicking on 'Done' button for a second time.

Additional info:
I found this bug when inspecting automated test results, however I haven't been able to reproduce it yet. I will try to reproduce it on the same machine where the bug was spotted once it becomes available.

Comment 6 Jan Stodola 2020-09-03 08:35:27 UTC
This could be related to bug 1853619.
If that's true, this bug should be reproducible on bare metal systems, but not on VMs.

Comment 8 Jan Stodola 2020-09-04 09:11:52 UTC
I'm closing this bug as a duplicate of bug 1853619, they are both reproducible on the same type of machines (PowerNV)

*** This bug has been marked as a duplicate of bug 1853619 ***