Change Details

Reported by Andrew Beekhof In the scheduler input, `rsc_SAPHana_I13_HDB00` has the below promotion scores on four nodes, plus a 99-score promoted colocation with vpcip. * ib1-az1-dbn1[1] (with vpcip): 100 * ib1-az1-dbn2[2]: -12200 * ib1-az2-dbn1[3]: 150 * ib1-az2-dbn2[4]: -10000 The promotion priority on node 1 counts the colocation score twice (giving a total of 298) since 2984222d in 2.1.7. It appears this is a bug and not an improvement, but that needs to be verified.

Reported by Andrew Beekhof In the scheduler input F768756, `rsc_SAPHana_I13_HDB00` has the below promotion scores on four nodes, plus a 99-score promoted colocation with vpcip. * ib1-az1-dbn1[1] (with vpcip): 100 * ib1-az1-dbn2[2]: -12200 * ib1-az2-dbn1[3]: 150 * ib1-az2-dbn2[4]: -10000 The promotion priority on node 1 counts the colocation score twice (giving a total of 298) since 2984222d in 2.1.7. It appears this is a bug and not an improvement, but that needs to be verified.

Reported by Andrew Beekhof In the scheduler input F768756, `rsc_SAPHana_I13_HDB00` has the below promotion scores on four nodes, plus a 99-score promoted colocation with vpcip. * ib1-az1-dbn1[1] (with vpcip): 100 * ib1-az1-dbn2[2]: -12200 * ib1-az2-dbn1[3]: 150 * ib1-az2-dbn2[4]: -10000 The promotion priority on node 1 counts the colocation score twice (giving a total of 298) since 2984222d in 2.1.7. It appears this is a bug and not an improvement, but that needs to be verified.