Bug 755952

Summary: cibadmin update failure - Update does not conform to the configured schema/DTD
Product: Red Hat Enterprise Linux 6 Reporter: Jaroslav Kortus <jkortus>
Component: pacemakerAssignee: Andrew Beekhof <abeekhof>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: cluster-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-24 01:09:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
output of cibadmin after it reported the failure none

Description Jaroslav Kortus 2011-11-22 14:03:01 UTC 
Description of problem:
Using one example from cibadmin man page I got to the state when it refuses to proceed with reference that the update dos not conform to schema/DTD.

Command used was cibadmin --replace --scope resources --xml-text '<resources/>'. It ran successfully couple of times and then suddenly stopped. The operations I was doing on the cluster were adding/removing and migrating ipv4 and apache resources.

Version-Release number of selected component (if applicable):
pacemaker-1.1.6-3.el6.x86_64

How reproducible:
not sure

Steps to Reproduce:
1. setup pacemaker
2. setup ipv4 and apache resource
3. migrate, delete and recreate them
4. use cibadmin every now and then
  
Actual results:
after some time it stops working saying "Update does not conform to the configured schema/DTD"

Expected results:
cibadmin removes the resources when the command is used

Additional info:
Comment 2 Jaroslav Kortus 2011-11-22 14:03:51 UTC 
Created attachment 535039 [details]
output of cibadmin after it reported the failure
Comment 3 Andrew Beekhof 2011-11-24 01:09:32 UTC 
Resource migration is handled by the creation and deletion of location constraints.

Attempting to removing all the resources results in an unresolvable reference in:
   <rsc_location id="cli-standby-ClusterIP" rsc="ClusterIP">

The cluster detects this and as a result, refuses to accept the change.