Bug 2334895 - dhcpcd: Allow the __NR_rt_sigprocmask for glibc userspace getrandom
Summary: dhcpcd: Allow the __NR_rt_sigprocmask for glibc userspace getrandom
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dhcpcd
Version: 41
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Petr Menšík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-30 03:27 UTC by Xiaofeng Wang
Modified: 2025-01-23 01:48 UTC (History)
17 users (show)

Fixed In Version: dhcpcd-10.1.0-1.fc41 dhcpcd-10.1.0-1.fc40
Clone Of:
Environment:
Last Closed: 2025-01-12 01:39:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github NetworkConfiguration dhcpcd issues 421 0 None closed dhcpcd crashes with SIGSYS with latest Ferdora 41 glibc 2024-12-30 08:54:12 UTC

Description Xiaofeng Wang 2024-12-30 03:27:31 UTC
glibc upgrade from glibc-2.40-11.fc41.x86_64 to glibc-2.40-12.fc41.x86_64.

glibc-2.40-11.fc41.x86_64 log: https://artifacts.osci.redhat.com/testing-farm/adc89258-4a0d-48f2-8d78-96a8184c2563/
glibc-2.40-12.fc41.x86_64 log: https://artifacts.osci.redhat.com/testing-farm/89fea7a1-65d8-42c3-8515-1ae0421e1a07/

When bootup a Fedora41 bootc image on Azure, the cloud-init has failures at dhcpcd command and retry for 20 minutes.

Same issue can be found on Fedora 40, rawhide, RHEL 10.0 and Centos Stream 10.

2024-11-27 09:12:58,103 - dhcp.py[DEBUG]: Performing a dhcp discovery on eth0
2024-11-27 09:12:58,103 - subp.py[DEBUG]: Running command ['ip', 'link', 'set', 'dev', 'eth0', 'up'] with allowed return codes [0] (shell=False, capture=True)
2024-11-27 09:12:58,106 - util.py[DEBUG]: Reading from /sys/class/net/eth0/type (quiet=False)
2024-11-27 09:12:58,106 - util.py[DEBUG]: Read 2 bytes from /sys/class/net/eth0/type
2024-11-27 09:12:58,107 - subp.py[DEBUG]: Running command ['/usr/sbin/dhcpcd', '--ipv4only', '--waitip', '--persistent', '--noarp', '--script=/bin/true', 'eth0'] with allowed return codes [0] (shell=False, capture=True)
2024-11-27 09:12:59,117 - subp.py[DEBUG]: ['/usr/sbin/dhcpcd', '--ipv4only', '--waitip', '--persistent', '--noarp', '--script=/bin/true', 'eth0'] took 1.0s to run
2024-11-27 09:12:59,118 - dhcp.py[DEBUG]: dhcpcd exited with code: 1 stderr: 'dhcpcd-10.0.8 starting\n        DUID 00:01:00:01:2e:d9:9f:1a:7c:1e:52:68:50:eb\n        eth0: IAID 52:68:50:eb\n        dhcpcd_fork_cb: dhcpcd manager hungup' stdout: ''
2024-11-27 09:12:59,118 - azure.py[ERROR]: Failed to obtain DHCP lease (iface=None)
2024-11-27 09:12:59,118 - dmi.py[DEBUG]: querying dmi data /sys/class/dmi/id/product_uuid
2024-11-27 09:12:59,118 - identity.py[DEBUG]: Read product uuid: 8969ad4c-54fd-4cfa-a7c3-85a93f5050c7
2024-11-27 09:12:59,118 - handlers.py[DEBUG]: start: azure-ds/_report_failure: _report_failure
2024-11-27 09:12:59,118 - azure.py[ERROR]: Azure datasource failure occurred: result=error|reason=failure to obtain DHCP lease|agent=Cloud-Init/24.2|duration=1.043481516|interface=None|vm_id=8969ad4c-54fd-4cfa-a7c3-85a93f5050c7|timestamp=2024-11-27T09:12:59.118388|documentation_url=https://aka.ms/linuxprovisioningerror 


Reproducible: Always

Steps to Reproduce:
1. build fedora-bootc azure image with bib
2. upload azure image
3. create vm and boot vm
Actual Results:  
Cannot boot Azure vm

Expected Results:  
Boot Azure vm without error

Comment 1 Florian Weimer 2024-12-30 08:54:12 UTC
The difference between the -11 and -12 builds is the implementation of userspace acceleration for getrandom. In dhcpcd, this has already been identified as an issue:

dhcpcd crashes with SIGSYS with latest Ferdora 41 glibc
<https://github.com/NetworkConfiguration/dhcpcd/issues/421>

linux: Allow the __NR_rt_sigprocmask syscall
<https://github.com/NetworkConfiguration/dhcpcd/commit/e9e40400003db2e4f12dba85acabbaf2212a520f>

Comment 2 Frank Crawford 2025-01-02 10:57:17 UTC
This also seems to affect Fedora 40.

Comment 3 Fedora Update System 2025-01-07 17:04:55 UTC
FEDORA-2025-0b4e2489b0 (dhcpcd-10.1.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-0b4e2489b0

Comment 4 Fedora Update System 2025-01-07 17:07:53 UTC
FEDORA-2025-4553d23d99 (dhcpcd-10.1.0-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4553d23d99

Comment 5 Fedora Update System 2025-01-08 02:12:59 UTC
FEDORA-2025-0b4e2489b0 has been pushed to the Fedora 41 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-0b4e2489b0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0b4e2489b0

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

Comment 6 Fedora Update System 2025-01-08 03:14:29 UTC
FEDORA-2025-4553d23d99 has been pushed to the Fedora 40 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-4553d23d99`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4553d23d99

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

Comment 7 Fedora Update System 2025-01-12 01:39:13 UTC
FEDORA-2025-0b4e2489b0 (dhcpcd-10.1.0-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-01-23 01:48:40 UTC
FEDORA-2025-4553d23d99 (dhcpcd-10.1.0-1.fc40) has been pushed to the Fedora 40 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.