On Sun, Apr 21, 2013 at 11:36:57AM +0100, Nux! wrote: > On 21.04.2013 10:38, Niels de Vos wrote: > >On Sun, Apr 21, 2013 at 10:26:29AM +0100, Nux! wrote: > >>On 21.04.2013 10:21, Niels de Vos wrote: > >>>On Sun, Apr 21, 2013 at 08:26:02AM +0100, Nux! wrote: > >>>>On 17.04.2013 17:10, jenkins@xxxxxxxxxxxxxxxxx wrote: > >>>>>RPM: http://bits.gluster.org/pub/gluster/glusterfs/3.4.0alpha3/ > >>>>> > >>>>>SRC: > >>>>>http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.0alpha3.tar.gz > >>>>> > >>>>>This release is made off jenkins-release-31 > >>>> > >>>>And rpm upgrade killed glusterd (3.4 git) and output this: > >>>> > >>>>[root@2216 3.4.0alpha3]# rpm -Uvh > >>>>glusterfs-3.4.0alpha3-1.el6.x86_64.rpm > >>>>glusterfs-fuse-3.4.0alpha3-1.el6.x86_64.rpm > >>>>glusterfs-server-3.4.0alpha3-1.el6.x86_64.rpm > >>>... > >>>>error: %preun(glusterfs-server-3.4git-1.el6.nux.x86_64) scriptlet > >>>>failed, exit status 1 > >>>> > >>>>Let me know if/what logs are needed to make sense of things. > >>> > >>>Looks like you updated glusterfs-3.4git-1.el6.nux to > >>>glusterfs-3.4.0alpha3-1.el6. The pre-uninstall script from > >>>glusterfs-server-3.4git-1.el6.nux.x86_64 exited with an error. It > >>>seems > >>>that you have build that version yourself, so you will need to > >>>verify > >>>the scriptlet of that RPM. You can print the scriptlet if you > >>>still have > >>>the rpm itself with a command like this: > >>> > >>> $ rpm -q --qf '%{PREUN}\n' -p > >>>glusterfs-server-3.4git-1.el6.nux.x86_64.rpm > >>> > >>>From a package that I build from git, I would suspect that the > >>>following > >>>command fails: > >>> > >>> /sbin/service glusterd condrestart > >>> > >>>The extras/init.d/glusterd-Redhat(.in) does not accept the > >>>condrestart > >>>action. The Fedora package seems to carry its own init-script > >>>which does > >>>include support for condrestart. The .spec from Fedora has > >>>been merged > >>>into the glusterfs project, but obviously some dependencies (like > >>>changes to the init-script) have been missed. > >>> > >>>I've filed this as > >>>https://bugzilla.redhat.com/show_bug.cgi?id=954149 > >>> > >>>Cheers, > >>>Niels > >> > >>Thanks a lot, Niels. You hit the nail on the head. > >>Hopefully this will get fixed soon. > > > >Patches have been filed for both the release-3.4 and master branch. It > >is much appreciated if you can test the result and post a comment > >in the > >review request (and/or Bug): > >- http://review.gluster.org/4865 > > > >Note that you will need to build two packages in order to test the > >functionality. The currently available packages contain an > >uninstall-scriptlet with the error, and this scriptlet will get > >executed > >on an update. After a package with the suggested change has been > >installed, updating to the next should go flawlessly. > > Niels, > > Sure, I can test. Can't just use a single package for the "initial" > installation and then rpm -U --force with the same one? Yeah, you could do that (but --force isn't really nice). Or, build a 2nd one and add something to the Release line in the .spec like Release: 1%{?dist}.0.bz954149 Thanks!
