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

nmea_status parsing throws nil pointer exception

XMLWordPrintable

    • No
    • CNF RAN Sprint 247
    • 1
    • False
    • Hide

      None

      Show
      None

      cloud event proxy log show null pointer exception 

      ime="2024-01-12T04:02:46Z" level=error msg="restored from extract metrics and events: runtime error: invalid memory address or nil pointer dereference"
      time="2024-01-12T04:02:46Z" level=error msg="failed to extract ts2phc[1705032166]:[ts2phc.0.config] ens2fx nmea_status 1 offset 0 s2"
      time="2024-01-12T04:02:46Z" level=info msg="depends on end Depending Process (key): GM\nIFace ens2f0\nClockSource GM\nProcess GM\n\n"

            [OCPBUGS-27053] nmea_status parsing throws nil pointer exception

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.16.0 security and extras update), 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/RHSA-2024:0040

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.16.0 security and extras update), 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/RHSA-2024:0040

            OpenShift Jira Bot added a comment -

            Hi aputtur@redhat.com,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi aputtur@redhat.com , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment -

            Looks like this bug is far enough along in the workflow that a code fix is ready. Customers and support need to know the backport plan. Please complete the "Target Backport Versions" field to indicate which version(s) will receive the fix.

            OpenShift Jira Bot added a comment - Looks like this bug is far enough along in the workflow that a code fix is ready. Customers and support need to know the backport plan. Please complete the " Target Backport Versions " field to indicate which version(s) will receive the fix.

              aputtur@redhat.com Aneesh Puttur
              aputtur@redhat.com Aneesh Puttur
              Hen Shay Hassid Hen Shay Hassid
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: