Description of problem: pg_temp_15.vacuum_l Table probably created during new postgres plugin operation 'Remove orphan large objects' introduced in bz 1381720 are discovered and shown in inventory. But they are later removed so they are marked in inventory as down and agent.log contains warnings: 2017-02-03 11:52:24,377 WARN [InventoryManager.availability-1] (rhq.core.pc.inventory.AvailabilityExecutor)- Availability collection failed with exception on Resource[id=12533, uuid=f1a4ff47-2e80-4c47-a4bd-7bf1ddb3a209, type={Postgres}Table, key=pg_temp_22.vacuum_l, name=pg_temp_22.vacuum_l, parent=rhq], availability will be reported as DOWN, reason=Failed to start component for Resource[id=12533, uuid=f1a4ff47-2e80-4c47-a4bd-7bf1ddb3a209, type={Postgres}Table, key=pg_temp_22.vacuum_l, name=pg_temp_22.vacuum_l, parent=rhq] - table does not exist Version-Release number of selected component (if applicable): JON3.3.8.ER02
This is because Postgres discovers temporary tables as normal tables.
Fixed in the master: commit 129ca1caf7ff084f115f4c00244e8fede267ca50 Author: Michael Burman <miburman> Date: Tue Apr 4 15:18:02 2017 +0300 [BZ 1419142] Do not discover tables in the pg_temp* namespace
Moving to ON_QA as available for test with the following binary: http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/133/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip *NOTE Build represents JON 3.3.9 DR01 build. Please report issues as you encounter them.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2846