Bug 2126506

Summary:	[RHEL-8] Creation of custom data partion fails on edge installer
Product:	Red Hat Enterprise Linux 8	Reporter:	Jan Stodola <jstodola>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	high	Docs Contact:	Sagar Dubewar <sdubewar>
Priority:	unspecified
Version:	8.6	CC:	dornelas, lmanasko, sbarcomb, sdubewar, vslavik
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	.RHEL for Edge installer image fails to create mount points when installing an rpm-ostree payload When deploying `rpm-ostree` payloads, used for example in a RHEL for Edge installer image, the installer does not properly create some mount points for custom partitions. As a consequence, the installation is aborted with the following error: ---- The command 'mount --bind /mnt/sysimage/data /mnt/sysroot/data' exited with the code 32. ---- To work around this issue: * Use an automatic partitioning scheme and do not add any mount points manually. * Manually assign mount points only inside `/var` directory. For example, `/var/_my-mount-point_`), and the following standard directories: `/`, `/boot`, `/var`. As a result, the installation process finishes successfully.	Story Points:	---
Clone Of:	2125542	Environment:
Last Closed:	2023-09-18 15:59:57 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 Jan Stodola 2022-09-13 16:07:34 UTC

The same problem can be reproduced with RHEL-8.6 edge installer.


+++ This bug was initially created as a clone of Bug #2125542 +++

Description of problem: 
Using Image Builder I've created an edge installer. When I try to create a custom data partion (/data) I get the error during the installation progress "The following error occurred while installing the payload. This a fatal error and installation will be aborted. The command 'mount --bind /mnt/sysimage/data /mnt/sysroot/data' exited with the code 32.

I've seen that if I create the data directory in a separate console under /mnt/sysimage and then making again mount --rbind /mnt/sysimage /mnt/sysroot the directory is properly created.


Version-Release number of selected component (if applicable):
- RHEL 9
- anaconda 34.25.0.29
- composer-cli v35.5
- API server status:
    Database version:   0
    Database supported: true
    Schema version:     0
    API version:        1
    Backend:            osbuild-composer
    Build:              NEVRA:osbuild-composer-46.3-1.el9_0.x86_64



How reproducible: everytime


Steps to Reproduce:
1. Select Installation Destination
2. Select Storage Configuration as Custom
3. Add a new mount point with Mount Point "/data" and Desiderd Capacity: 2 GiB
4. Accept changes
5. Begin installation

Actual results:
Installation reports  "The following error occurred while installing the payload. This a fatal error and installation will be aborted. The command 'mount --bind /mnt/sysimage/data /mnt/sysroot/data' exited with the code 32."

Expected results:
Installation complete with success.

Comment 2 Jan Stodola 2022-09-13 16:57:48 UTC

The bug can also be reproduced with a regular RHEL-8.7 installer, when pointing it to a remote ostree via a kickstart file, for example:

clearpart --all
reqpart --add-boot
part --size 1 --grow /
part --size 2048 /data
ostreesetup --nogpg --osname=rhel-edge --remote=rhel-edge --url=http://192.168.122.2/ostree/repo --ref=rhel/8/x86_64/edge

Comment 10 RHEL Program Management 2023-09-18 15:58:15 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 11 RHEL Program Management 2023-09-18 15:59:57 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.