Bug 1390582

Summary: timelines for azure items displays duplicate events
Product: Red Hat CloudForms Management Engine Reporter: Ievgen Zapolskyi <izapolsk>
Component: ProvidersAssignee: Bronagh Sorota <bsorota>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: medium    
Version: 5.6.0CC: gblomqui, jfrey, jhardy, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: provider:event, ui:timelines, provider:azure
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-02 22:27:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Azure Target Upstream Version:
Attachments:
Description Flags
duplicate events
none
event_streams cut none

Description Ievgen Zapolskyi 2016-11-01 12:59:51 UTC
Created attachment 1216109 [details]
duplicate events

Description of problem:
There are often duplicate events for Azure in event_streams table.
All such duplicate events appear in timelines for provider/vm etc.

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


How reproducible:
100%

Steps to Reproduce:
1. Add Azure cloud provider to CFME
2. Create/Start/Stop/Remove vm in Azure
3. Check event_streams table for Azure events related to just created vm
4. Open timelines for Azure provider

Actual results:
Both timelines and event_streams contain duplicate events.
Such events clog timelines.

Expected results:
Duplicate events shouldn't appear in Timelines.
It would be good if duplicate events wouldn't be added to db.


Additional info:
screenshot and csv file of event_streams are attached.
It seems only *EndRequest events have duplicates.

Comment 2 Ievgen Zapolskyi 2016-11-01 13:03:26 UTC
Created attachment 1216110 [details]
event_streams cut

Comment 4 Greg Blomquist 2016-11-02 22:27:17 UTC

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