Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1942298

Summary:	os crashes on timedatectl command and cannot reboot
Product:	[Fedora] Fedora	Reporter:	john <murphy.john69>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	33	CC:	fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, ssahani, s, systemd-maint, vslavik, yuwatana, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-24 11:56:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description john 2021-03-24 05:15:10 UTC

Description of problem:
OS crashes on timedate command 

Version-Release number of selected component (if applicable):
fedora 33 xfce or workstation live isos, or versions installed from them,
on all machines ive tried it on

How reproducible:


Steps to Reproduce:
1.timedatectl set-timezone Europe/Dublin
2.
Actual results:
CPU usges goes to 100% systemd running and grinds to
a halt,
3.installation is then broken and cannot reboot even in rescue mode


Expected results:


Additional info:

Comment 1 Vladimír Slávik 2021-03-24 11:39:54 UTC

Hello john, thank you for the report. Reassigning to systemd as that's the broken bit.

Comment 2 Zbigniew Jędrzejewski-Szmek 2021-03-24 11:56:07 UTC

Please, when submitting a bug report, always include rpm versions and logs. This greatly increases
the chances that somebody will be able to do something useful with the report, especially a few
weeks or months down the road.

Anyway, looks like a duplicate of #1941335. Please check that systemd-246.13-1.fc33 fixes the issue.

*** This bug has been marked as a duplicate of bug 1941335 ***