Description of problem: Making one or more changes to the Configuration, and then saving the changes does not result in the configuration being updated. Looking at the History, it can be seen that the changes to the configuration do save successfully, but the latest changes to not become current. Version-Release number of selected component (if applicable): 4.10.0-SNAPSHOT How reproducible: Always Steps to Reproduce: 1. Navigate to Inventory.Servers.postgres, and then click on Configuration tab 2. Make one more more changes to the configuration, and then click Save button. 3. View History, and validate that the configuration save was success. 4. Navigate back to the Configuration tab and validate whether the new changes were current. Actual results: Configuration changes to not update after saving. Expected results: Configuration changes should be updated after saving. Additional info:
When you don't run the agent as root or postgres user, nothing is saved and #updateConfiguration returns SUCCESS... So we need to clearly indicate that the update failed for that reason (now it's just an error message in agent logs) Also, some properties come from the postgres config file, some from the JDBC connection. The implementation to update properties over JDBC is missing. Eventually, we need to indicate in the ConfigurationUpdateReport that the resource needs a restart so that changes apply.
I was able to save a modified configuration (changed the 'Max_connections'). Can you list the properties you tried to change? Were they only "Runtime properties" (those gathered from the JDBC connection)?
I wonder how useful are Runtime-Parameter config definitions. According to the Postgres documentation [1], using 'SET' will only affect the current session, it's not persisted. I'd like to remove these parameters from configuration and add them to traits. [1] http://www.postgresql.org/docs/9.2/static/sql-set.html
Pushed to master commit d80a0032b012ea3318f1cea043df41aa5d9ffbc0 Author: Thomas Segismont <tsegismo> Date: Wed May 7 16:00:34 2014 +0200 Remove runtime-parameters from the list of configuration properties. They are now available as traits.
Cherry-picked over to release/jon3.2.x commit fba134e6e1d4a5e0d05e6f948a2e97484676f90c Author: Thomas Segismont <tsegismo> Date: Wed May 7 16:00:34 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