Description of problem: When changing the server configuration to be invalid (i.e. invalid "role name" and/or "role password) Status should be a user readable message instead of a stack trace. Note: The Server status and Child Resource status do report that there is an issue. Example: Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Navigate to Inventory.Connection Settings, and then change "role name" to an invalid value. 2. Click Save button, and then click "Connection Settings History", and then explore the Status message/text (aka: stack trace) 3. Actual results: Status text is a stack trace. Expected results: Status text should be more readable, and not a stack trace. Additional info:
Pushed to master commit dbeedced3664c0cda68f4a53b5bc789647cdd5f6 Author: Thomas Segismont <tsegismo> Date: Tue Apr 8 16:43:56 2014 +0200 Throwing an Exception is the only way a plugin component can fail the process of starting of a resource. So without changing the agent plugin facet we can't really avoid the stack trace shown on the server. Still, the stack trace shown when a Postgres server resource is configured with invalid credentials was particularly long, so I changed the plugin component implementation to make the server show a stack trace with no cause and a condensed message ("Invalid password").
Cherry-picked over to release/jon3.2.x commit 2076253a9be9e085a9b08d61d447490b6f369269 Author: Thomas Segismont <tsegismo> Date: Tue Apr 8 16:43:56 2014 +0200
Via product triage, determined that this bug is to be included for DR01 target milestone.
Moving to ON_QA as available for test in latest cumulative patch build(DR01): http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.2.GA/5-29-2014/
Verified JON 3.2.2 DR1
This has been verified and released in Red Hat JBoss Operations Network 3.2 Update 02 (3.2.2) available from the Red Hat Customer Portal[1]. [1]: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=31783