It was discovered that this release of glib project changed sligthly some parameters of how distribution of values within hash tables structures work, undermining pacemaker's hard (alas unfeasible) attempt to turn this data type into fully predictable entity.
Current impact is unknown beside some internal regression test failing due to this, so that, e.g., in the environment variables passed in the notification messages, the order of the active nodes (being a space separarated list) may be appear shuffled in comparison with the long standing (and perhaps making a false impression of determinism) behaviour witnessed with older versions of glib in the game. Variations like these are expected, and you may take it as an opportunity to fix incorrect order-wise (like in the stated case) assumptions. More serious troubles stemming from this expectation-reality mismatch regarding said data type cannot be denied at this point, subject of further investigation. When in doubt, staying with glib up to and including v2.58.2 (said tests are passing with it, though any later v2.58.* may keep working "as always") is likely a good idea for the time being. -- Thanks Jan (Poki)
pgphSRnAjMxHh.pgp
Description: PGP signature
_______________________________________________ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
