Comment 3 for bug 1403558

Is it not the same as "nodes should be manually removed from corosync "?
I remove it manually and restart 1 alive controller- cluster continue working without quorum

# crm_node --force -R node-20.domain.tld
# crm_node --force -R node-18.domain.tld

[root@node-19 ~]# pcs status
Cluster name:
Last updated: Thu Dec 18 14:03:32 2014
Last change: Thu Dec 18 14:02:08 2014 via crm_attribute on node-19.domain.tld
Stack: classic openais (with plugin)
Current DC: node-19.domain.tld - partition WITHOUT quorum
Version: 1.1.10-14.el6_5.3-368c726
1 Nodes configured, 3 expected votes
11 Resources configured

Online: [ node-19.domain.tld ]

Full list of resources:

 vip__management_old (ocf::mirantis:ns_IPaddr2): Started node-19.domain.tld
 vip__public_old (ocf::mirantis:ns_IPaddr2): Started node-19.domain.tld
 Clone Set: clone_ping_vip__public_old [ping_vip__public_old]
     Started: [ node-19.domain.tld ]
 Clone Set: clone_p_mysql [p_mysql]
     Started: [ node-19.domain.tld ]
 Master/Slave Set: master_p_rabbitmq-server [p_rabbitmq-server]
     Masters: [ node-19.domain.tld ]
 Clone Set: clone_p_haproxy [p_haproxy]
     Started: [ node-19.domain.tld ]
 Clone Set: clone_p_openstack-heat-engine [p_openstack-heat-engine]
     Started: [ node-19.domain.tld ]
 Clone Set: clone_p_neutron-openvswitch-agent [p_neutron-openvswitch-agent]
     Started: [ node-19.domain.tld ]
 Clone Set: clone_p_neutron-metadata-agent [p_neutron-metadata-agent]
     Started: [ node-19.domain.tld ]
 p_neutron-dhcp-agent (ocf::mirantis:neutron-agent-dhcp): Started node-19.domain.tld
 p_neutron-l3-agent (ocf::mirantis:neutron-agent-l3): Started node-19.domain.tld