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

pod sandbox error getting pods that have been deleted

    • Low
    • None
    • False
    • Hide

      None

      Show
      None

      (Feel free to update this bug's summary to be more specific.)
      Component Readiness has found a potential regression in the following test:

      [sig-network] pods should successfully create sandboxes by getting pod

      Significant regression detected.
      Fishers Exact probability of a regression: 99.97%.
      Test pass rate dropped from 98.45% to 88.46%.
      Overrode base stats using release 4.17

      Sample (being evaluated) Release: 4.19
      Start Time: 2025-03-17T00:00:00Z
      End Time: 2025-03-24T08:00:00Z
      Success Rate: 88.46%
      Successes: 23
      Failures: 3
      Flakes: 0

      Base (historical) Release: 4.17
      Start Time: 2024-09-01T00:00:00Z
      End Time: 2024-10-01T00:00:00Z
      Success Rate: 98.45%
      Successes: 124
      Failures: 2
      Flakes: 3

      View the test details report for additional context.

      Similar but slightly different to https://issues.redhat.com/browse/OCPBUGS-53087, again dealing with errors caused by pods deleted before multus can get to them.

      Example: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.19-e2e-agent-ha-dualstack-conformance/1903003951821754368

      namespace/e2e-deployment-8970 node/worker-0 pod/webserver-5b999469d-dlddn hmsg/fe7b4e2f40 - 6.36 seconds after deletion - firstTimestamp/2025-03-21T10:05:27Z interesting/true lastTimestamp/2025-03-21T10:05:27Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_webserver-5b999469d-dlddn_e2e-deployment-8970_4933e9f2-98e7-4f4e-8c4e-6ce983ed3cf5_0(ab970213f61e75d9d063afb458928a57ca9f675fb589cc440e91b751fe80fbbb): error adding pod e2e-deployment-8970_webserver-5b999469d-dlddn to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"ab970213f61e75d9d063afb458928a57ca9f675fb589cc440e91b751fe80fbbb" Netns:"/var/run/netns/927daf69-9769-4f93-8671-d6e2159bb0fc" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-deployment-8970;K8S_POD_NAME=webserver-5b999469d-dlddn;K8S_POD_INFRA_CONTAINER_ID=ab970213f61e75d9d063afb458928a57ca9f675fb589cc440e91b751fe80fbbb;K8S_POD_UID=4933e9f2-98e7-4f4e-8c4e-6ce983ed3cf5" Path:"" ERRORED: error configuring pod [e2e-deployment-8970/webserver-5b999469d-dlddn] networking: Multus: [e2e-deployment-8970/webserver-5b999469d-dlddn/4933e9f2-98e7-4f4e-8c4e-6ce983ed3cf5]: error waiting for pod: pods "webserver-5b999469d-dlddn" not found
      

              dosmith Douglas Smith
              rhn-engineering-dgoodwin Devan Goodwin
              Weibin Liang Weibin Liang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: