Hi Kristoffer
I reproduced the error with latest changest(b5ffd99e).
My config.crm file
-----------------------------------------
property \
no-quorum-policy="ignore" \
stonith-enabled="false"
# comment
rsc_defaults \
resource-stickiness="INFINITY" \
migration-threshold="1"
-----------------------------------------
# rpm -qa | grep pacemaker
pacemaker-cli-1.1.11-0.1.83fc351.git.el6.x86_64
pacemaker-cluster-libs-1.1.11-0.1.83fc351.git.el6.x86_64
pacemaker-libs-1.1.11-0.1.83fc351.git.el6.x86_64
pacemaker-1.1.11-0.1.83fc351.git.el6.x86_64
# python --version
Python 2.6.6
# crm --version
1.2.6-0.rc1.el6 (Build b5ffd99e8bce)
# crm configure load update config.crm
Call cib_apply_diff failed (-203): Update does not conform to the
configured schema
<cib epoch="5" num_updates="1" admin_epoch="0"
validate-with="pacemaker-1.2" crm_feature_set="3.0.7"
cib-last-written="Wed Aug 21 13:46:15 2013" update-origin="16-sl6"
update-client="cibadmin" have-quorum="0" dc-uuid="1084752244">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<nvpair id="cib-bootstrap-options-dc-version"
name="dc-version" value="1.1.11-0.1.83fc351.git.el6-83fc351"/>
<nvpair id="cib-bootstrap-options-cluster-infrastructure"
name="cluster-infrastructure" value="corosync"/>
<nvpair name="no-quorum-policy" value="ignore"
id="cib-bootstrap-options-no-quorum-policy"/>
<nvpair name="stonith-enabled" value="false"
id="cib-bootstrap-options-stonith-enabled"/>
</cluster_property_set>
</crm_config>
<nodes>
<node id="1084752244" uname="16-sl6"/>
</nodes>
<resources/>
<constraints/>
<rsc_defaults>
<meta_attributes id="rsc-options">
<comment/>
<nvpair name="resource-stickiness" value="INFINITY"
id="rsc-options-resource-stickiness"/>
<nvpair name="migration-threshold" value="1"
id="rsc-options-migration-threshold"/>
</meta_attributes>
</rsc_defaults>
</configuration>
<status>
<node_state id="1084752244" uname="16-sl6" in_ccm="true"
crmd="online" crm-debug-origin="do_state_transition" join="member"
expected="member">
<lrm id="1084752244">
<lrm_resources/>
</lrm>
<transient_attributes id="1084752244">
<instance_attributes id="status-1084752244">
<nvpair id="status-1084752244-probe_complete"
name="probe_complete" value="true"/>
</instance_attributes>
</transient_attributes>
</node_state>
</status>
</cib>
ERROR: could not patch cib (rc=203)
INFO: offending xml diff: <diff crm_feature_set="3.0.7">
<diff-removed>
<cib epoch="3"/>
</diff-removed>
<diff-added>
<cib epoch="4" num_updates="4" admin_epoch="0"
validate-with="pacemaker-1.2" crm_feature_set="3.0.7"
cib-last-written="Wed Aug 21 13:22:06 2013" update-origin="16-sl6"
update-client="crmd" have-quorum="0" dc-uuid="1084752244">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<nvpair name="no-quorum-policy" value="ignore"
id="cib-bootstrap-options-no-quorum-policy"
__crm_diff_marker__="added:top"/>
<nvpair name="stonith-enabled" value="false"
id="cib-bootstrap-options-stonith-enabled"
__crm_diff_marker__="added:top"/>
</cluster_property_set>
</crm_config>
<rsc_defaults __crm_diff_marker__="added:top">
<meta_attributes id="rsc-options">
<!--# comment-->
<nvpair name="resource-stickiness" value="INFINITY"
id="rsc-options-resource-stickiness"/>
<nvpair name="migration-threshold" value="1"
id="rsc-options-migration-threshold"/>
</meta_attributes>
</rsc_defaults>
</configuration>
</cib>
</diff-added>
</diff>
FYI, I have no error if I remove comment line.
-----------------------------------------
property \
no-quorum-policy="ignore" \
stonith-enabled="false"
rsc_defaults \
resource-stickiness="INFINITY" \
migration-threshold="1"
-----------------------------------------
Regards,
Takatoshi MATSUO
2013/8/21 Kristoffer Grönlund <[email protected]>:
> Hi Takatoshi-san,
>
> On Tue, 20 Aug 2013 14:18:49 +0900
> Takatoshi MATSUO <[email protected]> wrote:
>
>> Hi Kristoffer
>>
>> 2013/8/9 Kristoffer Grönlund <[email protected]>:
>> > I have been unable to reproduce this error in my test cluster. Could
>> > you provide the current cluster configuration, prior to applying the
>> > configuration update?
>>
>> I'll take and provide it.
>> Could you wait till tomorrow?
>>
>
> Yes, no problem! Thank you.
>
>> >
>> > Thank you,
>> > Kristoffer Grönlund
>> > [email protected]
>>
>> Thanks,
>> Takatoshi MATSUO
>> _______________________________________________________
>> Linux-HA-Dev: [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
>> Home Page: http://linux-ha.org/
>
>
>
> --
> // Kristoffer Grönlund
> // [email protected]
> _______________________________________________________
> Linux-HA-Dev: [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
