[ClusterLabs] Updating CIB Question Update does not conform to the configured schema

Tomas Jelinek tojeline at redhat.com
Mon Feb 22 04:01:21 EST 2021


Hi,

It seems to me that you defined 
"virtualip-instance_attributes-secondary_ip_address" id twice. That is 
not allowed, IDs must be unique.

Also note that multiple instance attributes with rules are not supported 
by pcs. Your CIB will work in general, just don't use pcs to update your 
'virtualip' resource instance attributes.

Regards,
Tomas


Dne 22. 02. 21 v 3:51 AM. E. napsal(a):
> Hi,
> I am using version 1.1.18 of pacemaker on my linux ubuntu 16.04.
> I am trying to push cib after updating and I keep getting the error below:
> 
> $ sudo pcs cluster cib-push cib_temp
> Error: unable to push cib
> Call cib_replace failed (-203): Update does not conform to the 
> configured schema
> 
> What I have added  was the sections in bold (I am trying to implement 
> multi subnet deployment)
>        <primitive class="ocf" id="virtualip" provider="heartbeat" 
> type="awsvip">
>          <instance_attributes id="virtualip-instance_attributes">
> *<rule id="Subnet1-IP" score="INFINITY">
> <expression id="Subnet1-Node" attribute="#uname" operation="eq" 
> value="ag1"/>
> </rule>*
>            <nvpair 
> id="virtualip-instance_attributes-secondary_ip_address" 
> name="secondary_ip_address" value="10.45.54.47"/>
>          </instance_attributes>
>          <instance_attributes id="virtualip-instance_attributes2">
> *<rule id="Subnet2-IP" score="INFINITY">
> <expression id="Subnet2-Node" attribute="#uname" operation="eq" 
> value="ag2"/>
> </rule>*
>            <nvpair 
> id="virtualip-instance_attributes-secondary_ip_address" 
> name="secondary_ip_address" value="10.45.54.147"/>
>          </instance_attributes>
> 
> Did I violate the schema ?  I saw a post at 
> https://www.drware.com/configure-multiple-subnet-alwayson-availability-groups-by-modifying-cib/ 
> <https://www.drware.com/configure-multiple-subnet-alwayson-availability-groups-by-modifying-cib/>
> Where the same portion was updated and there was no such issue?
> 
> I am using this version
> $ pacemakerd --version
> Pacemaker 1.1.14
> 
> Any insights?
> Thanks
> Ayman Els
> 
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> 
> ClusterLabs home: https://www.clusterlabs.org/
> 



More information about the Users mailing list