Red Hat Bugzilla – Bug 1034218
EAR subdeployments are not discovered for DomainDeployment
Last modified: 2015-11-01 19:43:48 EST
Created attachment 828644 [details] kitchensink-ear Description of problem: JON currently cannot discover EAR subdeployments (and their runtime child subsystems) Version-Release number of selected component (if applicable): JON 3.2.0.ER7 How reproducible: always Steps to Reproduce: 1. have EAP 6 in domain mode 2. deploy ear (see attachment) as domain deployment 3. assign it to all server groups 4. run discovery Actual results: ear is discovered on managed servers, but without any children. If you deploy the same ear to standalone server you'll see 2 subdeployments with web/ejb3/jpa runtime subsystems Expected results: ear deployment should be discovered same way as on standalone mode Additional info:
Setting as 3.2 blocker for further triage. Reasons: Within JON 3.2 there has been added alot of runtime subsystems support (web,jpa,ejb (calltimes)), we do support some of them on domain mode as well (at least web subsystem - Bug 912478). We should be able to support those features regardless the way a deployment is packaged.
Fixed in master commit d28e22f0c77f127efe6ff3f63f0f82e22c20083a Author: Thomas Segismont <tsegismo@redhat.com> Date: Tue Nov 26 18:52:31 2013 +0100
Moved back to ASSIGNED as it needs to be reviewed and cherry-picked over the 3.2.x branch
Cherry-picked over bug/1034218 commit f93fa4c72831225a79788fc049d4164caa1c831a Author: Thomas Segismont <tsegismo@redhat.com> Date: Tue Nov 26 18:52:31 2013 +0100 Lukas will review it
commit d7c63e2cecf690918c5f0d59de6a6e06eaf91237 Author: Thomas Segismont <tsegismo@redhat.com> Date: Tue Nov 26 18:52:31 2013 +0100 Bug 1034218 - EAR subdeployments are not discovered for DomainDeployment (cherry picked from commit d28e22f0c77f127efe6ff3f63f0f82e22c20083a) Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
Moving to ON_QA as available for testing in the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=336752 Note: the installed version is still JON 3.2.0.GA by design and this represents part of the payload for JON 3.2.1 also known as cumulative patch 1 for 3.2.0.GA. How this will be delivered to customers is still being discussed.
still visible in DR1 screen-shot attached
Created attachment 865097 [details] no-subdep
So my first commit fixed the problem of ejb, jpa ... etc runtimes not showing up on ManagedServerDeployment resources (wars in managed server). But not the problem of sub-deployments in managed server deployments... Fixed in master commit 88436871349b64251cc9c689a4291e6b9d9c56d6 Author: Thomas Segismont <tsegismo@redhat.com> Date: Fri Feb 21 16:54:28 2014 +0100 Added missing line: a Subdeployment can be a child of a ManagedServerDeployment
hmm... could not find commit 88436871349b64251cc9c689a4291e6b9d9c56d6 anywhere in the repo. have you pushed it, Thomas?
(In reply to Thomas Segismont from comment #14) > So my first commit fixed the problem of ejb, jpa ... etc runtimes not > showing up on ManagedServerDeployment resources (wars in managed server). > But not the problem of sub-deployments in managed server deployments... > > Fixed in master > > commit 88436871349b64251cc9c689a4291e6b9d9c56d6 > Author: Thomas Segismont <tsegismo@redhat.com> > Date: Fri Feb 21 16:54:28 2014 +0100 > > Added missing line: a Subdeployment can be a child of a > ManagedServerDeployment Ignore Comment 14 (I forgot to push to master) Now fixed in master commit d327d3ffccfdde166a746f42b542150fdd70d984 Author: Thomas Segismont <tsegismo@redhat.com> Date: Fri Feb 21 16:54:28 2014 +0100 Added missing line: a subdeployent can be a child of a ManagedServer deployment
branch: release/jon3.2.x link: https://github.com/rhq-project/rhq/commit/516a6af84 time: 2014-03-07 11:38:26 +0100 commit: 516a6af847cecd9df7f3b85d690250756e1bcd32 author: Thomas Segismont - tsegismo@redhat.com message: Bug 1034218 - EAR subdeployments are not discovered for DomainDeployment (cherry picked from commit d327d3ffccfdde166a746f42b542150fdd70d984) Signed-off-by: Jirka Kremser <jkremser@redhat.com>
Moving to ON_QA as available for test in newest cumulative patch build from here: http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.1.GA/4-01-2014/ I moved the earlier build to 3-18-2014.
Created attachment 882144 [details] sub_dep-NA
no sub-deployment resources visible - 3.2.0 with CP (#2) - screen-shot attached
Created attachment 882256 [details] Screenshot on inventory with master build Just tried on a recent master build and it works. How long did you wait after the "assign to server group operation" execution? It can take some time before the resource shows up.
Created attachment 882258 [details] applied_operation
Created attachment 882259 [details] auto-discovery
applied yesterday, ran auto-discovery several times, then re-ran auto-discover today, sub-resources are not yet visible. screen-shots attached
It appeared that the fix for that BZ is not included in the CP build pointed out by Comment 18
*** Bug 1091009 has been marked as a duplicate of this bug. ***
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
Created attachment 923220 [details] subdeployments
Created attachment 923267 [details] subdeployments-domain
verified in JON 3.3 DR1 (failed for eap plugin pack #1119505)-- screen-shots attached