Description of problem:I am not able to remove WAR deployment from JON, applies for Deployment and DomainDeployment Version-Release number of selected component (if applicable): Version: 3.0.1.GA Build Number: bf8f49a:9fe6384 EAP6 ER4.1 jboss-as-7 from #1314 How reproducible:always Steps to Reproduce: 1. create Deployment on standalone EAP6 2. wait 'till it's discovered 3. delete it Actual results:deployment is removed from EAP, but resource remains in inventory. Also removal operation result is SUCCESS. Deployment then becomes OFFLINE and further attemts to remove it are failing (wich makes sense, since deployment is no longer present on EAP) Expected results: deployment is removed and also disappears from inventory Additional info:
Does it stay in inventory (child of server) or only in the left nav tree? Works for me on master
Retested this and it works with the latest code. The deployment is deleted from JON and EAP.
I've currently re-tested this on JON 3.1RC1, and the issue is still here. Steps to Reproduce: 1. create Deployment on standalone EAP6 2. wait 'till it's discovered 3. delete it 4. run manual autodiscovery on platform After step 3. deployment is correctly removed from EAP and also from UI (removal operation is successfull) After step 4. resource appears in inventory again, in agent.log there is an interesting message: INFO [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Sending [runtime] inventory report to Server... INFO [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Syncing local inventory with Server inventory... INFO [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Got unknown resource: 11531 WARN [ResourceContainer.invoker.daemon-67] (rhq.modules.plugins.jbossas7.DeploymentComponent)- Could not determine the location of the deployment - the content descriptor wasn't found for deploymentAddress{path: deployment=hello.war}.
This sounds a lot like a general sync issue in the plugin container and not especially as7-plugin related.
Extensively debugged and rested this however I cannot get it to fail with the latest code. There were several enhancements done to the discovery process that could have resolved this issue. Please retest with the latest JON ER build. If it fails again, please attach the test application to this ticket. Might be something specific to the deployment used.
Version: 4.4.0.JON310-SNAPSHOT Build Number: 31b4844
Bulk closing of old issues in VERIFIED state.