Bug 1467333

Summary: exception when user switches between several reports with timelines
Product: Red Hat CloudForms Management Engine Reporter: Ievgen Zapolskyi <izapolsk>
Component: UI - OPSAssignee: Dávid Halász <dhalasz>
Status: CLOSED DUPLICATE QA Contact: Ievgen Zapolskyi <izapolsk>
Severity: high Docs Contact:
Priority: high    
Version: 5.8.0CC: hkataria, izapolsk, jhardy, mpovolny, obarenbo
Target Milestone: GAFlags: izapolsk: automate_bug-
Target Release: 5.8.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:report:timeline
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-21 07:30:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
exception
none
db dump none

Description Ievgen Zapolskyi 2017-07-03 12:25:45 UTC
Created attachment 1293882 [details]
exception

Description of problem:
I have 4 default timelines reports and 4 custom ones. Custom reports were made from default ones by slightly updating their filters to show this week events.
When I open reports one by one I get error page and exception in production.log.
I encounter the exception on almost each of those default or custom reports.

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

How reproducible:
100%

Steps to Reproduce:
1. Add f.e. any vsphere provider to cfme
2. Collect events for some time (my db dump is attached) 
3. Go to Cloud Intel->Timelines page and remember default timelines reports
4. Go to Cloud Intel->Reports, find those reports and make their copies
5. Edit every custom report to display "This Week" events
6. Go back to Cloud Intel->Timelines
7. Run through default and custom reports one by one there

Actual results:
Error page and exception in logs

Comment 2 Ievgen Zapolskyi 2017-07-03 12:45:41 UTC
Created attachment 1293883 [details]
db dump

Comment 4 Ievgen Zapolskyi 2017-07-07 20:29:31 UTC
David, I made db dump using pg_dump. So, you have to import it using postgre tools as well.
btw, I successfully imported it before attaching it to BZ. One note you have to drop old vmdb_production before import because I forgot to specify "cleanup db" when I was dumping that db.

Comment 9 Ievgen Zapolskyi 2017-08-21 07:30:20 UTC
sure, I'll verify it along with 1475782. thank you

*** This bug has been marked as a duplicate of bug 1475782 ***