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

Sriov network operator pod is crashing due to panic: runtime error: invalid memory address or nil pointer dereference

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • 4.12
    • Networking / SR-IOV
    • None
    • Important
    • No
    • CNF Network Sprint 253
    • 1
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-31779. The following is the description of the original issue:

      Description of problem:

      The SRIOV network operator pod is crashing and going into Crash Loop Back off state.
      Upon Checking the pod logs panic error messages can be seen :
      
      2024-04-03T17:48:33.008379552Z panic: runtime error: invalid memory address or nil pointer dereference
      2024-04-03T17:48:33.008379552Z [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x176c03f]
      Also on checking the Sriov Operator Config everything looks fine : 
      
      apiVersion: v1
      items:
      - apiVersion: sriovnetwork.openshift.io/v1
        kind: SriovOperatorConfig
        metadata:
          creationTimestamp: "2024-03-26T18:36:10Z"
          generation: 2
          name: default
          namespace: openshift-sriov-network-operator
          resourceVersion: "18324322"
          uid: 61f07940-ac92-437d-bacb-41fb1224cc34
        spec:
          disableDrain: true
          enableInjector: true
          enableOperatorWebhook: true
          logLevel: 2        

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

       

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

              sscheink@redhat.com Sebastian Scheinkman
              openshift-crt-jira-prow OpenShift Prow Bot
              Zhanqi Zhao Zhanqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: