Bug 913737

Summary: [as7] Changes to user name and/or password plug-in configuration properties don't get picked up by agent until restart
Product: [JBoss] JBoss Operations Network Reporter: Larry O'Leary <loleary>
Component: Plugin -- JBoss EAP 6Assignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: urgent    
Version: JON 3.1.2CC: myarboro, tsegismo
Target Milestone: ---   
Target Release: JON 3.2.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-12 15:12:31 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:

Description Larry O'Leary 2013-02-21 22:35:17 UTC
Description of problem:
If the management user or credentials change, the user is unable to update the values in the resource's plug-in configuration. Although the changes appear in the UI and are retrieved from the resource on future reloads of the resource, the agent does not pass these changes along to the resource's connection until you restart the agent or the agent plug-in container.

Version-Release number of selected component (if applicable):
4.4.0.JON312GA

How reproducible:
Always

Steps to Reproduce:
1. Install JBoss EAP 6 with a management user defined and start it.
2. Import EAP 6 server into inventory and update its connection settings to use the correct user and password.
3. Wait for service discovery to finish executing on the new EAP resource and for it to show as available in inventory.
4. Go back to the EAP resource's connection settings page and change the user and password values to something invalid. 
  
Actual results:
The EAP resource continues to be reported as available and metric continue to be collected.

Expected results:
The availability of the resource should have switched to down with an error indicating that the management user credentials may be invalid.

Additional info:
The use-case for this is when security credentials are updated for enterprise services based on security policy or when credentials are invalidated. The result is that the JBoss ON system must be restarted for the changes to take affect. This is not practical in a production environment or an environment that is managed by multiple IS teams monitored within a single JBoss ON system.

Comment 1 Larry O'Leary 2013-04-03 20:26:51 UTC
Perhaps this is related to bug 929200?

Comment 2 Thomas Segismont 2013-04-12 15:12:31 UTC
Closing as agreed with Charles. This is fixed with bug 929200 resolution.

*** This bug has been marked as a duplicate of bug 929200 ***