Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

Created attachment 535039 [details]
output of cibadmin after it reported the failure

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.