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 1172755

Summary:	The PReP Boot manipulations lead to unexpected results
Product:	Red Hat Enterprise Linux 7	Reporter:	Jaromír Cápík <jcapik>
Component:	anaconda	Assignee:	rmarshall
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	jvavra, mbanas, ovasik
Target Milestone:	rc
Target Release:	---
Hardware:	ppc64
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-21.48.22.24-1	Doc Type:	Bug Fix
Doc Text:	Cause: Internal Mount Point being set to format.type (prepboot) for PPC PReP Boot devices. Consequence: Custom and automatic partition for new devices would create the name in the GUI based on format.type which is prepboot and not the format name which is PPC PReP Boot. Subsequent updates to any other device would then update it to the actual format name. Fix: Changed the code that generates the fake mount point to use format.name instead of format.type Result: Now, no matter how it is made or when it is made, prepboot partitions show up in the GUI as PPC PReP Boot.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 09:50:28 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:

Description Jaromír Cápík 2014-12-10 16:52:57 UTC

Description of problem:
I always get a crash in the installer when trying to create the PReP Boot partition manually (Bug 1170294), but even when I create the PReP Boot partition automatically, it leads to unexpected results. The PReP Boot entry is not shown in the SYSTEM list and the rest partitions have numbers starting from 2 (e.g. mpatha2). Once I confirm the changes and return to the manual partitioning, the PReP Boot partition is suddenly there (written with small letters - "prepboot") and has the number 1 (e.g. mpatha1). However the order of entries in the list is a bit strange. It is sorted neither by numbers nor alphabetically.

Version-Release number of selected component (if applicable):
RHEL-7.1-20141201.0-Server

How reproducible:
always

Comment 2 Jaromír Cápík 2014-12-10 17:06:29 UTC

NOTE: If you create a standard partition with a filesystem on it (or swap) and then change what is incorrectly called filesystem to "PPC PReP Boot", then the list contains "PPC PReP Boot" with capital and small letters. So, in this case we display the same partition using two different labels.

Comment 3 Jaromír Cápík 2014-12-10 17:20:43 UTC

NOTE2: If you create the PReP Boot partition using the procedure from Comment 2, then the partition does one of the two following things after adding or removing a different mountpoint:

1.) changes the label from "PPC PReP Boot" to "prepboot"
-OR-
2.) disappears from the list

I haven't tried to find reliable reproduction scenarios leading to the #1 or #2 and I hope you'll be able to reproduce these by yourself and find the reason why it behaves so unexpectedly.

Comment 4 Jaromír Cápík 2014-12-10 17:32:29 UTC

NOTE3: A minute ago I experienced an unexpected rename from "prepboot" to "PPC PReP Boot" after changing a filesystem of the /boot mountpoint from xfs to ext4.

Comment 6 Jakub Vavra 2015-08-26 12:13:07 UTC

Fixed in compose RHEL-7.2-20150820.0 anaconda 21.48.22.35-1. (checked on ppc64le). The label is not editable anymore for prepboot and when fs is switched from something else to prepboot is properly cleared. The Doc Text seems to be reasonable.

Comment 7 Jakub Vavra 2015-08-26 12:15:05 UTC

Note: Any hacking around with sizes and fstypes mountpoints for prepboot did not result in error.

Comment 8 errata-xmlrpc 2015-11-19 09:50:28 UTC

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://rhn.redhat.com/errata/RHBA-2015-2284.html