Description of problem: Pod warning info could not be cleared when warning icon disappears. Also event warning info couldn't be cleared Version-Release number of selected component (if applicable): openshift v1.3.0-alpha.1-400-g5493ff6-dirty kubernetes v1.3.0-alpha.3-599-g2746284 etcd 2.3.0+git How reproducible: Very Often Steps to Reproduce: 1. Create a test pod which could trigger warning info on console In this example, pod image yapei/test-volume:test1 could not be found cat << EOF > pod.yaml { "kind": "Pod", "apiVersion":"v1", "metadata": { "name": "test-volume-instruction" }, "spec": { "containers": [{ "name": "test-volume-instruction", "image": "yapei/test-volume:test1", "ports": [ { "containerPort": 8080 } ] }] } } EOF 2. Login to web console, and go to Browse -> Pod page 3. When warning icon is triggered, hover the icon and warning info will be displayed 4. When warning icon disappears(maybe change to other intermediate state), the warning context is still there 5. Check event warning info Actual results: 4. When warning icon disappears(maybe change to other intermediate state), the warning context is still there and shown on every page, there is no way to clear it 5. Event page warning info could not be cleared Expected results: 4. When warning icon disappears, popover context should also be cleared 5. Warning info should be cleared after mouse is moved away Additional info:
Created attachment 1168945 [details] EventWarningOnOverview
Created attachment 1168946 [details] WarningOnBrowsePage
Attachment WarningOnBrowsePage is captured from OSE openshift v3.2.1.2-1-g64665fc kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5
https://github.com/openshift/origin-web-console/pull/192
Merged to origin-web-console. Fix will be available in origin after next vendor.
Fix should be in origin master now.
Checked against devenv-rhel7_4656 openshift v1.3.0-alpha.2+5c862c0 kubernetes v1.3.0+57fb9ac etcd 2.3.0+git Now warning info on pod & event page will disappear when mouse is moved away Move to VERIFIED
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://access.redhat.com/errata/RHBA-2016:1933