[ClusterLabs] Problem with constraint definition field 'with-rsc-role="Master"'

[Tomas Jelinek]

Hi Vitaly,

You don't need to worry much about this.

When pcs is editing CIB, it prefers using the new role names and 
automatically falls back to the old role names based on pacemaker / CIB 
schema version. When pcs is printing the configuration, it does a 
reverse transformation and prints the new role names even if CIB 
contains the old ones.

Pacemaker 2.1, which pcs 0.11 is compatible with, is capable of handling 
both old and new role names.

If you want to get rid of the old role names, you may replace them in 
CIB ('pcs cluster edit') or drop the constraints and recreate them using 
pcs. If it fails, you maybe have an old CIB version. You can update that 
with 'pcs cluster cib-upgrade'.

Regards,
Tomas


Dne 09. 04. 25 v 20:35 vitaly napsal(a):
> Hello,
> I have dual node clusters with postgres as one of the resources.
> The clusters were upgraded from pcs v 0.10 to pcs v 0.11.
> Pcs V 0.11 eliminated Master role and replaced it with Promoted.
> For clusters that were upgraded I needed to remove old configuration 
> for colocation because with old one in place while creating new one 
> commit of the configuration was failing due to duplicate constraint.
> Update works fine on all the clusters but on one of them AFTER UPGRADE 
> I see different output in “cibadmin --query” and in “pcs constraint list”
> The constraints in “cibadmin –query” are showing:
> <rsc_colocation rsc="DBSlave" with-rsc="postgres-ms" score="-10000" 
> rsc-role="Started" with-rsc-role="Master" 
> id="colocation-DBSlave-postgres-ms-Promoted"/>
> <rsc_colocation rsc="DBMaster" with-rsc="postgres-ms" score="INFINITY" 
> rsc-role="Started" with-rsc-role="Master" 
> id="colocation-DBMaster-postgres-ms-Promoted"/>
> Same constraints in “pcs constraint list” were showing:
> Colocation Constraints:
> Started resource 'DBSlave' with Promoted resource 
> 'postgres-ms' score=-10000
> Started resource 'DBMaster' with Promoted resource 
> 'postgres-ms' score=INFINITY
> On all other systems “cibadmin –query” is in agreement with pcs and 
> shows:
> <rsc_colocation rsc="DBSlave" with-rsc="postgres-ms" score="-10000" 
> rsc-role="Started" with-rsc-role="Promoted" 
> id="colocation-DBSlave-postgres-ms-Promoted"/>
> <rsc_colocation rsc="DBMaster" with-rsc="postgres-ms" score="INFINITY" 
> rsc-role="Started" with-rsc-role="Promoted" 
> id="colocation-DBMaster-postgres-ms-Promoted"/>
> So my problem is in with-rsc-role showing “Master” on a single system 
> and “Promoted” on all others.
> Would appreciate it if anybody could shed some light on the issue.
> Thank you very much!
> _Vitaly
>
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home:https://www.clusterlabs.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20250410/e1bdee5b/attachment.htm>