Description of problem: "yum update" to sssd-1.4.1-3.fc15.x86_64 gives warning messages on terminal.
Version-Release number of selected component (if applicable):
How reproducible: haven't tried
Steps to Reproduce:
1. yum update
Non-fatal POSTIN scriptlet failure in rpm package sssd-1.4.1-3.fc15.x86_64
Job failed. See system logs and 'systemctl status' for details.
warning: %post(sssd-1.4.1-3.fc15.x86_64) scriptlet failed, exit status 1
Expected results: No complaints.
# systemctl status
Too few arguments.
# systemctl status sssd
Failed to issue method call: Unit name sssd is not valid.
-----snippet from /var/log/messages [nothing unusual that I can see]
Nov 19 08:21:26 f15r64 yum: Updated: sssd-client-1.4.1-3.fc15.x86_64
Nov 19 08:21:27 f15r64 yum: Updated: mesa-libGL-7.10-0.11.fc15.x86_64
Nov 19 08:21:28 f15r64 yum: Updated: mesa-libGLU-7.10-0.11.fc15.x86_64
Nov 19 08:21:29 f15r64 yum: Updated: sssd-1.4.1-3.fc15.x86_64
Nov 19 08:21:29 f15r64 kernel: [ 224.307151] dbus: [system] Reloaded configuration
Nov 19 08:21:29 f15r64 kernel: [ 224.311935] dbus: [system] Reloaded configuration
Nov 19 08:21:30 f15r64 kernel: [ 224.334553] dbus: [system] Reloaded configuration
Nov 19 08:21:31 f15r64 yum: Updated: setroubleshoot-3.0.9-1.fc15.x86_64
'service SERVICENAME condrestart' is a common command put in the %post section of spec files to ensure that services are restarted after update if they were previously running.
If the service was not running, it should take no action. However, 'systemctl condrestart SERVICENAME.service' throws the error:
"Job failed. See system logs and 'systemctl status' for details"
There is no indication of which logs to check (and I could not find any that provided any information) and the error message should be more clear that the status command should be 'systemctl status SERVICENAME.service'.
As per http://fedoraproject.org/wiki/Packaging:SysVInitScript#condrestart_and_try-restart condrestart shouldn't fail. There is a patch in http://article.gmane.org/gmane.comp.sysutils.systemd.devel/679.
Bumping severity to high, because it breaks other systems and may lead to unnecessary workarounds in spec files.
(In reply to comment #2)
> There is a patch in http://article.gmane.org/gmane.comp.sysutils.systemd.devel/679.
Sorry, there is not patch there.
*** This bug has been marked as a duplicate of bug 635780 ***
*** Bug 673597 has been marked as a duplicate of this bug. ***