Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-2997

failure in test case "[sig-network] pods should successfully create sandboxes by other" - requests timing out

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Minor
    • None
    • None
    • None
    • 0
    • 0

    Description

      job link

      must-gather

      e2e log that mentions
      something about timing out due to system load:

      {  1 failures to create the sandbox

ns/openshift-monitoring pod/node-exporter-tv2fp node/ci-op-g20i7x0v-5cb9e-v4654-worker-centralus3-4njql - never deleted - reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = Kubelet may be retrying requests that are timing out in CRI-O due to system load: context deadline exceeded: error reserving pod name k8s_node-exporter-tv2fp_openshift-monitoring_c1ede183-2825-4441-bf11-6c92cb377bf1_0 for id b3efb9ff3d20ad6d85a198ba01d75efd8ec889f9375838d8e9d9ca6d23571164: name is reserved}​

      link to this job's testgrid for reference.

       

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. SDN-2995 console operator degraded from "All is Well" to "RouteHealthDegraded"

          • 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. SDN-3007 failure in test case "[sig-cluster-lifecycle] should not see excessive Back-off restarting failed containers"

          • 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
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-480 Sprint-220 SDN embedding work - Arkadeep

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-523 Sprint-221 SDN embedding work - Arkadeep

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CFE-540 Sprint-222 SDN embedding work - Arkadeep

          • 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

          Activity

            People

              rh-ee-arsen Arkadeep Sen
              jluhrsen Jamo Luhrsen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: