Created attachment 1008537 [details] screenshot.zip Description of problem: On Uninventory of platform always display a confirmation message "You are going to uninventory at least one resource that may be used by the storage cluster. To avoid any errors in the future, you should undeploy the storage node prior to this step. Do you really want to continue at your own risk?" even when storage node is not installed or deployed or child resource of the Platform. Please find screenshots from attached screenshot.zip. Version-Release number of selected component (if applicable): JBoss ON Version: 3.3.1 How reproducible: Always Steps to Reproduce: 1. Login to JON UI then navigate to Inventory-->Resources-->Platforms-->select any one of the platform that does not storage node then click Uninventory button at the bottom. 2. Answer pop-up question "Are you sure you want to uninventory the selected resources? Note that if a selected resource still exists, then it will get rediscovered during its agent's next discovery scan" as Yes 3. Then in next pop-up window you will see message "You are going to uninventory at least one resource that may be used by the storage cluster. To avoid any errors in the future, you should undeploy the storage node prior to this step. Do you really want to continue at your own risk?" Actual results: The message "You are going to uninventory at least one resource that may be used by the storage cluster. To avoid any errors in the future, you should undeploy the storage node prior to this step. Do you really want to continue at your own risk?" is always displayed even if the Platform does not have storage node deployed. Expected results: The message "You are going to uninventory at least one resource that may be used by the storage cluster. To avoid any errors in the future, you should undeploy the storage node prior to this step. Do you really want to continue at your own risk?" should not be displayed if the Platform does not have storage node deployed. Additional info: Refer Screenshot "Screenshot-JON-Uninventory-Platform.png" from attached screenshot.zip.
This seemed intentional, as it wanted to recheck all the platform & storage node resources. Fixed in the master: commit 6459ce98b6eff39b7854b98b9ca47b1845968ccd Author: Michael Burman <miburman> Date: Wed Jun 24 21:20:20 2015 +0300 [BZ 1207276] Removing platform does not cause additional question
Ignore the previous commit, I've reverted it.
Fixed in the master: commit 78acc25d3a058fd94da49a07ff914fa83d83b42b Author: Michael Burman <miburman> Date: Wed Jul 1 16:34:42 2015 +0300 [BZ 1207276] Do not ask for second confirmation on uninventory if platform resource does not have storage nodes under it
Available for test with 3.3.3 ER01 build: https://brewweb.devel.redhat.com/buildinfo?buildID=446732 *Note: jon-server-patch-3.3.0.GA.zip maps to ER01 build of jon-server-3.3.0.GA-update-03.zip.
Still visible in ER01 Version : 3.3.0.GA Update 03 Build Number : e4b348a:2f80c8c
I'd like to see the situation in which it does, as in that case the parent does have storage nodes associated to it or plugin called RHQStorage is in use.
Fixed in master: commit cdba34c214c30db599301b84c71be4cdb9e61127 Author: Michael Burman <miburman> Date: Tue Jul 21 12:58:47 2015 +0300 [BZ 1207276] Rename parentResourceId -> filterParentResourceId
branch: release/jon3.3.x commit: e3d3e157097b0de7f30dd42b9bf0e1e974c89e43 Author: Michael Burman <miburman> AuthorDate: Tue Jul 21 12:58:47 2015 +0300 Commit: Simeon Pinder <spinder.com> CommitDate: Tue Jul 21 12:41:01 2015 -0400 [BZ 1207276] Rename parentResourceId -> filterParentResourceId
Available for test with following build: https://brewweb.devel.redhat.com/buildinfo?buildID=448923 *Note: jon-server-patch-3.3.0.GA.zip maps to CR01 build of jon-server-3.3.0.GA-update-03.zip.
Verified on Version : 3.3.0.GA Update 03 Build Number : edc324f:119e8f4
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1525.html