Description of problem: Event message flickered on Monitoring page when message is updated in high frequency Version-Release number of selected component (if applicable): v3.3.0.14 How reproducible: Always Steps to Reproduce: 1. Create a test dc, pod will not be running since we don't have sufficient permission to create privileged containers $ cat dc.yaml apiVersion: v1 kind: DeploymentConfig metadata: labels: run: php-apache name: php-apache spec: replicas: 1 selector: run: php-apache template: metadata: labels: run: php-apache spec: containers: - image: gcr.io/google_containers/hpa-example imagePullPolicy: IfNotPresent name: php-apache resources: requests: cpu: 200m securityContext: privileged: true restartPolicy: Always securityContext: {} terminationGracePeriodSeconds: 30 triggers: - type: ConfigChange $ oc create -f dc.yaml deploymentconfig "php-apache" created 2. When deployment is running, go to Monitoring page Actual results: 2. During deployment process, it will try thousands of times to create pod, thus a lots of events is listed on Monitoring page and these events get flickered Expected results: 2. It's better to show one message only with trying times increased Additional info:
Created attachment 1187395 [details] EventsFlickering
Created attachment 1187397 [details] CleanEventMessageOnBrowseEventsPage
This should be fixed by https://github.com/openshift/origin-web-console/pull/276 which hasn't been vendored to origin yet.
Fix merging to origin in https://github.com/openshift/origin/pull/10222 Wait to put it in MODIFIED till its merged
This has been merged and is in OSE v3.3.0.17 or newer.
Checked against OCP v3.3.0.17 This fix wasn't merged yet
I will check when puddle newer than v3.3.0.17 is ready
If this is just waiting for a merge, it should be on Modified. Setting it there.
This is another issue caused by the origin-web-console enterprise branch not getting updated correctly during the update for ose/master
Hi, checked against v3.3.0.18, event message is displayed well now Could change it to ON_QA and I could verify