Bug 1324733 - [z-stream clone - 3.6.6] engine-setup stage 'Setup validation' takes too long to complete
Summary: [z-stream clone - 3.6.6] engine-setup stage 'Setup validation' takes too long...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.7
Hardware: All
OS: Linux
high
medium
Target Milestone: ovirt-3.6.6
: 3.6.6
Assignee: Eli Mesika
QA Contact: Gonza
URL:
Whiteboard: infra
Depends On: 1323826
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-07 06:46 UTC by rhev-integ
Modified: 2019-12-01 09:20 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the audit_log table was not cleaned correctly, so the FK validation on that table took too long. As a result, the upgrade validation stage also took too long. Now, the audit_log cleanup mechanism has been fixed so that upgrade validation time is normal.
Clone Of: 1323826
Environment:
Last Closed: 2016-05-25 12:08:24 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1119 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager (rhevm) bug fix 3.6.6 2016-05-25 16:07:50 UTC
oVirt gerrit 55724 0 master MERGED core: cleanup old event notification history 2021-01-28 12:27:24 UTC
oVirt gerrit 55743 0 ovirt-engine-3.6 MERGED core: cleanup old event notification history 2021-01-28 12:27:24 UTC

Comment 2 Gonza 2016-05-12 10:19:43 UTC 
Verified with:
rhevm-3.6.6.2-0.1.el6.noarch

# \d+ event_notification_hist
...
Indexes:
    "idx_event_notification_hist" btree (audit_log_id)
    "idx_event_notification_hist_audit_log_id" btree (audit_log_id)
Foreign-key constraints:
    "fk_event_notification_hist_audit_log" FOREIGN KEY (audit_log_id) REFERENCES audit_log(audit_log_id) ON DELETE CASCADE
...

# select DeleteAuditLogOlderThenDate('2016-05-05 10:27:38.951+02');
Comment 4 errata-xmlrpc 2016-05-25 12:08:24 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://rhn.redhat.com/errata/RHBA-2016-1119.html
Note You need to log in before you can comment on or make changes to this bug.