Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-27074

some events are missing time related infomration

XMLWordPrintable

    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, some Kubernetes API server events did not have the correct timestamps. With this release, Kubernetes API server events now have the correct timestamps. (link:https://issues.redhat.com/browse/OCPBUGS-27074[*OCPBUGS-27074*])
      Show
      * Previously, some Kubernetes API server events did not have the correct timestamps. With this release, Kubernetes API server events now have the correct timestamps. (link: https://issues.redhat.com/browse/OCPBUGS-27074 [* OCPBUGS-27074 *])
    • Bug Fix
    • Done

      Description of problem:

      Some events have time related infomration set to null (firstTimestamp, lastTimestamp, eventTime)
      

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

      cluster-logging.v5.8.0

      How reproducible:

      100% 

      Steps to Reproduce:

          1.Stop one of the masters
          2.Start the master
          3.Wait untill the ENV stabilizes
          4. oc get events -A | grep unknown     

      Actual results:

      oc get events -A | grep unknow
      default                                      <unknown>   Normal    TerminationStart                             namespace/kube-system                                                            Received signal to terminate, becoming unready, but keeping serving
      default                                      <unknown>   Normal    TerminationPreShutdownHooksFinished          namespace/kube-system                                                            All pre-shutdown hooks have been finished
      default                                      <unknown>   Normal    TerminationMinimalShutdownDurationFinished   namespace/kube-system                                                            The minimal shutdown duration of 0s finished
      ....
      

      Expected results:

          All time related information is set correctly

      Additional info:

         This causes issues with external monitoring systems. Events with no timestamp will never show or push other events from the view depending on the sorting order of the timestamp. The operator of the environment has then trouble to see what is happening there. 

            akashem@redhat.com Abu H Kashem
            rhn-support-rhodain1 Roman Hodain
            Rahul Gangwar Rahul Gangwar
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: