Bug 907232

Summary:	Custom Materialized Views should be treated differently from regular product Materialized Views
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Eli Mesika <emesika>
Component:	ovirt-engine	Assignee:	Eli Mesika <emesika>
Status:	CLOSED ERRATA	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, bazulay, cboyle, dyasny, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul, yzaslavs
Target Milestone:	---	Keywords:	Improvement
Target Release:	3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:	sf9	Doc Type:	Enhancement
Doc Text:	The current implementation did not distinguish between Custom Materialized Views and Product Materialized Views. As a result, an upgrade could fail because the Custom Materialized Views contained errors. This has been fixed by adding the ability to distinguish between Custom Materialized Views and Product Materialized Views, adding a minimum refresh rate, and the ability to disable a Materialized view, rather than just fix it or delete it.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-10 21:46:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	917401

Description Eli Mesika 2013-02-03 21:53:15 UTC

Description of problem:
Custom Materialized Views should be treated differently from regular product  Materialized Views
Current implementation does not distinguish between custom Materialized Views and Product Materialized Views
As a result upgrade may fail because the Custom Materialized Views has errors.
Also, we may have MON morning affect when lot of users are logged-in at the same time, in this case, it is important to set a minimum refresh rate for some Materialized Views in order to prevent refreshing those views too frequently.
Last, up till now if a Materialized View has a problem, the option is only to fix it or delete it, we should have an option to disable a Materialized View as well.


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


How reproducible:
Always

Steps to Reproduce:
1.Define a custom materialized View that has sql errors
2.upgrade rhevm
3.upgrade throw an error an stop
  
Actual results:
upgrade throw an error an stop if custom materialized view has errors

Expected results:
upgrade should only report errors on custom materialized views and continue


Additional info:

http://www.ovirt.org/OVirt-DB-Issues/MaterializedViews

Comment 1 Eli Mesika 2013-02-13 17:44:58 UTC

fixed in commits: 7f6c14d, 2f503ab

Comment 3 Eli Mesika 2013-02-25 09:18:57 UTC

How to test: (MV = Materialized View)

Test the API (see http://www.ovirt.org/OVirt-DB-Issues/MaterializedViews for details ans examples)

1) Create a custom MV
2) run the upgrade script 
3) run the application
4) create a cron job that calls the refresh SP as described in the wiki
5) test application behaviour and performance

5) Test other API functionality of the MV such as changing refresh rate, disabling the refresh , dropping the MV etc.

candidates for testing : all *permission* views

Comment 7 Cheryn Tan 2013-04-03 06:53:39 UTC

This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 9 errata-xmlrpc 2013-06-10 21:46:08 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.

http://rhn.redhat.com/errata/RHSA-2013-0888.html