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

openshift-tests unable to run on OCP cluster on Power platform

XMLWordPrintable

    • Important
    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      E2E test suite is getting failed with below error -
      
      Falling back to built-in suite, failed reading external test suites: unable to extract k8s-tests binary: failed extracting "/usr/bin/k8s-tests" from "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f98d9998691052cb8049f806f8c1dc9a6bac189c10c33af9addd631eedfb5528": exit status 1
      No manifest filename passed

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

      4.14

      How reproducible:

      So far with 4.14 clusters on Power

      Steps to Reproduce:

      1. Deploy 4.14 cluster on Power
      2. Run e2e test suite from - https://github.com/openshift/origin
      3. Monitor e2e
      

      Actual results:

      E2E test failed

      Expected results:

      E2E should pass

      Additional info:

      ./openshift-tests run -f ./test-suite.txt -o /tmp/conformance-parallel-out.txt
      warning: KUBE_TEST_REPO_LIST may not be set when using openshift-tests and will be ignored
      openshift-tests version: v4.1.0-6960-gd9cf51f
        Aug  9 00:48:21.959: INFO: Enabling in-tree volume drivers
      Attempting to pull tests from external binary...
      Falling back to built-in suite, failed reading external test suites: unable to extract k8s-tests binary: failed extracting "/usr/bin/k8s-tests" from "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f98d9998691052cb8049f806f8c1dc9a6bac189c10c33af9addd631eedfb5528": exit status 1
      creating a TCP service service-test with type=LoadBalancer in namespace e2e-service-lb-test-bvmbl
        Aug  9 00:48:35.424: INFO: Waiting up to 15m0s for service "service-test" to have a LoadBalancer
        Aug  9 00:48:36.272: INFO: ns/openshift-authentication route/oauth-openshift disruption/ingress-to-oauth-server connection/new started responding to GET requests over new connections
        Aug  9 00:48:36.272: INFO: ns/openshift-authentication route/oauth-openshift disruption/ingress-to-oauth-server connection/reused started responding to GET requests over reused connections
        Aug  9 00:48:36.310: INFO: ns/openshift-console route/console disruption/ingress-to-console connection/new started responding to GET requests over new connections
        Aug  9 00:48:36.310: INFO: ns/openshift-console route/console disruption/ingress-to-console connection/reused started responding to GET requests over reused connections
        Aug  9 01:04:07.507: INFO: disruption/ci-cluster-network-liveness connection/reused started responding to GET requests over reused connections
        Aug  9 01:04:07.507: INFO: disruption/ci-cluster-network-liveness connection/new started responding to GET requests over new connections
      Starting SimultaneousPodIPController
        I0809 01:04:37.551879  134117 shared_informer.go:311] Waiting for caches to sync for SimultaneousPodIPController
        Aug  9 01:04:37.558: INFO: ns/openshift-image-registry route/test-disruption-reused disruption/image-registry connection/reused started responding to GET requests over reused connections
        Aug  9 01:04:37.624: INFO: disruption/cache-kube-api connection/new started responding to GET requests over new connections
        E0809 01:04:37.719406  134117 shared_informer.go:314] unable to sync caches for SimultaneousPodIPControllerSuite run returned error: error waiting for load balancer: timed out waiting for service "service-test" to have a load balancer: timed out waiting for the condition
      disruption/kube-api connection/new producer sampler context is done
      disruption/cache-kube-api connection/reused producer sampler context is done
      disruption/oauth-api connection/new producer sampler context is done
      disruption/oauth-api connection/reused producer sampler context is done
      ERRO[0975] disruption sample failed: context canceled    auditID=464fb276-71b0-48bf-8fb4-3099ae37cedf backend=oauth-api type=reused
      disruption/cache-kube-api connection/new producer sampler context is done
      disruption/openshift-api connection/reused producer sampler context is done
      disruption/cache-openshift-api connection/reused producer sampler context is done
      ns/openshift-authentication route/oauth-openshift disruption/ingress-to-oauth-server connection/new producer sampler context is done
      ns/openshift-authentication route/oauth-openshift disruption/ingress-to-oauth-server connection/reused producer sampler context is done
      ns/openshift-console route/console disruption/ingress-to-console connection/new producer sampler context is done
      disruption/ci-cluster-network-liveness connection/reused producer sampler context is done
      disruption/ci-cluster-network-liveness connection/new producer sampler context is done
      ns/openshift-image-registry route/test-disruption-new disruption/image-registry connection/new producer sampler context is done
      ns/openshift-image-registry route/test-disruption-reused disruption/image-registry connection/reused producer sampler context is done
      ns/openshift-console route/console disruption/ingress-to-console connection/reused producer sampler context is done
      disruption/kube-api connection/reused producer sampler context is done
      disruption/openshift-api connection/new producer sampler context is done
      disruption/cache-openshift-api connection/new producer sampler context is done
      disruption/cache-oauth-api connection/reused producer sampler context is done
      
      disruption/cache-oauth-api connection/new producer sampler context is done
      Shutting down SimultaneousPodIPController
      SimultaneousPodIPController shut down
      No manifest filename passed
      error running options: error waiting for load balancer: timed out waiting for service "service-test" to have a load balancer: timed out waiting for the conditionerror: error waiting for load balancer: timed out waiting for service "service-test" to have a load balancer: timed out waiting for the condition

            pdsilva1 Pravin D Silva
            sbobade Swapnil Bobade
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: