Bug 1121994
Summary: | Ovirt-engine-dwh fails to collect statistics due to high number in database sequences. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Roman Hodain <rhodain> |
Component: | ovirt-engine-dwh | Assignee: | Shirly Radco <sradco> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.4.0 | CC: | aberezin, abisogia, bazulay, dsulliva, ecohen, iheim, juwu, lnovich, meverett, pmatyas, rbalakri, Rhev-m-bugs, sradco, tdosek, yeylon, ylavi |
Target Milestone: | --- | ||
Target Release: | 3.5.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | infra | ||
Fixed In Version: | vt5 - rhevm-dwh-3.5.0-4.el6ev | Doc Type: | Release Note |
Doc Text: |
Previously, in specific cases the DWH was unable to insert new records to the ovirt_engine_history database as some of the sequences next value contained a higher number than what the primary key could store. With this update, the column of "history_id" for statistics tables has been changed from type integer to type bigint. Note that if users use the previous version through the REST API, they will need to update the history_id type to bigint in their environment.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-11 18:15:52 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: | 1156162 |
Description
Roman Hodain
2014-07-22 10:13:47 UTC
We should change all columns to bigint. Yaniv Barak, what do you think we should do regarding the legacy views? If we change the column type to bigint it can brake their api and if we dont they will not they may hit the int limit. Shirly This needs to be addressed by moving to big int. The might only influence customers who upgrade to 3.5 and still use older viewes. I don't thing there are any such customers Tomas ? This fix should go in with appropriate release note message (for 3.5) I totally agree with Barak. Releasing this fix with a proper release not seems like the solution we need here. With regards to customers using legacy views, I don't really think we have any customer using these on never versions. Why did this fail qe? Behaviour is the same as in description. using vt2.2 Can you please attach the logs? Thanks, Shirly This bug need to be checked on upgrade from 3.4 to 3.5 and not between 3.5.0 versions. 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://rhn.redhat.com/errata/RHEA-2015-0177.html |