2012/4/17 Andreas Kurz <span dir="ltr"><<a href="mailto:andreas@hastexo.com">andreas@hastexo.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 04/14/2012 11:14 PM, ruslan usifov wrote:<br>
> Hello<br>
><br>
> I remove 2 nodes from cluster, with follow sequence:<br>
><br>
> crm_node --force -R <id of node1><br>
> crm_node --force -R <id of node2><br>
> cibadmin --delete --obj_type nodes --crm_xml '<node uname="node1"/>'<br>
> cibadmin --delete --obj_type status --crm_xml '<node_state uname="node1"/>'<br>
> cibadmin --delete --obj_type nodes --crm_xml '<node uname="node2"/>'<br>
> cibadmin --delete --obj_type status --crm_xml '<node_state uname="node2"/>'<br>
><br>
><br>
> Nodes after this deleted, but if for example i restart (reboot) one of<br>
> existent nodes in working cluster, this deleted nodes appear again in<br>
> OFFLINE state<br>
<br>
</div>Just to double check ... corosync was already stopped (on these<br>
to-be-deleted nodes) prior to the deletion and it's still stopped on the<br>
removed nodes? ... and no cman involved?<br>
<br></blockquote></div><br>This nodes doesn't present physically:-)) (we remove this from network), so no corosync no cman not anything else<br>