Bug 2345544 - systemd segfault in Anaconda after adding unit condition "ConditionOSRelease=|ID_LIKE$=*rhel*"
Summary: systemd segfault in Anaconda after adding unit condition "ConditionOSRelease=...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-13 13:26 UTC by Radek Vykydal
Modified: 2025-02-13 23:37 UTC (History)
9 users (show)

Fixed In Version: systemd-257.3-3.fc43 systemd-257.3-3.fc42
Clone Of:
Environment:
Last Closed: 2025-02-13 23:25:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github systemd systemd pull 36375 0 None open core/condition: fix segfault when key not found in os-release 2025-02-13 14:55:51 UTC

Description Radek Vykydal 2025-02-13 13:26:37 UTC
In our kickstrart tests (Anaconda installations run in a VM) we are hitting systemd segfault when adding

ConditionOSRelease=|ID_LIKE$=*rhel*

to our service.

Console output tail:
[  OK  ] Reached target ssh-access.target - SSH Access Available.
[  OK  ] Listening on systemd-hostnamed.socket - Hostname Service Socket.
[  OK  ] Reached target sockets.target - Socket Units.
         Starting dbus-broker.service - D-Bus System Message Bus...
[  OK  ] Started dbus-broker.service - D-Bus System Message Bus.
[  OK  ] Reached target basic.target - Basic System.
         Starting anaconda-import-initramfs… stage of Anaconda via kickstart...
[   17.921886] systemd[1]: segfault at 0 ip 00007feb7ad2e79c sp 00007ffe71e90128 error 4 in libc.so.6[15a79c,7feb7abd4000+170000] likely on CPU 0 (core 0, socket 0)
[   17.922826] Code: ff ff 48 89 f8 0f bc c9 f3 a4 c3 0f 1f 00 f3 0f 1e fa 89 f8 62 a1 fd 00 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 24 01 00 00 <62> f1 7d 20 74 07 c5 fb 93 c0 85 c0 74 16 0f bc c0 c3 66 90 0f bc
         Starting anaconda-nm-config.servic…nda NetworkManager configuration...


It is in this commit: https://github.com/rhinstaller/anaconda/pull/6142/commits/5714b3b01ba5444bc2d1b8b9b55a3e6b85e38f4c (PR https://github.com/rhinstaller/anaconda/pull/6142)

Versions:
boot.iso: Fedora-Rawhide-20250212.n.0
systemd 257.2-17.fc42

Reproducible: Always

Steps to Reproduce:
1. Run installation with the latest rawhide boot.iso using updates image with the patch: https://rvykydal.fedorapeople.org/updates.centos-autocons.img
It can be applied by adding kernel boot option
inst.updates=https://rvykydal.fedorapeople.org/updates.centos-autocons.img
2.
3.
Alternatively we can build boot.iso in the PR (This does not happen on RHEL 10 nightly.) by adding comment
/build-image
Actual Results:  
Installation crashes at initramfs stage.

Expected Results:  
Installation succeeds.
(With the service doing its job, for example being activated on Rocky linux UI installation).

This does not happen with RHEL 10 nightly.

Comment 2 Zbigniew Jędrzejewski-Szmek 2025-02-13 14:55:52 UTC
https://github.com/systemd/systemd/pull/36375

Comment 3 Fedora Update System 2025-02-13 21:36:50 UTC
FEDORA-2025-85daeb8b4b (systemd-257.3-3.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-85daeb8b4b

Comment 4 Fedora Update System 2025-02-13 22:04:11 UTC
FEDORA-2025-33e5bf1eb1 (systemd-257.3-3.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-33e5bf1eb1

Comment 5 Fedora Update System 2025-02-13 23:25:41 UTC
FEDORA-2025-85daeb8b4b (systemd-257.3-3.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2025-02-13 23:37:40 UTC
FEDORA-2025-33e5bf1eb1 (systemd-257.3-3.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.