Hide Forgot
Created attachment 1149766 [details] logs Description of problem: getting error on method when query timeline events on alarm/Status Change/Errors for pod Version-Release number of selected component (if applicable): cfme-5.6.0.4-beta2.3.1.el7cf.x86_64 atomic-openshift-node-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64 How reproducible: 100% Steps to Reproduce: 1. select compute -> containers -> pods -> select a pod that has events -> change events group to larm/Status Change/Errors 2. 3. Actual results: we get an exception Expected results: we should get alerts or no alerts message Additional info: Unexpected error encountered Errors in Management Engine can be caused by: ① Accessing Management Engine from multiple tabs or windows of the same browser on a single machine. Close any duplicate browser sessions, then select a menu option above. ② Pressing the back button during a session. Close any duplicate browser sessions, then select a menu option above. ③ An internal system error. Please contact your administrator for assistance. Error text: undefined method `container_group' for #<EmsEvent:0x00000006b12bb8> [container_group/tl_chooser] [root@dafna-openshift-master01 ~]# oc get events |grep jenkins-1-n3w7v 1h 1h 1 jenkins-1-n3w7v Pod Scheduled {scheduler } Successfully assigned jenkins-1-n3w7v to dafna-openshift-node02.qa.lab.tlv.redhat.com 1h 1h 1 jenkins-1-n3w7v Pod implicitly required container POD Pulled {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} Container image "openshift3/ose-pod:v3.1.1.6" already present on machine 1h 1h 1 jenkins-1-n3w7v Pod implicitly required container POD Created {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} Created with docker id f27c5ece0378 1h 1h 1 jenkins-1-n3w7v Pod implicitly required container POD Started {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} Started with docker id f27c5ece0378 1h 1h 1 jenkins-1-n3w7v Pod spec.containers{jenkins} Pulling {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} pulling image "registry.access.redhat.com/openshift3/jenkins-1-rhel7:latest" 1h 1h 1 jenkins-1-n3w7v Pod spec.containers{jenkins} Pulled {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} Successfully pulled image "registry.access.redhat.com/openshift3/jenkins-1-rhel7:latest" 1h 1h 1 jenkins-1-n3w7v Pod spec.containers{jenkins} Created {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} Created with docker id eaf5dafdc0a8 1h 1h 1 jenkins-1-n3w7v Pod spec.containers{jenkins} Started {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} Started with docker id eaf5dafdc0a8 1h 1h 1 jenkins-1-n3w7v Pod spec.containers{jenkins} Unhealthy {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} Readiness probe failed: 1h 1h 1 jenkins-1-n3w7v Pod spec.containers{jenkins} Unhealthy {kubelet dafna-openshift-node02.qa.lab.tlv.redhat.com} Readiness probe failed: 1h 1h 1 jenkins-1 ReplicationController SuccessfulCreate {replication-controller } Created pod: jenkins-1-n3w7v [root@dafna-openshift-master01 ~]#
Related to: https://github.com/ManageIQ/manageiq/issues/6508
Submited upstream: https://github.com/ManageIQ/manageiq/pull/7857
verified on cfme-5.6.0.5-beta2.4.1.el7cf.x86_64
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:1348