Bug 1300371

Summary: events timeline scalability: not all events are shown under provider
Product: Red Hat CloudForms Management Engine Reporter: Dafna Ron <dron>
Component: UI - OPSAssignee: Dan Clarizio <dclarizi>
Status: CLOSED DUPLICATE QA Contact: Dafna Ron <dron>
Severity: high Docs Contact:
Priority: high    
Version: 5.5.0CC: cpelland, dajohnso, dajo, dkorn, dron, fsimonce, hkataria, jhardy, mpovolny, obarenbo
Target Milestone: GAFlags: dclarizi: needinfo? (dajo)
Target Release: 5.6.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: timeline
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-03 04:11:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
logs
none
screenshots none

Description Dafna Ron 2016-01-20 15:22:13 UTC
Created attachment 1116675 [details]
logs

Description of problem:

I created 100 pods and I cannot see all the events generated in the cm 

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

cfme-5.5.2.1-1.el7cf.x86_64

How reproducible:

100%

Steps to Reproduce:
1. create 100 pods 
oc scale --replicas=100 replicationcontrollers jenkins-1
2. select the providers from the providers menu -> select the openshift provider -> select the monitoring button -> timeline -> select menu: Create/Addition or Alarm/Status Change/Error
3.

Actual results:

not all of the pods or the alerts are shown on the timeline 

Expected results: 

we should be able to do paging if not all of the alerts can be shown for large number of pods. 

Additional info:

Comment 1 Federico Simoncelli 2016-01-25 22:24:25 UTC
Dafna do you have a quick way to reproduce and check if the events were in the database? (Get some help from Daniel if you need it)

Also a screenshot could help to determine if it is a UI issue.

Bottom line through peeking at the db and UI we should understand if this is a backend/collection issue or a frontend/display issue.

Comment 3 Dafna Ron 2016-03-09 19:16:17 UTC
Created attachment 1134624 [details]
screenshots

Adding screen shot. 

the issue is that we do not see all alerts that are shown by oc command.

Comment 4 Federico Simoncelli 2016-03-10 12:07:30 UTC
Dafna, a couple of comments. The supported events are:

CONTAINER_CREATED
CONTAINER_KILLING
CONTAINER_STARTED
CONTAINER_STOPPED
CONTAINER_UNHEALTHY
NODE_FAILEDMOUNT
NODE_INVALIDDISKCAPACITY
NODE_NODENOTREADY
NODE_NODENOTSCHEDULABLE
NODE_NODEREADY
NODE_NODESCHEDULABLE
NODE_REBOOT
POD_DEADLINEEXCEEDED
POD_FAILEDSCHEDULING
POD_FAILEDSYNC
POD_FAILEDVALIDATION
POD_HOSTPORTCONFLICT
POD_INSUFFICIENTFREECPU
POD_INSUFFICIENTFREEMEMORY
POD_NODESELECTORMISMATCHING
POD_OUTOFDISK
POD_SCHEDULED
REPLICATOR_FAILEDCREATE
REPLICATOR_SUCCESSFULCREATE

So some of the ones you see in the oc commands are not relevant for CFME.

That said, in screenshot 'events3.png' you're displaying several NodeNotReady/NodeReady/Rebooting events that should be visible in the "Power" category (no screenshot about that).

Anyway I agree that in fact in the 'event2.png' screenshot all the events are not shown because the timeline is not scalable.


Dafna, unless you experienced something container-specific, I believe that this should be moved to Dan as the timeline scalability (in terms of how many events can be shown), is a UI issue that should be resolved across all the providers.

Comment 5 Dafna Ron 2016-03-10 12:18:56 UTC
sure. this was indeed a scale bug. 
I can investigate further on smaller amounts of pods

Comment 6 Federico Simoncelli 2016-03-10 12:27:29 UTC
As this is a generic timeline ui scalability issue I am removing container from the whiteboard and assigning to Dan.

Comment 8 Federico Simoncelli 2016-04-29 11:19:22 UTC
Unrelated to containers. Removing from the whiteboard (again).

Comment 9 Dave Johnson 2016-05-03 04:11:06 UTC

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