Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1079403

Summary:	Postgres Plugin - Table Vacuum Fails
Product:	[JBoss] JBoss Operations Network	Reporter:	Matt Mahoney <mmahoney>
Component:	Plugin -- Other	Assignee:	Thomas Segismont <tsegismo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	tsegismo
Target Milestone:	DR01
Target Release:	JON 3.2.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-29 00:16:59 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:
Bug Depends On:	1095369
Bug Blocks:	1082792

Description Matt Mahoney 2014-03-21 14:23:53 UTC

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:

Comment 1 Thomas Segismont 2014-04-08 11:54:51 UTC

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

Comment 2 Thomas Segismont 2014-05-09 15:27:33 UTC

Cherry-picked over to release/jon3.2.x

commit 1b4ff09b813cee73b251fb5b94b779bc0e2503f7
Author: Thomas Segismont <tsegismo>
Date:   Tue Apr 8 13:52:58 2014 +0200

Comment 3 Simeon Pinder 2014-05-22 15:15:35 UTC

Via product triage, determined that this bug is to be included for DR01 target milestone.

Comment 4 Simeon Pinder 2014-05-30 02:43:33 UTC

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/

Comment 5 Mike Foley 2014-05-30 18:48:58 UTC

Verified JON 3.2.2 DR1

Comment 6 Larry O'Leary 2014-07-29 00:16:59 UTC

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