On current rawhide (and f28) installs we see: DEBUG util.py:439: (539/775) lvm2-2.02.177-4.fc28.x86_64 DEBUG util.py:439: Non-fatal POSTIN scriptlet failure in rpm package lvm2 DEBUG util.py:439: 2018-03-06 23:20:36,795: Non-fatal POSTIN scriptlet failure in rpm package lvm2 DEBUG util.py:439: Non-fatal POSTIN scriptlet failure in rpm package lvm2 It's non fatal, but it should be fixed. It seems the lvm2.spec tries to start some things: systemctl start lvm2-lvmetad.socket systemctl start lvm2-lvmpolld.socket According to guidelines: https://fedoraproject.org/wiki/Packaging:Systemd#Why_don.27t_we.... "Why don't we.... Start the service after installation? Installations can be in changeroots, in an installer context, or in other situations where you don't want the services autostarted."
No service is started here, this is socket for socket activation. Nothing will be started in chroot. The socket and lvmetad is important for auto-activation of lvm2 volumes. Peter, shall we close this a NOTABUG/WONTFIX?
(In reply to Marian Csontos from comment #1) > No service is started here, this is socket for socket activation. Nothing > will be started in chroot. > > The socket and lvmetad is important for auto-activation of lvm2 volumes. > > Peter, shall we close this a NOTABUG/WONTFIX? We need to make those lvm2-{lvmetad,lvmpolld}.socket units to be active after installation. And, these should be only debug messages, so if we don't have another way of making these units started after installation, we need to close this bug then.
Please at least add ' /dev/null 2>&1 || : ' to these socket enable/start calls. In a chroot it won't do anything, but it does exit 1 and cause a scriptlet failure in anaconda, which can sometimes be fatal. At least ignore the return code so we don't keep seeing this.
*** Bug 1399776 has been marked as a duplicate of this bug. ***
I have added the `|| :` part of the fix in lvm2-2.02.178-0.1.rc1. Thinking about it, I think we can safely use the redirection as well - if systemctl does not work, system is either seriously broken or we are running in special environment e.g. container or chroot. I have committed second change to fedpkg and will bundle with the next release.