On Fri, 2023-06-09 at 14:03 +0200, Ondrej Mular wrote: > To me, this seems like an issue in `crm_resource` as the error > message > comes from it. Pcs is actually using `crm_resource --move` when > moving > resources. In this case, pcs should call `crm_resource --move > REDIS-clone --node podnode3 --master`, you can see that if you run > pcs > with `--debug` option. I guess `crm_resource --move --master` creates > a location constraint with `role="Promoted"` and doesn't take into > account the currently used schema. However, I'm unable to test this > theory as I don't have any testing environment available at the > moment. > > Ondrej
Ah yes, you are correct. crm_resource does not check the current CIB first, it just submits a change. It bases the role name on whether pacemaker was built with the --enable-compat-2.0 flag, which is true for el8 and false for el9. We could change it to try with the new name first, and if that fails, retry with the old name. > > On Fri, 9 Jun 2023 at 01:39, Reid Wahl <nw...@redhat.com> wrote: > > On Thu, Jun 8, 2023 at 2:24 PM lejeczek via Users < > > users@clusterlabs.org> wrote: > > > > > > > > > > Ouch. > > > > > > > > Let's see the full output of the move command, with the whole > > > > CIB that > > > > failed to validate. > > > > > > > For a while there I thought perhaps it was just that one > > > pglsq resource, but it seems that any - though only a few > > > are set up - (only clone promoted?)resource fails to move. > > > Perhaps primarily to do with 'pcs' > > > > > > -> $ pcs resource move REDIS-clone --promoted podnode3 > > > Error: cannot move resource 'REDIS-clone' > > > 1 <cib crm_feature_set="3.17.4" > > > validate-with="pacemaker-3.6" epoch="8212" num_updates="0" > > > admin_epoch="0" cib-last-written="Thu Jun 8 21:59:53 2023" > > > update-origin="podnode1" update-client="crm_attribute" > > > have-quorum="1" update-user="root" dc-uuid="1"> > > > > This is the problem: `validate-with="pacemaker-3.6"`. That old > > schema > > doesn't support role="Promoted" in a location constraint. Support > > begins with version 3.7 of the schema: > > https://github.com/ClusterLabs/pacemaker/commit/e7f1424df49ac41b2d38b72af5ff9ad5121432d2. > > > > You'll need at least Pacemaker 2.1.0. > > > > > 2 <configuration> > > > 3 <crm_config> > > > 4 <cluster_property_set id="cib-bootstrap-options"> > > > 5 <nvpair > > > id="cib-bootstrap-options-have-watchdog" > > > name="have-watchdog" value="false"/> > > > 6 <nvpair id="cib-bootstrap-options-dc-version" > > > name="dc-version" value="2.1.6-2.el9-6fdc9deea29"/> > > > 7 <nvpair > > > id="cib-bootstrap-options-cluster-infrastructure" > > > name="cluster-infrastructure" value="corosync"/> > > > <snip> > > > crm_resource: Error performing operation: Invalid configuration > > > > > > _______________________________________________ > > > Manage your subscription: > > > https://lists.clusterlabs.org/mailman/listinfo/users > > > > > > ClusterLabs home: https://www.clusterlabs.org/ > > > > > > -- > > Regards, > > > > Reid Wahl (He/Him) > > Senior Software Engineer, Red Hat > > RHEL High Availability - Pacemaker > > > > _______________________________________________ > > Manage your subscription: > > https://lists.clusterlabs.org/mailman/listinfo/users > > > > ClusterLabs home: https://www.clusterlabs.org/ > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/