Description of problem: Cannot deploy a bundle to domain mode. Groups of Host Controller or Managed Servers do not appear in bundle deployment dropdown Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Spin up EAP in domain mode 2. Create Group of Host Controllers and Group of Managed Servers 3. Add and try to deploy a bundle Actual results: Neither Group shows up in dropdown Expected results: At least one of the groups should show up Additional info:
*** Bug 847049 has been marked as a duplicate of this bug. ***
See BZ 847049 for some more discussion of the possible implementation approaches.
Fixed in master commit ad48260579effc8b5eea2e059895d8b4534352c7 Author: Thomas Segismont <tsegismo> Date: Thu Jul 3 10:19:20 2014 +0200
Heiko Rupp <hrupp> updated the status of jira JON3-7 to Resolved
Additional commit to master commit cede4b6da948a3218b55316166fd6fba049b008b Author: Thomas Segismont <tsegismo> Date: Thu Jul 24 16:06:57 2014 +0200 Deployment node must be created with the filename, not the runtime name See also Bug 1119781 - runtime name provided for deployment child creation overrides application name and path
(In reply to Thomas Segismont from comment #6) > Additional commit to master > > commit cede4b6da948a3218b55316166fd6fba049b008b > Author: Thomas Segismont <tsegismo> > Date: Thu Jul 24 16:06:57 2014 +0200 > > Deployment node must be created with the filename, not the runtime name > > See also Bug 1119781 - runtime name provided for deployment child creation > overrides application name and path Cherry-picked over to release/jon3.3.x commit 4afff8009c59cb1924180d5a237523f1b3d3b63b Author: Thomas Segismont <tsegismo> Date: Thu Jul 24 16:09:23 2014 +0200
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
JON3-7 task. taking QA contact
sorry, please. I move it back to ON_QA status - I actually missed the point - it's need to be checked for EAP6 _domain_ servers (I did making for Standalone ones).
REOPEN But there is an issue however even trying on EAP6 Domain Controllers: Steps to reproduce: 1. create a bundle (could be used the same in the comment#10. 2. make a system group from a EAP6 Domain agent (see attachments): 2.1. create group step 1 - bz_1050014_create_servergroup.png 2.2. choose the EAP6 Domain Controller resource (with recoursive checkbox selected) - bz_1050014_create_servergroup_step2.png 2.3 see the result - bz_1050014_servergroup.png 3. Try to deploy the bundle to that server group - failing 3.1. see attachment - bz_1050014_deploymentFails.png logs: agent.log === 2014-08-08 03:42:10,586 ERROR [ResourceContainer.invoker.nonDaemon-7] (org.rhq.plugins.ant.AntBundlePluginComponent)- Failed to deploy bundle [class org.rhq.core.pluginapi.bundle.BundleDeployRequest: deployment=[BundleResourceDeployment: bdd=[BundleDeployment[id=10012, name=Deployment [1] of Version [1.0] to [jon]]], resource=[Resource[id=12998, uuid=4a125223-a673-4ebb-bfe8-5db65532bfb6, type={JBossAS7}JBossAS7 Host Controller, key=hostConfig: /root/jboss-eap-6.0/domain/configuration/host.xml, name=EAP Domain Controller (master 0.0.0.0:8990), version=EAP 6.0.0.GA]]], full-deploy-directory=[/root/jboss-eap-6.0/domain/tmp/.], clean=[true], revert=[false]] java.lang.Exception: Failed to execute the bundle Ant script at org.rhq.plugins.ant.AntBundlePluginComponent.deployBundle(AntBundlePluginComponent.java:168) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocation.call(ResourceContainer.java:759) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: Failed to execute bundle deploy file [/root/rhq-agent/data/tmp/bundle-versions/10035/ant-bundle-recipe2643464848411448197.xml]. Cause: /root/rhq-agent/data/tmp/bundle-versions/10035/ant-bundle-recipe2643464848411448197.xml:6: Failed to deploy bundle [Jenkins build (Linux)] version [1.0]: java.lang.Exception: Handover failed: Handover[action='deployment', handoverParams=[antlib:org.rhq.bundle:handover-param [name='runtimeName', value='jenkins.war'], antlib:org.rhq.bundle:handover-param [name='serverGroup', value='jon-mercury']], failOnError=true] at org.rhq.bundle.ant.AntLauncher.executeBundleDeployFile(AntLauncher.java:154) at org.rhq.plugins.ant.AntBundlePluginComponent.executeDeploymentPhase(AntBundlePluginComponent.java:324) at org.rhq.plugins.ant.AntBundlePluginComponent.deployBundle(AntBundlePluginComponent.java:148) ... 9 more Caused by: /root/rhq-agent/data/tmp/bundle-versions/10035/ant-bundle-recipe2643464848411448197.xml:6: Failed to deploy bundle [Jenkins build (Linux)] version [1.0]: java.lang.Exception: Handover failed: Handover[action='deployment', handoverParams=[antlib:org.rhq.bundle:handover-param [name='runtimeName', value='jenkins.war'], antlib:org.rhq.bundle:handover-param [name='serverGroup', value='jon-mercury']], failOnError=true] at org.rhq.bundle.ant.type.DeploymentUnitType.install(DeploymentUnitType.java:300) at org.rhq.bundle.ant.type.DeploymentUnitType.upgrade(DeploymentUnitType.java:532) at org.rhq.bundle.ant.task.BundleTask.execute(BundleTask.java:170) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:179) at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:80) at org.rhq.bundle.ant.AntLauncher.executeBundleDeployFile(AntLauncher.java:150) ... 11 more Caused by: java.lang.Exception: Handover failed: Handover[action='deployment', handoverParams=[antlib:org.rhq.bundle:handover-param [name='runtimeName', value='jenkins.war'], antlib:org.rhq.bundle:handover-param [name='serverGroup', value='jon-mercury']], failOnError=true] at org.rhq.bundle.ant.type.DeploymentUnitType.install(DeploymentUnitType.java:274) ... 24 more ===
Created attachment 925120 [details] bz_1050014_create_servergroup.png
Created attachment 925121 [details] bz_1050014_create_servergroup_step2.png
Created attachment 925122 [details] bz_1050014_servergroup.png
Created attachment 925123 [details] bz_1050014_deploymentFails.png
mfoley user <mfoley> updated the status of jira JON3-7 to Reopened
I had a look at the screenshots and to me, it looks like you made a confusion between the JON resource group and the EAP 6 domain server group. The JON resource group is part of the bundle target and is chosen when creating the bundle destination. The EAP 6 server group is the name of the group of logical servers you want to deploy the application to. It has the value of the "serverGroup" handover parameter and is chosen when deploying the bundle. A default value may come from the bundle recipe.
# ON_QA after discussion with Thomas S. got the confusion which I made: following are two different things: resource group and the EAP6 domain server group (this is what I should be providing in serverGroup parameter). --- <tsegismont> open Inventory > Child resources subtab and then Create Child > Server group <tsegismont> you must not confuse an EAP Domain Server group <tsegismont> and a JON resource group <tsegismont> These are two different concepts ---
test documentation https://tcms.engineering.redhat.com/run/169471/?from_plan=14599 qe owner - garik
Created attachment 931488 [details] bundle_depl_domain
moving back to ON_QA until https://tcms.engineering.redhat.com/run/169471/?from_plan=14599 TCMS test run is finished
Back to MODIFIED, all blockers at MODIFIED or VERIFIED level
Moving to ON_QA as available for test with the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=385149
Created attachment 938451 [details] domain_delp
changing target release to ER04, to close with #1139684
all blocking BZs verified - moving to verified state thank you
mfoley user <mfoley> updated the status of jira JON3-7 to Resolved