Bug 1710718

Summary:	libsystemd-shared-239.so not included in initramfs
Product:	[Fedora] Fedora	Reporter:	Sami Farin <hvtaifwkbgefbaei>
Component:	dracut	Assignee:	dracut-maint-list
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	29	CC:	dracut-maint-list, jonathan, zbyszek
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:	2019-11-27 22:34:27 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 Sami Farin 2019-05-16 07:35:51 UTC

Description of problem:
[    1.328952] Run /init as init process
/init: error while loading shared libraries: libsystemd-shared-239.so: cannot open shared object file: No such file or directory
[    1.330947] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[    1.332430] CPU: 1 PID: 1 Comm: init Not tainted 5.0.14-200.fc29.x86_64 #1
[    1.333416] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20180724_192412-buildhw-07.phx2.fedoraproject.org-1.fc29 04/01/2014


Version-Release number of selected component (if applicable):
dracut-049-26.git20181204.fc29.x86_64

How reproducible:
unknown

Steps to Reproduce:
1. upgrade kernel with dnf
2.
3.

Actual results:
dracut does not bother to include required libraries for systemd

Expected results:
booting system

Additional info:

Comment 1 Sami Farin 2019-05-20 14:55:33 UTC

This is just silly.
If I add libsystemd-shared-*.so via option install_items , next thing it complains on reboot is 
/init: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory
[    1.316483] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

Comment 2 Ben Cotton 2019-10-31 19:19:42 UTC

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-11-27 22:34:27 UTC

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.