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

4.14 Regressions in periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-remote-libvirt-ppc64le - Node Enters NotReady State

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Blocker
    • 4.14
    • 4.13.z, 4.14
    • Multi-Arch
    • None
    • Important
    • Yes
    • Multi-Arch Sprint 239, Multi-Arch Sprint 240
    • 2
    • Approved
    • ppc64le
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:
      Component Readiness is detecting a regression for ovn no-upgrade ppc64le libvirt standard

      Looking at failed jobs for periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-remote-libvirt-ppc64le there are an increasing number with failures > 100 since 6/23.

      Those failures all seem to indicate the install did not complete successfully even though the cluster does report initialized.

      time="2023-06-17T05:22:51Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operators authentication, console, image-registry, insights, monitoring are not available"
time="2023-06-17T05:22:51Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operators authentication, console, image-registry, insights, monitoring are not available"
time="2023-06-17T05:23:36Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operators authentication, console, insights, monitoring are not available"
time="2023-06-17T05:25:21Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operators authentication, console, insights are not available"
time="2023-06-17T05:25:21Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operators authentication, console, insights are not available"
time="2023-06-17T05:25:51Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operators authentication, console are not available"
time="2023-06-17T05:26:21Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operator authentication is not available"
time="2023-06-17T05:28:39Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operator authentication is not available"
time="2023-06-17T05:29:21Z" level=debug msg="Cluster is initialized"
 

      Looker Studio (scroll down for graph) shows that a sampling of test failures that we see in those failed runs has been sporadic but increased since mid june or so.

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

       

      Expected results:

       

      Additional info:

       

      Attachments

        Issue Links

          depends on

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-16715 community-e2e-images missing manifest listed images

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-17427 http://quay.io/openshift/community-e2e-images:e2e-7-registry-k8s-io-e2e-test-images-busybox-1-29-4-4zE9mRvED4RQoUxQ broken on ppc64le

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-16619 4.14 Regressions in periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-remote-libvirt-s390x - TLS Handshake Timeout

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          Web Link 4.14 Periodics Adjustment

          Web Link FDP / OVS Ticket

          Activity

            People

              shgokul Shilpa Gokul
              rh-ee-fbabcock Forrest Babcock
              Doug Slavens Doug Slavens
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: