Bug 2292526 - (IoT): rpm-ostree upgrade from Fedora IoT 39 to 40 fails when initramfs generation is enabled
Summary: (IoT): rpm-ostree upgrade from Fedora IoT 39 to 40 fails when initramfs gener...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm-ostree
Version: 39
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: IoT
TreeView+ depends on / blocked
 
Reported: 2024-06-15 20:33 UTC by geoffrey.bonneville
Modified: 2024-07-01 09:38 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-01 09:38:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1217 0 None None None 2024-06-15 20:33:58 UTC

Description geoffrey.bonneville 2024-06-15 20:33:09 UTC
Description of problem:
Upgrading from Fedora IoT 39 to IoT 40 fails when initramfs generation is enabled.

Version-Release number of selected component (if applicable):
2023.7

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora IoT 39.x (I installed 20231103.1 in a VM)
2. Enable initramfs regeneration with "rpm-ostree initramfs --enable"
3. Reboot
4. Try to upgrade with "rpm-ostree upgrade"

Actual results:
An error message is displayed:
"error: bwrap(rpm-ostree-dracut-wrapper): Child process killed by signal 1"


Expected results:
The upgraded deployment should be successful.

Comment 1 Timothée Ravier 2024-06-17 10:42:36 UTC
We would need the system logs to be able to investigate.

Comment 2 geoffrey.bonneville 2024-06-29 19:20:27 UTC
I tried to reproduce the issue in a new VM to submit logs, but the upgrade has been successful this time.
I have been able to upgrade another Fedora 39 IoT instance which couldn't be upgraded for more than 2 months.
I guess this has been resolved by a package update in the last few days.

We can close this, thank you.


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