Bug 812000

Summary: Guide the user what to do when the agent token is "not there"
Product: [Other] RHQ Project Reporter: Heiko W. Rupp <hrupp>
Component: AgentAssignee: John Mazzitelli <mazz>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3CC: hrupp, mazz
Target Milestone: ---   
Target Release: RHQ 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-01 06:08:26 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Heiko W. Rupp 2012-04-12 09:45:28 EDT
snert:/im/rhq/modules/enterprise/agent/target/rhq-agent hrupp$ bin/rhq-agent.shListening for transport dt_socket at address: 8788
RHQ 4.4.0-SNAPSHOT [74326f0] (null)
The server has rejected the agent registration request. Cause: [org.rhq.core.clientapi.server.core.AgentRegistrationException:An agent is trying to register with an existing agent name [snert] without providing a valid security token. If you are attempting to re-register this agent, please consult an administrator to reconfigure this agent with its proper security token.]
Will retry the agent registration request soon...

Neither this, nor rhq-agent.sh --help tells me the magic -Dx=y combination to pass the token in - I think this is not user friendly.


We should either in that message list the property name - or on the server page that lists the token, so that a user that runs into that issue can easily fix it without googling etc.
Comment 2 John Mazzitelli 2012-04-12 09:57:31 EDT
the error messages are build in CoreServerServiceImpl - so any changes would go in there
Comment 3 John Mazzitelli 2012-04-12 10:28:55 EDT
git commit 5745929

message will now say:

An agent is trying to register with an existing agent name [snert] without providing a valid security token. If you are attempting to re-register this agent, please consult an administrator to obtain the agent's proper security token and restart the agent with the option "-Drhq.agent.security-token=<the valid security token>"
Comment 4 Heiko W. Rupp 2013-09-01 06:08:26 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.