Bug 2524990 - Ignition remote config fetch fails on Fedora 45 IoT - network unreachable in initramfs
Summary: Ignition remote config fetch fails on Fedora 45 IoT - network unreachable in ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ignition
Version: 45
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jonathan Lebon
QA Contact: Fedora Extras Quality Assurance
URL: https://github.com/fedora-iot/ignitio...
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F45FinalFreezeException, FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2026-08-27 14:59 UTC by Klara Necasova
Modified: 2026-09-21 19:42 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-09-21 19:42:37 UTC
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github fedora-iot ignition-edge pull 12 0 None Merged Fix network setup for dracut 110+ 2026-09-09 07:22:02 UTC

Description Klara Necasova 2026-08-27 14:59:04 UTC
Description of problem:
On Fedora 45 IoT (dracut 111), Ignition fails to fetch remote configuration with "network is unreachable" error because NetworkManager never starts in initramfs.

Root cause:
dracut 110 removed the compatibility symlink from /usr/lib/dracut/hooks/ to /var/lib/dracut/hooks/ (commit 7dcc0ad1). The ignition-edge script coreos-enable-network.sh hardcoded the old path /usr/lib/dracut/hooks/cmdline/99-nm-config.sh, which no longer exists.


Reproducible: Always

Steps to Reproduce:
1. Boot Fedora 45 IoT image with Ignition remote config.
2. Observe Ignition attempting to fetch remote configuration.
3. Network fetch fails with "network is unreachable".
Actual Results:
NetworkManager hook is not sourced, network never comes up in initramfs, Ignition cannot fetch remote config.

Expected Results:
NetworkManager should start in initramfs and Ignition should successfully fetch remote configuration.

Comment 1 Fedora Blocker Bugs Application 2026-09-08 14:42:01 UTC
Proposed as a Freeze Exception for 45-beta by Fedora user knecasov using the blocker tracking app because:

 This Bug resolves a regression where Fedora 45 IoT cannot fetch an Ignition remote configuration due to a hardcoded path in ignition-edge broken by dracut 110's symlink removal.

Comment 2 Kamil Páral (Red Hat) 2026-09-09 07:22:02 UTC
Upstream PR merged:
https://github.com/fedora-iot/ignition-edge/pull/12

Comment 3 Adam Williamson (Fedora) 2026-09-10 18:11:35 UTC
We signed off on Beta today (with 20260909.0 snapshot as the IoT release), so this can't be a Beta FE now.

Comment 4 Kamil Páral (Red Hat) 2026-09-11 10:32:52 UTC
@pwhalen said in https://forge.fedoraproject.org/quality/blocker-review/issues/2173 that this is important for IoT and might propose a criterion change for it. Marking this as proposed for Final FE at least, so that we don't lose track of it (and might be even a blocker, if that criterion change gets proposed).

Comment 5 Lukas Ruzicka (Red Hat) 2026-09-14 17:37:03 UTC
AGREED AcceptedFinalFreezeException

Discussed at the 2026-09-14 (blocker / freeze exception) review meeting:

this is accepted as it affects deployment and thus cannot be fixed with a post-release update

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-09-14/f45-blocker-review.2026-09-14-16.01.log.txt

Comment 6 Paul Whalen 2026-09-21 19:42:37 UTC
Verified fixed in ignition-2.27.0-2.fc45


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