Just a short note to remind people that its almost time for another Pacemaker bug-fix release. So now is a good time to report any bugs/problems - otherwise you'll have to wait another whole month to get them fixed :-)

I don't expect any problems in testing... there have not been many changes since 0.6.3

  * Changes since Pacemaker-0.6.3
+ High: crmd: Bug LF:1881 LF:1882 - Overhaul the logic for operation cancelation and deletion + High: crmd: Bug LF:1894 - Make sure cancelled recurring operations are cleaned out from the CIB + High: PE: Bug N:387749 - Colocation with clones causes unnecessary clone instance shuffling + High: PE: Ensure 'master' monitor actions are cancelled _before_ we demote the resource + High: PE: Fix assert failure leading to core dump - make sure variables are properly initialized + High: PE: Make sure 'slave' monitoring happens after the resource has been demoted + High: PE: Prevent failure stickiness underflows (where too many failures become a _positive_ preference) + Medium: Admin: crm_mon - Only complain if the output file could not be opened + Medium: Common: filter_action_parameters - enable legacy handling only for older versions + Medium: PE: Bug N:385265 - The failure stickiness of group children is ignored until it reaches -INFINITY + Medium: TE: Bug LF:1875 - Correctly find actions to cancel when their node leaves the cluster

Andrew


_______________________________________________
Pacemaker mailing list
Pacemaker@clusterlabs.org
http://list.clusterlabs.org/mailman/listinfo/pacemaker

Reply via email to