It has always been the case that symmetrical=true was ignored (with a warning) for serialized constraints; the only recent change was making false the default so the warning wouldn't be displayed.
If you want the services to start and stop in a particular order, you don't want a serialized constraint, just a regular order constraint. A serialized constraint merely says that the actions can't be done at the same time, either one may be done first. If you have a serialized constraint saying the resources can't start at the same time, and want that to apply to stops as well, then you can create a second serialized constraint explicitly specifying stop as the action to be ordered. On Mon, 2020-03-16 at 19:41 +0530, Dileep V Nair wrote: > Hi, > > I have pacemaker clusters which were working fine with Serialize and > symmetrical=true together. After an upgrade, I see that Serialize > does not work with symmetrical=true. How do I make sure the resources > in Serialize stop in reverse order of start ? All the clusters are > already in production. Please help. > > Thanks & Regards > > Dileep Nair > Squad Lead - SAP Base > Togaf Certified Enterprise Architect > IBM Services for Managed Applications > +91 98450 22258 Mobile > [email protected] > > IBM Services > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Ken Gaillot <[email protected]> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
