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

e2e failures: [sig-arch][Jira:"kube-apiserver"] TLS artifact conformance tests failing - metadata, registration, and certificate data collection

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.21.0
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • ppc64le
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      The below three testcases are failing on IBM Power Architecture(ppc64le). This only started happening during the latest merges, we are also seeing this on AWS with 4.21.
      
      [sig-arch][Late][Jira:"kube-apiserver"] all registered tls artifacts must have no metadata violation regressions [Suite:openshift/conformance/parallel]
      [sig-arch][Late][Jira:"kube-apiserver"] all tls artifacts must be registered [Suite:openshift/conformance/parallel]
      [sig-arch][Late][Jira:"kube-apiserver"] collect certificate data [Suite:openshift/conformance/parallel]

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

          

      How reproducible:

          Continuously failing on normal cluster, IPSec encryption enabled cluster, VLAN configured cluster.

      Steps to Reproduce:

          1. git clone -b release-4.21 https://github.com/openshift/origin.git     
          2. cd origin
          3. make build
          4. ./openshift-tests run -f tests.txt -o output.txt
          

      Actual results:

      The testcases are failing
      Blocking test failures:        
      * [sig-arch][Late][Jira:"kube-apiserver"] all registered tls artifacts must have no metadata violation regressions [Suite:openshift/conformance/parallel]
      * [sig-arch][Late][Jira:"kube-apiserver"] all tls artifacts must be registered [Suite:openshift/conformance/parallel]
      * [sig-arch][Late][Jira:"kube-apiserver"] collect certificate data [Suite:openshift/conformance/parallel]

      Expected results:

          The testcases should pass.

      Additional info:

      Attaching the logs of the testrun on ppc64le arch: https://drive.google.com/file/d/1Pj7HoV3fNtO6-gV0ZEanUoe1d0SJrwa7/view?usp=sharing
      
      The logs show,
       [sig-arch][Late][Jira:"kube-apiserver"] collect certificate data
        github.com/openshift/origin/test/extended/operators/certs.go:142
      Ginkgo detected an issue with your spec structure
      github.com/openshift/origin/test/extended/util/client.go:183
        It looks like you are trying to add a [BeforeEach] node
        to the Ginkgo spec tree in a leaf node after the specs started running.
      
        To enable randomization and parallelization Ginkgo requires the spec tree
        to be fully constructed up front.  In practice, this means that you can
        only create nodes like [BeforeEach] at the top-level or within the
        body of a Describe, Context, or When.
      
        Learn more at:
        http://onsi.github.io/ginkgo/#mental-model-how-ginkgo-traverses-the-spec-hierarchy

              afogarol@redhat.com Angela Fogarolli
              rh-ee-jdarapu Jeevan Darapu
              None
              None
              Ke Wang Ke Wang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: