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

nil pointer error in e2e DNS tests

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.18.0
    • Networking / DNS
    • None
    • 1
    • NE Sprint 260, NE Sprint 261
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • In Progress

      Description of problem:

          panic: runtime error: invalid memory address or nil pointer dereference [recovered]
          panic: runtime error: invalid memory address or nil pointer dereference
      [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x1a774eb]goroutine 11358 [running]:
      testing.tRunner.func1.2({0x1d3d600, 0x3428a50})
          /usr/lib/golang/src/testing/testing.go:1631 +0x24a
      testing.tRunner.func1()
          /usr/lib/golang/src/testing/testing.go:1634 +0x377
      panic({0x1d3d600?, 0x3428a50?})
          /usr/lib/golang/src/runtime/panic.go:770 +0x132
      github.com/openshift/cluster-ingress-operator/test/e2e.updateDNSConfig(...)
          /go/src/github.com/openshift/cluster-ingress-operator/test/e2e/dns_ingressdegrade_test.go:89
      github.com/openshift/cluster-ingress-operator/test/e2e.TestIngressStatus(0xc000511380)
          /go/src/github.com/openshift/cluster-ingress-operator/test/e2e/dns_ingressdegrade_test.go:53 +0x34b
      testing.tRunner(0xc000511380, 0x218c9f8)
          /usr/lib/golang/src/testing/testing.go:1689 +0xfb
      created by testing.(*T).Run in goroutine 11200
          /usr/lib/golang/src/testing/testing.go:1742 +0x390
      FAIL    github.com/openshift/cluster-ingress-operator/test/e2e    1612.553s
      FAIL
      make: *** [Makefile:56: test-e2e] Error 1

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

          master

      How reproducible:

          run the cluster-ingress-operator e2e tests against the OpenStack platform.

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          the nil pointer error

      Expected results:

          no error

      Additional info:

          

              emacchi@redhat.com Emilien Macchi
              emacchi@redhat.com Emilien Macchi
              Melvin Joseph Melvin Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: