Bug 781586
Summary: | Agent update results in environment specific configuration being lost | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Larry O'Leary <loleary> |
Component: | Installer | Assignee: | John Mazzitelli <mazz> |
Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.2 | CC: | hrupp, mazz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
JON 2.4.1 upgraded to JON 3.0.0
|
|
Last Closed: | 2012-02-14 14:42:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Larry O'Leary
2012-01-13 19:38:46 UTC
i'll test this - auto-upgrade SHOULD be copying over the original _env.sh script for this very purpose - to maintain customized environment settings. We specifically tell people that they can cusotmize the _env.sh, just not the main launcher scripts: http://rhq-project.org/display/JOPR2/RHQ+Agent+Installation#RHQAgentInstallation-DoNotAlterTheLauncherScripts FYI: I ran a quick test on my master branch, I edited rhq-agent-env.sh, forced a agent auto-upgrade, and the rhq-agent-env.sh changes were still there. (In reply to comment #2) > FYI: I ran a quick test on my master branch, I edited rhq-agent-env.sh, forced > a agent auto-upgrade, and the rhq-agent-env.sh changes were still there. I this is the case, you can reject this as not able to reproduce. From the looks of it, the person who originally reported the error was not clear on where they edited the JVM options and I did not attempt to reproduce as I should have. My guess is that they were editing the start script directly. Sorry about the false alarm. while the -env scripts are maintained, the one item in the description has never been intended to be supported: > JON 2.4.1 Agent has its log4j configuration modified to reduce the verboseness > of an installed plug-in. When JON 3.0.0 is installed, the log4j configuration > is discarded and the default configuration is used. We do not maintain log4j changes across upgrades. If a customer has a custom log4j file, the solution is that they should prepare a custom agent distribution and install it in the server so when agents auto-upgrade themselves, they can pick up the custom log4j.xml. see http://rhq-project.org/display/JOPR2/Preconfiguring+the+Agent#PreconfiguringtheAgent-BuildingYourOwnPreconfiguredAgentBundle for how to prepare a preconfigured agent bundle. But as it is, the agent update is working as expected. You only add environment customizations in the -env scripts. |