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

vSphere multiple in-tree test failures (non-zonal)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.13.0
    • Storage
    • None
    • No
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      Description of problem:

      In tree test failures on vSphere IPI (non-zonal)

      https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_installer/6770/pull-ci-openshift-installer-master-e2e-vsphere-ovn/1626234182315282432

      https://github.com/openshift/installer/pull/6770

      Feb 16 17:22:19.563: INFO: 
      Feb 16 17:22:19.853: INFO: skipping dumping cluster info - cluster too large
      [DeferCleanup (Each)] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy
        tear down framework | framework.go:193
      STEP: Destroying namespace "e2e-fsgroupchangepolicy-1487" for this suite. 02/16/23 17:22:19.853
      
      k8s.io/kubernetes/test/e2e/storage/vsphere.GetReadySchedulableNodeInfos()
      	k8s.io/kubernetes@v1.26.1/test/e2e/storage/vsphere/vsphere_utils.go:756 +0x30
      k8s.io/kubernetes/test/e2e/storage/drivers.(*vSphereDriver).PrepareTest.func1()
      	k8s.io/kubernetes@v1.26.1/test/e2e/storage/drivers/in_tree.go:1292 +0x19
      reflect.Value.call({0x77630c0?, 0x8f6f4f0?, 0x13?}, {0x89991da, 0x4}, {0xd2080c8, 0x0, 0x0?})
      	reflect/value.go:584 +0x8c5
      reflect.Value.Call({0x77630c0?, 0x8f6f4f0?, 0xc005c90000?}, {0xd2080c8?, 0x0?, 0xc000640840?})
      	reflect/value.go:368 +0xbc
      fail [runtime/panic.go:260]: Test Panicked: runtime error: invalid memory address or nil pointer dereference
      Ginkgo exit error 1: exit with code 1
      

            rhn-engineering-jsafrane Jan Safranek
            jcallen@redhat.com Joseph Callen
            Wei Duan Wei Duan
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: