Skip to content

Scheduled E2E

Scheduled E2E #795

Triggered via schedule February 14, 2025 16:45
Status Failure
Total duration 22m 47s
Artifacts

scheduled-e2e.yaml

on: schedule
Matrix: Chart Upgrade E2E
Matrix: Cilium Chaining E2E
Matrix: Cyclonus Network Policy E2E
Matrix: Installation Compatibility Test
Matrix: Iptables VPC NAT Gateway E2E
Matrix: Kubernetes Conformance E2E
Matrix: Kubernetes Network Policy E2E
Matrix: Kube-OVN Conformance E2E
Matrix: Kube-OVN HA E2E
Matrix: Kube-OVN IC Conformance E2E
Matrix: Kube-OVN Submariner Conformance E2E
Matrix: Kubevirt VM E2E
Matrix: LB Service E2E
Matrix: Disable Network Policy Test
Matrix: Disable OVN LB Test
Matrix: OVN VPC NAT Gateway E2E
Matrix: Underlay Logical Gateway Installation Test
Matrix: Webhook E2E
Fit to window
Zoom out
Zoom in

Annotations

122 errors and 57 warnings
Kubevirt VM E2E (release-1.12-mc)
Process completed with exit code 1.
Kube-OVN Conformance E2E (release-1.12-mc, dual, overlay)
Process completed with exit code 1.
Kube-OVN Conformance E2E (release-1.12-mc, dual, underlay)
Process completed with exit code 1.
Kube-OVN Conformance E2E (release-1.12-mc, ipv4, overlay)
Process completed with exit code 1.
LB Service E2E (release-1.12-mc)
Process completed with exit code 1.
Kube-OVN Conformance E2E (release-1.12-mc, ipv6, overlay)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, true, true, ipv6)
Process completed with exit code 1.
Kube-OVN Conformance E2E (release-1.12-mc, ipv6, underlay)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, false, false, ipv4)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, true, false, ipv4)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, false, true, ipv6)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, true, false, dual)
Process completed with exit code 1.
Kube-OVN Conformance E2E (release-1.12-mc, ipv4, underlay)
Process completed with exit code 1.
OVN VPC NAT Gateway E2E (release-1.12-mc)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, false, true, ipv4)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, true, true, dual)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, true, true, ipv4)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, true, false, ipv6)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, false, false, ipv6)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, false, true, dual)
Process completed with exit code 1.
Kube-OVN HA E2E (release-1.12-mc, false, false, dual)
Process completed with exit code 1.
Installation Compatibility Test (master)
Process completed with exit code 2.
Chart Upgrade E2E (release-1.11 => release-1.12)
Process completed with exit code 2.
Chart Upgrade E2E (release-1.11 => master)
Process completed with exit code 2.
Chart Upgrade E2E (release-1.11 => release-1.13)
Process completed with exit code 2.
Kube-OVN IC Conformance E2E (master)
System.IO.IOException: No space left on device : '/home/runner/runners/2.322.0/_diag/Worker_20250214-164524-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) System.IO.IOException: No space left on device : '/home/runner/runners/2.322.0/_diag/Worker_20250214-164524-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Common.Tracing.Error(Exception exception) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/runners/2.322.0/_diag/Worker_20250214-164524-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at System.Diagnostics.TraceSource.Flush() at GitHub.Runner.Common.Tracing.Dispose(Boolean disposing) at GitHub.Runner.Common.Tracing.Dispose() at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing) at GitHub.Runner.Common.TraceManager.Dispose() at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing) at GitHub.Runner.Common.HostContext.Dispose() at GitHub.Runner.Worker.Program.Main(String[] args)
Cyclonus Network Policy E2E (release-1.13, ipv6)
Process completed with exit code 2.
Disable OVN LB Test (release-1.12)
Process completed with exit code 2.
LB Service E2E (release-1.11): test/e2e/lb-svc/e2e_test.go#L248
It 02/14/25 16:50:44.092
LB Service E2E (release-1.11): test/e2e/lb-svc/e2e_test.go#L348
It 02/14/25 16:51:40.521
LB Service E2E (release-1.11)
Process completed with exit code 2.
Disable OVN LB Test (release-1.13)
Process completed with exit code 2.
Cyclonus Network Policy E2E (release-1.12, dual)
Process completed with exit code 2.
Disable Network Policy Test (release-1.12)
Process completed with exit code 2.
Cyclonus Network Policy E2E (release-1.13, dual)
Process completed with exit code 2.
Cilium Chaining E2E (release-1.11)
Process completed with exit code 2.
Cyclonus Network Policy E2E (release-1.12, ipv6)
Process completed with exit code 2.
Disable Network Policy Test (release-1.13)
Process completed with exit code 2.
Cyclonus Network Policy E2E (release-1.13, ipv4)
Process completed with exit code 2.
Cyclonus Network Policy E2E (release-1.12, ipv4)
Process completed with exit code 2.
Underlay Logical Gateway Installation Test (release-1.13)
Process completed with exit code 2.
Underlay Logical Gateway Installation Test (release-1.12)
Process completed with exit code 2.
Kubernetes Network Policy E2E (release-1.12, dual)
Process completed with exit code 2.
Kubevirt VM E2E (release-1.13)
Process completed with exit code 2.
Kubernetes Network Policy E2E (release-1.13, ipv4)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.12, ipv6, underlay)
Process completed with exit code 2.
Kubernetes Network Policy E2E (release-1.12, ipv6)
Process completed with exit code 2.
Kubernetes Network Policy E2E (release-1.12, ipv4)
Process completed with exit code 2.
Chart Upgrade E2E (release-1.12 => release-1.13)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.12, dual, underlay)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.12, ipv6, overlay)
Process completed with exit code 2.
Chart Upgrade E2E (release-1.12 => master)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.12, dual, overlay)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.12, dual, overlay)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.13, ipv4, overlay)
Process completed with exit code 2.
Installation Compatibility Test (release-1.12)
Process completed with exit code 2.
Kubernetes Network Policy E2E (release-1.13, ipv6)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.13, dual, overlay)
Process completed with exit code 2.
Chart Upgrade E2E (release-1.13 => master)
Process completed with exit code 2.
OVN VPC NAT Gateway E2E (release-1.12)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.12, ipv4, overlay)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.13, ipv4, underlay)
Process completed with exit code 2.
Kubevirt VM E2E (release-1.12)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.12, ipv4, underlay)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.12, dual, underlay)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.13, ipv6, overlay)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.13, dual, underlay)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.13, ipv6, underlay)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.13, ipv4, overlay)
Process completed with exit code 2.
OVN VPC NAT Gateway E2E (release-1.13)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.13, ipv6, underlay)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.12, ipv6, overlay)
Process completed with exit code 2.
Webhook E2E (release-1.12)
Process completed with exit code 2.
LB Service E2E (release-1.13)
Process completed with exit code 2.
Webhook E2E (release-1.13)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.12, ipv4, overlay)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.12, ipv4, underlay)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.13, dual, overlay)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.12, ipv6, underlay)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.13, ipv4, underlay)
Process completed with exit code 2.
Kube-OVN Conformance E2E (release-1.13, dual, underlay)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.13, ipv6, overlay)
Process completed with exit code 2.
Installation Compatibility Test (release-1.13)
Process completed with exit code 2.
LB Service E2E (release-1.12)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, false, true, ipv4)
Process completed with exit code 2.
Kube-OVN Submariner Conformance E2E (release-1.13)
Process completed with exit code 2.
Iptables VPC NAT Gateway E2E (release-1.13)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, false, false, dual)
Process completed with exit code 2.
Kubernetes Network Policy E2E (release-1.13, dual)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, true, false, ipv4)
Process completed with exit code 2.
Iptables VPC NAT Gateway E2E (release-1.12)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, false, true, ipv6)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, false, true, dual)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, false, false, ipv4)
Process completed with exit code 2.
Kube-OVN Submariner Conformance E2E (release-1.12)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, true, false, ipv4)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, false, true, ipv6)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, true, true, ipv4)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, true, true, dual)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, true, true, ipv6)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, false, false, ipv6)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, false, false, ipv6)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, false, true, ipv4)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, true, false, dual)
Process completed with exit code 2.
Kube-OVN IC Conformance E2E (release-1.13)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, false, false, dual)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, true, false, ipv6)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, true, false, dual)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, false, false, ipv4)
Process completed with exit code 2.
Kube-OVN IC Conformance E2E (release-1.12)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, false, true, dual)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, true, false, ipv6)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, true, true, ipv4)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.12, true, true, ipv6)
Process completed with exit code 2.
Kubernetes Conformance E2E (release-1.11, dual, overlay)
Process completed with exit code 2.
Kube-OVN HA E2E (release-1.13, true, true, dual)
Process completed with exit code 2.
Cilium Chaining E2E (release-1.13)
Process completed with exit code 2.
Cilium Chaining E2E (release-1.12)
Process completed with exit code 2.
OVN VPC NAT Gateway E2E (master)
The job running on runner GitHub Actions 317 has exceeded the maximum execution time of 10 minutes.
OVN VPC NAT Gateway E2E (master)
The operation was canceled.
Kubernetes Conformance E2E (master, ipv4, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
LB Service E2E (master)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (master, ipv6, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (master, ipv6, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (release-1.11, ipv6, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (master, ipv4, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (release-1.11, ipv6, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (release-1.11, ipv4, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, true, false, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, false, false, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, false, true, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, true, false, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, true, true, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, false, true, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, true, true, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (release-1.11, ipv4, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, false, false, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, true, true, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, false, false, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, false, true, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, false, true, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, false, true, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, false, false, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, true, false, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, false, true, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, true, false, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, true, true, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, false, false, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, true, false, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, true, false, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, false, false, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (master, true, true, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN HA E2E (release-1.11, true, true, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (master, dual, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (master, dual, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Conformance E2E (release-1.11, dual, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubevirt VM E2E (master)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Iptables VPC NAT Gateway E2E (master)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN IC Conformance E2E (release-1.11)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (release-1.11, ipv6, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (release-1.11, ipv4, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (release-1.11, ipv4, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (release-1.11, dual, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (release-1.11, dual, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (master, ipv6, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (master, ipv4, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (master, ipv4, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (master, ipv6, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Network Policy E2E (master, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (release-1.11, ipv6, overlay)
Failed to save: Failed to CreateCacheEntry: Failed to make request after 5 attempts: Request timeout: /twirp/github.actions.results.api.v1.CacheService/CreateCacheEntry
Kubernetes Network Policy E2E (master, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Network Policy E2E (master, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Network Policy E2E (release-1.11, ipv4)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (master, dual, overlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kube-OVN Conformance E2E (master, dual, underlay)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Network Policy E2E (release-1.11, dual)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Kubernetes Network Policy E2E (release-1.11, ipv6)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists