+++ This bug was initially created as a clone of Bug #1104647 +++ Description of problem: I had 6 storage nodes and I wanted to undeploy them one by one. First was undeployed succesfully but second was not and it stayed in LEAVING cluster status and following exception was thrown to server.log: Caused by: java.lang.IllegalStateException: previousClusterSize[5] and newClusterSize[4] is not supported Version-Release number of selected component (if applicable): Version : 3.2.0.GA Update 02 Build Number : 055b880:0620403 How reproducible: 1/1 Steps to Reproduce: 1. have 6 storage nodes all in status NORMAL 2. undeploy one of them and wait until it is gone 3. undeploy another one Actual results: Storage node stayed in status LEAVING and following exception was thrown to server.log Caused by: java.lang.IllegalStateException: previousClusterSize[5] and newClusterSize[4] is not supported Expected results: No errors Additional info: Complete server.log attached --- Additional comment from Filip Brychta on 2014-06-04 08:37:19 EDT --- --- Additional comment from Filip Brychta on 2014-06-04 08:47:35 EDT --- Status of the storage node is LEAVING even after restart of the node and jon server and 'Undeploy Selected' is disabled for all nodes. --- Additional comment from Filip Brychta on 2014-06-04 08:50:02 EDT --- Oracle DB is used --- Additional comment from John Sanda on 2014-06-04 10:08:06 EDT --- I am changing the severity of this to urgent because the undeploy process is essentially broken for a cluster size > 4.
fixed in master commit hash: 7c05050c6ea8
Verified on Version : 4.12.0-SNAPSHOT Build Number : 4745403
Bulk close of items fixed in RHQ 4.12 If you think this is not solved, then please open a *new* BZ and link to this one.