Bug 1104647

Summary: IllegalStateException: previousClusterSize[5] and newClusterSize[4] is not supported when undeploying storage node
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: Storage NodeAssignee: John Sanda <jsanda>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: JON 3.2.1CC: loleary, myarboro
Target Milestone: DR02Keywords: Triaged
Target Release: JON 3.2.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1104916 (view as bug list) Environment:
Last Closed: 2014-07-29 00:17:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1104916    
Bug Blocks:    
Attachments:
Description Flags
server log
none
storage log from fbr-jon32-dr1-4.bc.jonqe.lab.eng.bos.redhat.com none

Description Filip Brychta 2014-06-04 12:30:31 UTC
Created attachment 902165 [details]
server log

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

Comment 1 Filip Brychta 2014-06-04 12:37:19 UTC
Created attachment 902166 [details]
storage log from fbr-jon32-dr1-4.bc.jonqe.lab.eng.bos.redhat.com

Comment 2 Filip Brychta 2014-06-04 12:47:35 UTC
Status of the storage node is LEAVING even after restart of the node and jon server and 'Undeploy Selected' is disabled for all nodes.

Comment 3 Filip Brychta 2014-06-04 12:50:02 UTC
Oracle DB is used

Comment 4 John Sanda 2014-06-04 14:08:06 UTC
I am changing the severity of this to urgent because the undeploy process is essentially broken for a cluster size > 4.

Comment 5 John Sanda 2014-06-05 14:54:03 UTC
Fix committed and pushed to release/jon3.2.x branch.

commit hash: 2ab7ff613696

Comment 6 Simeon Pinder 2014-06-13 14:34:48 UTC
Moving to ON_QA as available for test in build:
http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.2.GA/6-13-2014_0900/

Comment 7 Filip Brychta 2014-06-16 13:25:18 UTC
Verified on
Version :	
3.2.0.GA Update 02
Build Number :	
dd34f04:ee37628

Comment 8 Larry O'Leary 2014-07-29 00:17:31 UTC
This has been verified and released in Red Hat JBoss Operations Network 3.2 Update 02 (3.2.2) available from the Red Hat Customer Portal[1].



[1]: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=31783