See https://projects.clusterlabs.org/T13#12405. We'll need an XSL transform to, at minimum, drop require-all from order constraints. Ideally, the XSL transform would grab the clone name from the ordering constraint and then add a clone-min="1" meta-attribute to the clone configuration. That may not be possible with XSL, however.
Description
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Restricted Maniphest Task | ||||
Restricted Maniphest Task | ||||
Open | None | T829 Drop support for require-all in order constraints |
Event Timeline
Comment Actions
@kgaillot I had added this as a parent task because we can't drop require-all from ordering constraints until after we've dropped support for rolling upgrades from <2.0.0
Comment Actions
I guess it's a matter of perspective :)
Set the policy of dropping support for rolling upgrades -> various tasks that break rolling upgrades
or
Various tasks that break rolling upgrades -> Dropping support for rolling upgrade is complete
Either approach works for me