Description of problem: If EAP deployment is updated outside of JBoss ON, subdeployments are marked unavailable in ON Version-Release number of selected component (if applicable): 3.3 How reproducible: Steps to Reproduce: 1. Basically when I have a ear to deploy, let's say "abc-1.0.0.ear". I log into the JBoss Domain Console and upload the EAR into the Jboss Content Repo, then assign/deploy the EAR to a server group/JVM. Note: Jon picks up this EAR deployment and SubDeployments fine. 2. Now when I have a new version to deploy, let's say "abc-1.2.0.ear". I log into the JBoss Domain Console and unassign to old EAR from the server group, then I upload the new EAR into the Jboss Content Repo, then assign/deploy the EAR to a server group/JVM. Then I remove the old EAR from the JBoss Content Repo. Actual results: Note: Jon picks up this NEW EAR deployment, but seems to have trouble with the SubDeployments and thinks they are unavailable, maybe still referencing the old version? You have to uninventory the entire EAR and have the agent discovery it again for all subdeployments to become available again. Expected results: JBoss ON would pick up the new subdeployments Additional info:
Jay, does that ring a bell? (regarding versioned deployments)
With the versioned deployments we should see an abc.ear resource with version 1.0.0. And then later, the same resource with version 1.2.0. The subdeployments should be the same way, resources with stripped names and versioning based on the subdeployment archive versions. After the redeploy the version for each subdeployment should have been updated, if necessary. If the subdeployments are not going green it would indicate the the path's are incorrect (in the plugin config). Of course that should not be the case. Have we reproduced?
Jay, no I haven't replicated this locally. He is not deploying the new version via JBoss ON (that works) but via the EAP Admin Console.
As there is no documented reproducer attached to this report and it is unclear how the sub-deployments changed from the previous version, this issue is being closed. If you are still experiencing this issue, please provide a complete test/use case that can be used to reproduce the issue. This should include: - version 1 of sample application; - steps used to deploy sample application version 1; - version 2 of sample application; - steps used to deploy sample application version 2; - expected results; - actual results; - any other information that is necessary to reproduce this in an isolated lab instance;