diff options
| author | Jakub Hrozek <jhrozek@redhat.com> | 2014-08-10 19:25:28 +0200 |
|---|---|---|
| committer | Jakub Hrozek <jhrozek@redhat.com> | 2014-08-11 15:56:43 +0200 |
| commit | 34e1d900fcb37a8e9f8b9c28467f37cd30ed854a (patch) | |
| tree | 62d6e289f78afb121f023d1991c0dc715965970c /contrib | |
| parent | a963daabd3b2d817b27ea5d0e01df8ddc3f00f6c (diff) | |
| download | sssd-34e1d900fcb37a8e9f8b9c28467f37cd30ed854a.tar.gz sssd-34e1d900fcb37a8e9f8b9c28467f37cd30ed854a.tar.xz sssd-34e1d900fcb37a8e9f8b9c28467f37cd30ed854a.zip | |
RPM: Restart service in %posttrans, not %post
When upgrading from a 1.9 version with monolithic packaging to 1.10 or
later with per-provider subpackage, sssd-common can be upgraded (and
restarted) before the new sssd-$provider is restarted. This can lead to
a startup failure, because the sssd_be process from already upgraded
sssd-common would attempt to load a sssd_$provider.so from the
legacy sssd package.
Restarting the service in %posttrans makes sure all the packages are in
place when we restart the service.
Resolves:
https://fedorahosted.org/sssd/ticket/2399
(cherry picked from commit 192027debeaa991690160c3cb68480fe54ad8fdf)
Diffstat (limited to 'contrib')
| -rw-r--r-- | contrib/sssd.spec.in | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/contrib/sssd.spec.in b/contrib/sssd.spec.in index 4a3c402c3..ce6800f20 100644 --- a/contrib/sssd.spec.in +++ b/contrib/sssd.spec.in @@ -779,9 +779,8 @@ fi %post common /sbin/chkconfig --add %{servicename} -if [ $1 -ge 1 ] ; then - /sbin/service %{servicename} condrestart 2>&1 > /dev/null -fi +%posttrans +/sbin/service %{servicename} condrestart 2>&1 > /dev/null %preun common if [ $1 = 0 ]; then |