Red Hat Bugzilla – Bug 1465829
pcs should warn when setting utilization attributes may unexpectedly have no effect
Last modified: 2017-07-21 07:03:59 EDT
Unfortunately, [bug 1158500] missed this guidance point completely
(also because the effect of utilization was never properly tested?).
When setting utilization attribute while the placement-strategy is
"default" (implicitly or not) ...
1. ... on-the-fly: emit guidance message that placement-strategy cluster
property needs to be changed for the current change to take effect
2. ... accumulate + push: ditto as for 1. + make the "grand check"
in the push stage that will verify that the final CIB indeed
carries placement-strategy set to non-default, if not, emit
the warning once more + perhaps prevent the push unless --force
Note also there's no restriction of available values for
placement-strategy values in the current code.
Some kind of warning should be present in both cli and gui.
In reply to Jan Pokorný from comment #0)
> Note also there's no restriction of available values for
> placement-strategy values in the current code.
It would be nice if pacemaker specified allowed values of cluster properties in pengine metadata (and others) in a nicely parsable form.
Also this should be covered in documentation and pcs man page / usage.
This is what has rung a bell for me about this configuration
intertwining (thanks, Ken):
Note there's also a precedent in pcs where the clash between
the non-properties configuration and particular cluster property
is also accompanied with a whistleblowing: