Le Tue, 2 Aug 2016 10:02:36 -0500, Ken Gaillot <[email protected]> a écrit :
> On 08/02/2016 03:10 AM, Jehan-Guillaume de Rorthais wrote: > > Le Mon, 1 Aug 2016 12:00:24 -0500, > > Ken Gaillot <[email protected]> a écrit : > > > >> On 08/01/2016 11:18 AM, Jehan-Guillaume de Rorthais wrote: > >>> Le Mon, 1 Aug 2016 10:27:53 -0500, > >>> Ken Gaillot <[email protected]> a écrit : > >>> > >>>> On 07/29/2016 06:19 PM, Andrew Beekhof wrote: > >>>>> Urgh. I must be confused with sles11. > >>>>> In any case, the first version of pacemaker was identical to the last > >>>>> heartbeat crm. > >>>>> > >>>>> I don't recall the ocfs2 agent changing design while I was there, so 11 > >>>>> may be broken too > >>>> > >>>> I just realized *_active_* is only broken for master/slave clones. > >>>> Filesystem is not master/slave, so it wouldn't have any issue. > >>> > >>> Well, I'm glad we are the first RA using it :) > >>> > >>> I wonders how other m/s RA are doing without it. We are using it (actually > >>> "master + slave + start - stop" because of the bug) to check during a > >>> promotion after a failover if the resource being promoted is the best one > >>> among the known ones. > >> > >> Yes, the very simple workaround is simply to set active = master + > >> slave; that's all the pacemaker fix will do. You'll still need the "+ > >> start - stop" to get the situation after the action. > > > > Ok, thank you for the confirmation. > > > >> Coincidentally, we need to bump crm_feature_set to 3.0.11 anyway, so > >> you'll be able to test that to tell whether *_active_* is correct, if > >> desired. > > > > I will test it. > > fix is merged in master branch I did some superficial tests and it seems to work fine. I'll do some more test later when I'll work on the OCF_Functions perl module. Regards, -- Jehan-Guillaume de Rorthais Dalibo _______________________________________________ Developers mailing list [email protected] http://clusterlabs.org/mailman/listinfo/developers
