Description of problem: Performing a table vacuum fails with the following error: History record: "The following resources failed to invoke the operation: rhq_advisory_buglist,rhq_alert_notification,rhq_advisory..." Resource Status example: "org.postgresql.util.PSQLException: ERROR: relation "rhq_tagging_resource_map" does not exist" Version-Release number of selected component (if applicable): 3.2 How reproducible: Always Steps to Reproduce: 1. Click <databaseName>.Tables 2. Click Schedules, and select Operation "Vacuum" from the drop-down list 3. Select "Schedule using" "Now", and then click "Schedule" button. 4. Click "History" button, and then drill into the latest record "Name". Evaluate the error once the Status is no longer "In Progress". Actual results: Vacuum fails with Error. Expected results: Vacuum should be successful. Additional info:
Fixed in master commit 45ddd7c1a1c6b8deae6b94ac211929324fc8ed75 Author: Thomas Segismont <tsegismo> Date: Tue Apr 8 13:52:58 2014 +0200 Changed sql query to include the schema which the table is part of. Also updated table component #invokeOperation method to use connection pooling support
Cherry-picked over to release/jon3.2.x commit 1b4ff09b813cee73b251fb5b94b779bc0e2503f7 Author: Thomas Segismont <tsegismo> Date: Tue Apr 8 13:52:58 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