Bug 1900735

Summary:	update to systemd-247~rc2-1.fc34 hangs
Product:	[Fedora] Fedora	Reporter:	Paul Whalen <pwhalen>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	awilliam, fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, ssahani, s, systemd-maint, yuwatana, zbyszek, z
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-02 17:40:04 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 Paul Whalen 2020-11-23 15:39:44 UTC

Description of problem:

Attempting to update systemd to systemd-247~rc2-1.fc34


  Running scriptlet: systemd-247~rc2-1.fc34.aarch64                        5/12 
  Upgrading        : systemd-247~rc2-1.fc34.aarch64                        5/12 
  Running scriptlet: systemd-247~rc2-1.fc34.aarch64                        5/12 
[  753.242897] systemd[1]: systemd v247~rc2-1.fc34 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[  753.267787] systemd[1]: Detected architecture arm64.
[  753.444118] zram_generator::generator[995]: Creating dev-zram0.swap for /dev/zram0 (4096MB)
[  753.781554] systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[  754.024274] systemd[1]: serial-getty: Current command vanished from the unit file, execution of the command list won't be resumed.
[  759.062251] zram_generator::generator[1050]: Creating dev-zram0.swap for /dev/zram0 (4096MB)
[  761.187891] ldconfig (1055) used greatest stack depth: 9568 bytes left
[  762.523372] zram_generator::generator[1243]: Creating dev-zram0.swap for /dev/zram0 (4096MB)


No further output.


From the logs:

Nov 23 09:51:04 seattle zram_generator::generator[995]: Creating dev-zram0.swap for /dev/zram0 (4096MB)
Nov 23 09:51:04 seattle systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Nov 23 09:51:04 seattle systemd[1]: serial-getty: Current command vanished from the unit file, execution of the command list won't be resumed.

Shortly after this ssh session was closed. 

Version-Release number of selected component (if applicable):
systemd-247~rc2-1.fc34

How reproducible:
Everytime

Steps to Reproduce:
1. Update existing F34 installation, limiting updates to systemd
2. Update hangs

Comment 1 Zbigniew Jędrzejewski-Szmek 2020-11-26 19:12:28 UTC

Hmm, what was the version you were upgrading from?

Comment 2 Paul Whalen 2020-11-26 19:39:23 UTC

systemd-246.6-3.fc34 -> systemd-247~rc2-1.fc34

Comment 3 Zbigniew Jędrzejewski-Szmek 2020-11-28 11:35:09 UTC

I'm not sure what is going on here. I don't have an arm64 system to test on, but I don't expect this
to be relevant. serial-getty changed indeed in this version (another baud rate was added).
That could explain why "Current command vanished from the unit file", but not why systemd would try
to reexec the command in the first place. Maybe it's somehow caused by the udev upgrade issue that
was only resolved before final 247 release.

Could you try if systemd-247-1.fc34 works better?

Comment 4 Adam Williamson (Red Hat non-Fedora) 2020-11-30 18:53:58 UTC

Was this possibly the same thing as https://bugzilla.redhat.com/show_bug.cgi?id=1900878 ? We had a lot of people experience Rawhide upgrade failing and crashing stuff around that time.

Comment 5 Zbigniew Jędrzejewski-Szmek 2020-12-01 12:45:14 UTC

Maybe? Please test with systemd-247.1-1.fc34.

Comment 6 Paul Whalen 2020-12-02 17:17:27 UTC

Upgrade from systemd-246.6-3.fc34 > systemd-247-1.fc34 worked as expected.

(In reply to Adam Williamson from comment #4)
> Was this possibly the same thing as
> https://bugzilla.redhat.com/show_bug.cgi?id=1900878 ? We had a lot of people
> experience Rawhide upgrade failing and crashing stuff around that time.

That looks the same.

Comment 7 Adam Williamson (Red Hat non-Fedora) 2020-12-02 17:40:04 UTC

OK. That bug seems to have more traction, so let's close this as a dupe of that even though this one is older.

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