Fabian Arrotin wrote: > Ralph Angenendt wrote: >> Hi, >> >> there are new drbd83-8.3.9 packages available in the testing >> repository (4 and 5, i386 and x86_64), if you want to try them out. >> >> There shouldn't be a problem to drop those in as a replacement to >> older drbd83 packages. >> >> Regards, >> >> Ralph > > I'll test an upgrade tomorrow at $work on at least one secondary node > and i'll post the results > I've done a quick test on a secondary node and reported the result in the #centos-social channel directly to Ralph, but I think that it would be a good idea to "archive" my answer on the list too. The machine on which i tested an update wasn't up2date and so was missing that module-init-tools-3.3-0.pre3.1.60.el5_5.1 rpm (released three weeks ago, see https://bugzilla.redhat.com/show_bug.cgi?id=593504) As a consequence, that drbd secondary node didn't come back automagically (known issue, see above) I discussed with Ralph to see if that was a good idea (or a bad one) to put an extra Requires: line in the kmod spec to fetch that fixed module-init-tools rpm prior to the kmod update. One can argue that sysadmins have to keep their machine up2date (which is right) Another one can argue that if those sysadmins didn't update their machine prior to the drbd83 update, some 'bug reports' will appear on bugs.centos.org to say that the latest drbd update broke their cluster . Thoughts about this ? -- -- Fabian Arrotin