Bug 961294 - JON Agent installed using RPM cannot be silently configured
Summary: JON Agent installed using RPM cannot be silently configured
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.1.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER03
: JON 3.3.0
Assignee: Stefan Negrea
QA Contact: Armine Hovsepyan
Depends On:
TreeView+ depends on / blocked
Reported: 2013-05-09 11:17 UTC by bkramer
Modified: 2015-09-03 00:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-09-19 20:31:28 UTC
Type: Bug

Attachments (Terms of Use)
agent_rpm_silent_config (178.79 KB, image/png)
2014-08-25 12:36 UTC, Armine Hovsepyan
no flags Details
config_not_fount_error (69.94 KB, application/octet-stream)
2014-09-10 12:34 UTC, Armine Hovsepyan
no flags Details

Description bkramer 2013-05-09 11:17:39 UTC
Description of problem:
The only way to change agent configuration (RPM installation), as per Installation Guide [1] 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.

[1] https://access.redhat.com/site/documentation/en-US/JBoss_Operations_Network/3.1/html/Installation_Guide/changing-rpm-config.html

Version-Release number of selected component (if applicable):
JON 3.1.2

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Peter Larsen 2013-05-13 20:16:38 UTC
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.

Comment 3 Stefan Negrea 2014-06-20 18:59:06 UTC
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:



Comment 5 Simeon Pinder 2014-07-31 15:52:16 UTC
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993

Comment 6 Armine Hovsepyan 2014-08-25 12:36:41 UTC
Created attachment 930451 [details]

Comment 7 Armine Hovsepyan 2014-08-25 12:40:39 UTC
neither config nor status for agent service is working, re-assigned, screen-shot attached

Comment 9 Simeon Pinder 2014-09-03 20:31:48 UTC
Moving to ON_QA as available for test with the following brew build:

Comment 10 Armine Hovsepyan 2014-09-10 12:34:25 UTC
Created attachment 936127 [details]

Comment 11 Armine Hovsepyan 2014-09-10 12:35:03 UTC
config not found error is visible, while config full path is provided
re-assigning back

Comment 13 Stefan Negrea 2014-09-19 17:11:32 UTC
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.

Comment 14 Stefan Negrea 2014-09-19 17:12:45 UTC
Switching back to the ER3 for re-testing since there are no further code changes required.

Comment 16 Mike Foley 2014-09-29 14:41:39 UTC

Note You need to log in before you can comment on or make changes to this bug.