[CI]: TestNetworkInspect is flaky in windows #4322

Activity

1. Shubhranshu153

   added

   kind/unconfirmed-bug-claimUnconfirmed bug claimUnconfirmed bug claim

   area/cie.g., CI failuree.g., CI failure

   on Jun 17, 2025
2. apostasie commented on Jun 17, 2025

   

   apostasie

   on Jun 17, 2025

   Contributor

   More actions

   @Shubhranshu153 can you add the log output? + the link to the build that failed?
3. apostasie commented on Jun 17, 2025

   

   apostasie

   on Jun 17, 2025

   Contributor

   More actions

   eg:

   • linking the PR(s) that failed with this helps evaluating how prevalent this is
   • concrete log output avoids linking unrelated issues that may affect the same test
     :)
4. apostasie commented on Jun 23, 2025

   

   apostasie

   on Jun 23, 2025

   Contributor

   More actions

             +------------------------------------------------------------------------------------------------------------+
             | ➡️      | ⚙️ C:\Users\runneradmin\go\bin\nerdctl.exe create --name testnetworkinspect-verify-that-only-act |
             |         | ive-containers-appear-in-the-0a54a379 --network testnetworkinspect-verify-that-only-active-conta |
             |         | iners-appear-in-the-844e8a21 registry.k8s.io/e2e-test-images/nginx:1.14-2                        |
             +------------------------------------------------------------------------------------------------------------+
             |         | 🚫 command returned a non-zero exit code                                                         |
             +------------------------------------------------------------------------------------------------------------+
             |         | ⚠️ 1                                                                                             |
             +------------------------------------------------------------------------------------------------------------+
             |         | 🟠 time="2025-06-22T21:52:24Z" level=warning msg="default network named \"nat\" does not have an |
             |         |  internal nerdctl ID or nerdctl-managed config file, it was most likely NOT created by nerdctl"  |
             |         | time="2025-06-22T21:52:24Z" level=warning msg="default network named \"nat\" does not have an in |
             |         | ternal nerdctl ID or nerdctl-managed config file, it was most likely NOT created by nerdctl"     |
             |         | time="2025-06-22T21:52:25Z" level=warning msg="networking setup error has occurred" error="plugi |
             |         | n type=\"nat\" failed (add): hcnCreateNetwork failed in Win32: The object already exists. (0x139 |
             |         | 2) {\"Success\":false,\"Error\":\"The object already exists. \",\"ErrorCode\":2147947410}"       |
             |         | time="2025-06-22T21:52:25Z" level=warning msg="default network named \"nat\" does not have an in |
             |         | ternal nerdctl ID or nerdctl-managed config file, it was most likely NOT created by nerdctl"     |
             |         | time="2025-06-22T21:52:25Z" level=fatal msg="plugin type=\"nat\" failed (add): hcnCreateNetwork  |
             |         | failed in Win32: The object already exists. (0x1392) {\"Success\":false,\"Error\":\"The object a |
             |         | lready exists. \",\"ErrorCode\":2147947410}"        
   
   
5. apostasie commented on Jun 23, 2025

   

   apostasie

   on Jun 23, 2025

   Contributor

   More actions

   Wondering if windows network create is asynchronous...
6. apostasie commented on Jul 2, 2025

   

   apostasie

   on Jul 2, 2025

   Contributor

   More actions

   https://github.com/microsoft/windows-container-networking/blob/master/common/core/network.go#L145

   So, the windows CNI plugin will create the network if it does not exist during CmdAdd (this is just plain wrong).

   https://github.com/microsoft/windows-container-networking/blob/master/common/core/network.go#L399-L421

   Why is it not finding the existing network (GetNetworkByName)? Unclear. Maybe hcnEnumerateNetworks is somehow faulty.
7. apostasie commented on Jul 2, 2025

   

   apostasie

   on Jul 2, 2025

   Contributor

   More actions

   Also note that reading through that stuff, most of it does not seem safe to use concurrently...
8. AkihiroSuda

   added a commit that references this issue on Oct 27, 2026

   test(windows): do not run TestNetworkInspectWithContainers in parallel

   ...

   d42c075
9. AkihiroSuda

   closed this as completedin #5269on Oct 27, 2026