Details
-
Task
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
cmapi-1.6.3, cmapi-1.5, cmapi-1.6, cmapi-1.6.2
-
None
Description
Removing one single node in some cases can produces Single node cluster.
- No MCS services stopped after removing node from single node.
reproduce:
add node by ip then remove using hostname or fqdn, got one active node with name
127.0.0.1. If use same name while add\remove process got no active nodes but all working
mcs processes as a result.
I guess the main reason is in coping SingleNode.xml config while removing node from cluster with one active node.
Attachments
Issue Links
- includes
-
MCOL-5345 Fix SingleNode.xml causing PrimProc failure.
- Closed