Bug 2328530 - coreos-installer-dracut builds from outdated commit hash
Summary: coreos-installer-dracut builds from outdated commit hash
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-coreos-installer
Version: 41
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Rust SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F42FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2024-11-24 06:50 UTC by Sebastian
Modified: 2025-04-11 04:04 UTC (History)
8 users (show)

Fixed In Version: rust-coreos-installer-0.23.0-6.fc42
Clone Of:
Environment:
Last Closed: 2025-04-11 04:04:21 UTC
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1361 0 None None None 2024-11-24 06:51:20 UTC

Description Sebastian 2024-11-24 06:50:50 UTC
The rust-coreos-installer package automatically updates when new versions of coreos-installer are released. However, this does not update the commit hash of coreos-installer-dracut, leading to the currently specified commit being significantly out-of-date.

This means #2232406 never got fixed for Fedora which breaks installs of the Fedora IoT Simplified Provisioner image when trying to install to /dev/nvme or /dev/mmcblk devices.

Reproducible: Always

Steps to Reproduce:
1. Use coreos-installer to install to a mmcblk or nvme block device.
Actual Results:  
coreos-installer-growfs fails due to the bug identified in #2232406.

Expected Results:  
coreos-installer-growfs should succeed.

This means #2232406 is still an issue in Fedora distros. The commit hash seems to have gotten updated in the RHEL repositories as part of the original bug report.

Comment 1 Fedora Update System 2025-03-27 14:37:50 UTC
FEDORA-2025-d10cc065e6 (rust-coreos-installer-0.23.0-6.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-d10cc065e6

Comment 2 Fedora Update System 2025-03-28 15:26:24 UTC
FEDORA-2025-d10cc065e6 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d10cc065e6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d10cc065e6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Blocker Bugs Application 2025-04-04 18:59:36 UTC
Proposed as a Freeze Exception for 42-final by Fedora user miabbott using the blocker tracking app because:

 The IoT simplified-provisioner relies on the `rust-coreos-installer` package to write out the disk image during the install phase of provisioning. If we do not include the fixed version of this package as part of the Fedora 42 GA compose, we will end up shipping a version of the IoT simplified-provisioner that does not work correctly when installing to MMC devices, which are commonly used in the IoT/Edge device space.  The fixed package already exists and has an update in Bodhi, but it didn't make it to stable before the freeze.

Comment 4 Adam Williamson 2025-04-07 07:06:12 UTC
+5 in https://pagure.io/fedora-qa/blocker-review/issue/1838 , marking accepted FE.

Comment 5 Kamil Páral 2025-04-08 07:44:09 UTC
The Bodhi update needs one more karma (or lower the stable threshold), if we should include it in stable updates. Please test and provide karma, thanks!

Comment 6 Adam Williamson 2025-04-09 23:15:13 UTC
Lowering the stable threshold would not be possible. This is a critpath update which means it needs +2 by policy. If anyone had tried to lower the autopush threshold to 1, Bodhi would've rejected it.

Comment 7 Fedora Update System 2025-04-11 04:04:21 UTC
FEDORA-2025-d10cc065e6 (rust-coreos-installer-0.23.0-6.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.