Description of problem:
The only way to change agent configuration (RPM installation), as per Installation Guide  would be to run config command:
service jon-agent config
which is equivalent to:
rhq-agent.sh --cleanconfig --setup --advanced --daemon --nostart
and will force interactive setup. However, RPM based agent installation can not be done via kickstart or satellite if interactive configuration is required. We should have something like:
service rhq-agent config --silent
where configuration will be done using whatever is specified in the agent.configuration file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Without an unattended install option, JON cannot be provisioned as part of a Satellite setup. They impedes customers from using a Red Hat supported provisioning solution. Being able to either manually deploy the configuration file without the need to run a "post config" script, or being able to provide an answer file directly to the "post config" script is important.
Other options should include the ability to specify the user-name or a group name the agent should have access to.
A silent flag does not help at all because the agent still needs to be configured to connect to the correct server. When installed via RPM, the agent is not pre-configured to connect back to the server where it was just downloaded because the RPM comes from RHN.
So instead of a flag the user will have to pass the path to a configuration file that will then be used to do a no-prompt configuration of the agent.
A sample command:
service jon-agent config /path/to/agent/config/agent-configuration.xml
The user can modify the default agent configuration and pass that in to the config command. The default config file is /etc/jboss-on/agent-configuration.xml
The code is now merged in master branch.
master branch commits:
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
Created attachment 930451 [details]
neither config nor status for agent service is working, re-assigned, screen-shot attached
Moving to ON_QA as available for test with the following brew build:
Created attachment 936127 [details]
config not found error is visible, while config full path is provided
This feature works as expected.
Please refer to the following documentation about RPMs:
The important aspect here is that by default the agent runs as a special user/group. In your test case, the config file was not accessible to this specific user.
There are two ways to correct the test case:
1) Run the agent under the hudson user. Update the init script with the correct user.
2) Give jbosson-agent user or jbosson group proper access to the configuration file.
Switching back to the ER3 for re-testing since there are no further code changes required.