Description of problem: We use dell servers equipped with drac controller. For fencing we are using commad: <fencedevice agent="fence_drac5" cmd_prompt="admin1->" ipaddr="192.168.0.101" login="root" name="node1-drac" passwd="drac_password"/> but when config is updated cmd_prompt="admin1->" is changed to cmd_prompt="admin1->" It seems to not have any visible influence on fence capability but IMHO cluster config shouldn't be changed by system without any notification . Version-Release number of selected component (if applicable): RHEL 4U4 with 2.6.9-78.0.22.ELsmp ; system-config-cluster-1.0.54-2.0; rgmanager-1.9.87-1 How reproducible: always Steps to Reproduce: - create cluster.conf with cmd line as above - ccs_tool update /etc/cluster/cluster.conf - cman_tool version -r 4 - check cluster.conf Actual results: "admin1->" is changed to "admin1->" Expected results: "admin1->" should not be changed to "admin1->" Additional info: moreover when opening cluster.conf using GUI tool I got: Relax-NG validity error : Extra element fencedevices in interleave /etc/cluster/cluster.conf:21: element fencedevices: Relax-NG validity error : Element cluster failed to validate content /etc/cluster/cluster.conf:15: element device: validity error : IDREF attribute name references an unknown ID "node1-drac" /etc/cluster/cluster.conf fails to validate
anything?
The XML validity (cluster.ng is missing cmd_prompt for the fencedevice element) will be addressed as part of bug 597253. The other part (the change of the > to >) will not. CDATA and elements should have special characters escaped in order to be valid XML. I highly suspect libxml2 did this translation for us, not ccsd, system-config-cluster, or cluster.ng. *** This bug has been marked as a duplicate of bug 597253 ***