[Pacemaker] crm_verify reports bogus "requires fencing but fencing is disabled" notices

[Andrew Beekhof]

Seems to be fixed in the latest 1.1.12 beta:

# tools/crm_verify -x ~/Downloads/cibadmin-Ql.txt -VVV
  notice: update_validation: 	pacemaker-1.2-style configuration is also valid for pacemaker-1.3
  notice: update_validation: 	Upgrading pacemaker-1.3-style configuration to pacemaker-2.0 with upgrade-1.3.xsl
  notice: update_validation: 	Transformed the configuration from pacemaker-1.2 to pacemaker-2.0
  notice: unpack_config: 	On loss of CCM Quorum: Ignore


On 2 Jul 2014, at 11:59 pm, Ron Kerry <rkerry at sgi.com> wrote:

> attached the requested output ...
> 
>> Can you send us the 'cibadmin -Ql' output?
> 
> On 2 Jul 2014, at 3:30 am, Ron Kerry <rkerry at sgi.com> wrote:
>> I have seen the following reporting coming out of crm_verify that is clearly misleading
>> to a sysadmin. Every resource defined with this sort of start/stop operations is called
>> out twice (presumably because this is a 2-node cluster)
>>  op start interval="0" timeout="xx" on-fail="restart" requires="fencing"
>>  op stop interval="0" timeout="xx" on-fail="fence"
>> 
>> piranha:~ # crm_verify -LVVV
>> notice: unpack_config:        On loss of CCM Quorum: Ignore
>> notice: unpack_operation:     DMF requires fencing but fencing is disabled
>> notice: unpack_operation:     CXFS requires fencing but fencing is disabled
>> notice: unpack_operation:     IP requires fencing but fencing is disabled
>> notice: unpack_operation:     IP2 requires fencing but fencing is disabled
>> notice: unpack_operation:     NFS requires fencing but fencing is disabled
>> notice: unpack_operation:     DMFSOAP requires fencing but fencing is disabled
>> notice: unpack_operation:     DMFMAN requires fencing but fencing is disabled
>> notice: unpack_operation:     OV requires fencing but fencing is disabled
>> notice: unpack_operation:     CXFS requires fencing but fencing is disabled
>> notice: unpack_operation:     IP requires fencing but fencing is disabled
>> notice: unpack_operation:     IP2 requires fencing but fencing is disabled
>> notice: unpack_operation:     OV requires fencing but fencing is disabled
>> notice: unpack_operation:     DMF requires fencing but fencing is disabled
>> notice: unpack_operation:     NFS requires fencing but fencing is disabled
>> notice: unpack_operation:     DMFMAN requires fencing but fencing is disabled
>> notice: unpack_operation:     DMFSOAP requires fencing but fencing is disabled
>> 
>> Fencing is enabled and perfectly functioning in this cluster.
> 
> -- 
> 
> Ron Kerry         rkerry at sgi.com
> 
> 
> <cibadmin-Ql.txt>_______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140704/64e58821/attachment-0003.sig>