Bug 1546864

Summary: Remove vim_performance_tag_values table
Product: Red Hat CloudForms Management Engine Reporter: Nandini Chandra <nachandr>
Component: ReportingAssignee: Gregg Tanzillo <gtanzill>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: obarenbo, simaishi, smallamp, yrudman
Target Milestone: GA   
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.10.0.11 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 23:01:17 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:

Description Nandini Chandra 2018-02-19 20:23:22 UTC 
Description of problem:
-----------------------------
The commits made through https://bugzilla.redhat.com/show_bug.cgi?id=1530713 
were the first step to get rid of the vim_performance_tag_values DB table.

The commits addressed the following:

1)queries to the table have been removed
2)reads and writes to the table have been removed

The vim_performance_tag_values DB table still exists.So, I'm opening this BZ so that the table is removed.


Version-Release number of selected component (if applicable):
---------------
5.9.0.21


How reproducible:
-----------------
Always


Steps to Reproduce:
------------------
1.
2.
3.


Actual results:
---------------


Expected results:
-----------------


Additional info:
----------------
Comment 2 Gregg Tanzillo 2018-02-20 14:11:05 UTC 
https://github.com/ManageIQ/manageiq-schema/pull/147
https://github.com/ManageIQ/manageiq/pull/16728
Comment 3 Gregg Tanzillo 2018-02-20 14:11:05 UTC 
https://github.com/ManageIQ/manageiq-schema/pull/147
https://github.com/ManageIQ/manageiq/pull/16728
Comment 4 Nandini Chandra 2018-09-04 20:20:36 UTC 
verified in 5.10.0.14
Comment 5 errata-xmlrpc 2019-02-07 23:01:17 UTC 
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/RHSA-2019:0212