Bug 1441599
| Summary: | hawkular-wildfly-agent-installer does not work correctly with running EAP | ||
|---|---|---|---|
| Product: | [JBoss] Middleware Manager | Reporter: | Filip Brychta <fbrychta> |
| Component: | Agent, download agent | Assignee: | jstickle |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | jdoyle, mmahoney |
| Target Milestone: | ER3 | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature: Agent Installer
Reason: Document that the EAP server must be down when running the agent installer.
Result:
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-20 19:54:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This has never been a requirement of the installer - in fact, it has always been that we assumed the server is down at the time you install the agent. Is this a new requirement or just a "nice to have" - because as it is, the installer requires the server to be down for it to work. Let's ensure that the documentation specifies that EAP should be down. If we find demand for install on a live server, I will log a new requirement. Added a note to the doc that EAP must be down to install the agent. https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_middleware_management/7.0.techpreview/html-single/installing_red_hat_middleware_management_with_cloudforms/#installing_the_middleware_management_agent |
Description of problem: Currently hawkular-wildfly-agent-installer requires the EAP to be stopped to install hawkular-wildfly-agent. It should be possible to install the agent while the EAP is running as well. Version-Release number of selected component (if applicable): mm DR04 eap7-middleware-manager-agent-0.29.3-1.Final_redhat_1.1.ep7.el7 How reproducible: Always Steps to Reproduce: 1. install EAP 7 (yum groupinstall jboss-eap7) 2. start it (systemctl start eap7-standalone) 3. install hawkular wildfly agent (yum install eap7-middleware-manager-agent-0.29.3-1.Final_redhat_1.1.ep7.el7.noarch.rpm) 4. configure the agent: export JBOSS_HOME=/opt/rh/eap7/root/usr/share/wildfly/ java -jar ${JBOSS_HOME}/bin/hawkular-wildfly-agent-installer.^Cr --target-location=${JBOSS_HOME} --server-url=http://hawkular.bc.jonqe.lab.eng.bos.redhat.com:8080 --username=jdoe --password=password --config-only=true 5. update some configuration via jboss-cli and reload (e.g. /opt/rh/eap7/root/usr/share/wildfly/bin/jboss-cli.sh --connect --commands="/subsystem=datasources/data-source=ExampleDS:write-attribute(name=max-pool-size,value=12),reload") Actual results: After step 4 the standalone.xml is correctly update, but after step 5 all the changes are overwritten. Expected results: Changes should be permanent (done via jboss-cli) Additional info: Solutions would be to use jboss-cli and embedded server or admin-only mode which should be available for EAP 6 as well.