This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2126506 - [RHEL-8] Creation of custom data partion fails on edge installer
Summary: [RHEL-8] Creation of custom data partion fails on edge installer
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.6
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
Sagar Dubewar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-13 16:07 UTC by Jan Stodola
Modified: 2023-09-18 15:59 UTC (History)
5 users (show)

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.
Clone Of: 2125542
Environment:
Last Closed: 2023-09-18 15:59:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4744 0 None Migrated None 2023-09-18 15:59:53 UTC
Red Hat Issue Tracker RHELPLAN-133864 0 None None None 2022-09-13 16:11:50 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.