After upgrading to the latest Ubuntu-HA packages a script I had stopped working correctly. I tracked down the issue and fixed it but now I'm not sure whether it's a bug or I don't know how to properly write ordering constraints.
If I should be posting this to the Pacemaker list instead please let me know! I have a script that stops an LSB resource, manipulates some of it's files, then restarts the resource. When it executes the stop it not only stopped the LSB resource but also the underlying file system resource (but not the DRBD resource under that). Prior to updating it only stopped the LSB resource. I modified my ordering constraints around the LSB and now it works as expected. Here is the before and after: Command in script: crm resource stop p_lsb_arpwatch Before: order o_drbd_arpwatch_master_before_fs_arpwatch_before_lsb_arpwatch inf: ms_drbd_arpwatch:promote p_fs_arpwatch:start p_lsb_arpwatch:start Command results in p_lsb_arpwatch and p_fs_arpwatch stopping After: order o_drbd_arpwatch_master_before_fs_arpwatch inf: ms_drbd_arpwatch:promote p_fs_arpwatch:start order o_fs_arpwatch_before_lsb_arpwatch inf: p_fs_arpwatch:start p_lsb_arpwatch:start Command results in only p_lsb_arpwatch stopping Is this a bug or do I not understand multi-resource ordering constraints properly? Thanks! Jake Smith Network Admin Argotec, Inc.
_______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
