fix(monitor): prevent sample loss during disruption sampler shutdown #30771

mgencur · 2026-02-10T08:21:59Z

Add graceful shutdown logic to ensure all samples are processed before the disruption sampler terminates. Previously, samples could be lost when the context was cancelled, as the consumer would exit immediately without draining the remaining queue.

Changes:

Add 30-second timeout when waiting for consumer to finish
Implement contextCancelled flag to track cancellation state
Continue processing remaining samples after context cancellation
Remove early returns that would skip sample processing
Ensure current sample completes even if context is cancelled

This prevents the "not finished writing all samples" error and ensures data integrity during shutdown.

The error was spotted in multiple runs for Hypershift on AWS, example: 2020875118166675456

Root cause analysis:

Producer goroutine (produceSamples, line 449) creates samples on each tick and launches goroutines to check connections
Consumer goroutine (consumeSamples, line 450) processes samples from the queue
When the context is cancelled, both goroutines receive the signal simultaneously

The problematic sequence:

  Time T:   produceSamples creates a new sample (line 538)
  Time T+1: produceSamples adds it to activeSamplers queue (line 709)
  Time T+2: produceSamples launches CheckConnection goroutine (line 539-558)
  Time T+3: Context cancelled (ctx.Done())
  Time T+4: consumeSamples sees ctx.Done() in select statement (line 587-590 or 597-598 or 605-607)
  Time T+5: consumeSamples returns immediately WITHOUT processing the last sample
  Time T+6: consumeSamples closes consumerDoneCh (deferred at line 570)
  Time T+7: RunEndpointMonitoring wakes up, finds 1 sample still in activeSamplers
  Time T+8: Error: "not finished writing all samples (1 remaining)"

Add graceful shutdown logic to ensure all samples are processed before the disruption sampler terminates. Previously, samples could be lost when the context was cancelled, as the consumer would exit immediately without draining the remaining queue. Changes: - Add 30-second timeout when waiting for consumer to finish - Implement contextCancelled flag to track cancellation state - Continue processing remaining samples after context cancellation - Remove early returns that would skip sample processing - Ensure current sample completes even if context is cancelled This prevents the "not finished writing all samples" error and ensures data integrity during shutdown.

openshift-ci-robot · 2026-02-10T08:22:02Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

mgencur · 2026-02-10T08:24:12Z

Tested the solution against my dev cluster:

ᐅ openshift-tests run-monitor --monitor pod-network-avalibility
I0210 09:13:40.663198 2786585 factory.go:195] Registered Plugin "containerd"
  I0210 09:13:40.884478 2786585 binary.go:77] Found 8507 test specs
  I0210 09:13:40.885861 2786585 binary.go:94] 1057 test specs remain, after filtering out k8s
openshift-tests v4.1.0-10518-g1e1237d
Starting the monitor.
INFO[0000]   Preparing pod-network-avalibility for Network / ovn-kubernetes 
INFO[0001] Using target cluster release image            release_image="quay.io/openshift-release-dev/ocp-release-nightly@sha256:ec0824c60a1460dcaa2b4f2c261594115b0dc31a4b6b2a286bb8f1ae4cba32ed"
INFO[0001] payload image reported by CV: quay.io/openshift-release-dev/ocp-release-nightly@sha256:ec0824c60a1460dcaa2b4f2c261594115b0dc31a4b6b2a286bb8f1ae4cba32ed 
INFO[0001] Using target cluster pull-secrets for registry auth 
INFO[0001] Run image extract for release image "quay.io/openshift-release-dev/ocp-release-nightly@sha256:ec0824c60a1460dcaa2b4f2c261594115b0dc31a4b6b2a286bb8f1ae4cba32ed" and src "/release-manifests/image-references" 
INFO[0250] Completed image extract for release image "quay.io/openshift-release-dev/ocp-release-nightly@sha256:ec0824c60a1460dcaa2b4f2c261594115b0dc31a4b6b2a286bb8f1ae4cba32ed" in 4m8.745468289s 
openshift-tests image pull spec is quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:e3bcb9d253dacd2efba9c9986f00130a24c00b82807582eb64a764cee11d7ec5
  I0210 09:17:55.692591 2786585 monitortest.go:129] Starting deployment: pod-network-to-pod-network-disruption-poller
  I0210 09:17:56.081272 2786585 monitortest.go:136] Starting deployment: pod-network-to-host-network-disruption-poller
  I0210 09:17:56.486073 2786585 monitortest.go:143] Starting deployment: host-network-to-pod-network-disruption-poller
  I0210 09:17:56.942271 2786585 monitortest.go:150] Starting deployment: host-network-to-host-network-disruption-poller
  I0210 09:17:57.301432 2786585 monitortest.go:157] Starting deployment: pod-network-disruption-target
  I0210 09:17:58.091353 2786585 monitortest.go:170] Starting deployment: host-network-disruption-target
  I0210 09:18:52.096002 2786585 monitortest.go:188] Starting deployment: pod-network-to-service-disruption-poller
  I0210 09:19:22.421374 2786585 monitortest.go:188] Starting deployment: host-network-to-service-disruption-poller
INFO[0341]   Starting pod-network-avalibility for Network / ovn-kubernetes 
All monitor tests started.
Monitor started, waiting for ctrl+C to stop...
^CInterrupted, terminating
Monitor shutting down, this may take up to twenty minutes...
Shutting down the monitor
Collecting data.
INFO[0418] Starting CollectData for all monitor tests   
INFO[0418]   Starting CollectData for [Monitor:pod-network-avalibility][Jira:"Network / ovn-kubernetes"] monitor test pod-network-avalibility collection 
INFO[0455]   Finished CollectData for [Monitor:pod-network-avalibility][Jira:"Network / ovn-kubernetes"] monitor test pod-network-avalibility collection 
INFO[0455] Finished CollectData for all monitor tests   
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:40Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:40Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:40Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:40Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:40Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:40Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-new-connections","connection":"new","disruption":"pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-new-connections connection/new disruption/pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-pod-reused-connections","connection":"reused","disruption":"pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-pod-reused-connections connection/reused disruption/pod-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-new-connections","connection":"new","disruption":"pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-new-connections connection/new disruption/pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-host-reused-connections","connection":"reused","disruption":"pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-host-reused-connections connection/reused disruption/pod-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.133.0.21 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.132.0.25 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-new-connections","connection":"new","disruption":"host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-new-connections connection/new disruption/host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-pod-reused-connections","connection":"reused","disruption":"host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-pod-reused-connections connection/reused disruption/host-to-pod-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.134.0.18 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-142-23.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:49Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-136-89.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:50Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-136-89.ec2.internal-endpoint-10.0.136.89 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:48Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-134-229.ec2.internal-endpoint-10.0.134.229 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-new-connections","connection":"new","disruption":"host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-new-connections connection/new disruption/host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-host-reused-connections","connection":"reused","disruption":"host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-host-reused-connections connection/reused disruption/host-to-host-from-node-ip-10-0-134-229.ec2.internal-to-node-ip-10-0-142-23.ec2.internal-endpoint-10.0.142.23 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:47Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-service-new-connections","connection":"new","disruption":"pod-to-service-to-service-from-node-ip-10-0-134-229.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-service-new-connections connection/new disruption/pod-to-service-to-service-from-node-ip-10-0-134-229.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:53Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-service-reused-connections","connection":"reused","disruption":"pod-to-service-to-service-from-node-ip-10-0-134-229.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-service-reused-connections connection/reused disruption/pod-to-service-to-service-from-node-ip-10-0-134-229.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:53Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-service-new-connections","connection":"new","disruption":"pod-to-service-to-service-from-node-ip-10-0-136-89.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-service-new-connections connection/new disruption/pod-to-service-to-service-from-node-ip-10-0-136-89.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:54Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-service-reused-connections","connection":"reused","disruption":"pod-to-service-to-service-from-node-ip-10-0-136-89.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-service-reused-connections connection/reused disruption/pod-to-service-to-service-from-node-ip-10-0-136-89.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:54Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-service-new-connections","connection":"new","disruption":"pod-to-service-to-service-from-node-ip-10-0-142-23.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-service-new-connections connection/new disruption/pod-to-service-to-service-from-node-ip-10-0-142-23.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:54Z","to":"2026-02-10T08:20:40Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"pod-to-service-reused-connections","connection":"reused","disruption":"pod-to-service-to-service-from-node-ip-10-0-142-23.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/pod-to-service-reused-connections connection/reused disruption/pod-to-service-to-service-from-node-ip-10-0-142-23.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:18:54Z","to":"2026-02-10T08:20:40Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-service-new-connections","connection":"new","disruption":"host-to-service-to-service-from-node-ip-10-0-136-89.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-service-new-connections connection/new disruption/host-to-service-to-service-from-node-ip-10-0-136-89.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:19:23Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-service-reused-connections","connection":"reused","disruption":"host-to-service-to-service-from-node-ip-10-0-136-89.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-service-reused-connections connection/reused disruption/host-to-service-to-service-from-node-ip-10-0-136-89.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:19:23Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-service-new-connections","connection":"new","disruption":"host-to-service-to-service-from-node-ip-10-0-142-23.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-service-new-connections connection/new disruption/host-to-service-to-service-from-node-ip-10-0-142-23.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:19:23Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-service-reused-connections","connection":"reused","disruption":"host-to-service-to-service-from-node-ip-10-0-142-23.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-service-reused-connections connection/reused disruption/host-to-service-to-service-from-node-ip-10-0-142-23.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:19:23Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-service-new-connections","connection":"new","disruption":"host-to-service-to-service-from-node-ip-10-0-134-229.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-service-new-connections connection/new disruption/host-to-service-to-service-from-node-ip-10-0-134-229.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over new connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:19:23Z","to":"2026-02-10T08:20:39Z"}
{"level":"Info","source":"Disruption","locator":{"type":"Disruption","keys":{"backend-disruption-name":"host-to-service-reused-connections","connection":"reused","disruption":"host-to-service-to-service-from-node-ip-10-0-134-229.ec2.internal-to-clusterIP-172.31.57.192"}},"message":{"reason":"DisruptionEnded","cause":"","humanMessage":"backend-disruption-name/host-to-service-reused-connections connection/reused disruption/host-to-service-to-service-from-node-ip-10-0-134-229.ec2.internal-to-clusterIP-172.31.57.192 started responding to GET requests over reused connections","annotations":{"reason":"DisruptionEnded"}},"from":"2026-02-10T08:19:23Z","to":"2026-02-10T08:20:39Z"}
Computing intervals.
Evaluating tests.
Cleaning up.
INFO[0455] beginning cleanup                             monitorTest=pod-network-avalibility
  I0210 09:22:01.930335 2786585 monitortest.go:313] Deleting namespace: e2e-pod-network-disruption-test-c2lzg took 45.21 seconds
Serializing results.
Writing to storage.
  m.startTime = 2026-02-10 09:13:40.891588795 +0100 CET m=+0.276442521
  m.stopTime  = 2026-02-10 09:21:16.435169991 +0100 CET m=+455.820023737
Processing monitorTest: pod-network-avalibility
  finalIntervals size = 84
  first interval time: From = 2026-02-10 09:18:47 +0100 CET; To = 2026-02-10 09:20:39 +0100 CET
  last interval time: From = 2026-02-10 09:19:23 +0100 CET; To = 2026-02-10 09:20:39 +0100 CET
Writing junits.
Writing JUnit report to e2e-monitor-tests_.xml

mgencur · 2026-02-10T08:31:39Z

/assign @xueqzhan

Please.

mgencur · 2026-02-10T11:13:35Z

/test ci/prow/okd-scos-images

mgencur · 2026-02-10T11:13:57Z

/test okd-scos-images

openshift-ci · 2026-02-10T11:32:00Z

@mgencur: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-images	`7e97475`	link	true	`/test okd-scos-images`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

xueqzhan · 2026-02-10T13:50:46Z

/lgtm

openshift-ci · 2026-02-10T13:56:41Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mgencur, xueqzhan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [xueqzhan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

mgencur · 2026-02-10T14:04:30Z

Seems there is a known issue for the okd-scos-images failing check: slack thread

openshift-ci bot requested review from deads2k and sjenning February 10, 2026 08:26

openshift-ci bot assigned xueqzhan Feb 10, 2026

mgencur mentioned this pull request Feb 10, 2026

[WIP] CNTRLPLANE-2647: Configure Calico CNI periodic job on 4.21 openshift/release#73985

Open

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2026

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(monitor): prevent sample loss during disruption sampler shutdown #30771

fix(monitor): prevent sample loss during disruption sampler shutdown #30771

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

openshift-ci-robot commented Feb 10, 2026

Uh oh!

mgencur commented Feb 10, 2026 •

edited

Loading

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

openshift-ci bot commented Feb 10, 2026

Uh oh!

xueqzhan commented Feb 10, 2026

Uh oh!

openshift-ci bot commented Feb 10, 2026

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

fix(monitor): prevent sample loss during disruption sampler shutdown #30771

Are you sure you want to change the base?

fix(monitor): prevent sample loss during disruption sampler shutdown #30771

Uh oh!

Conversation

mgencur commented Feb 10, 2026

Uh oh!

openshift-ci-robot commented Feb 10, 2026

Uh oh!

mgencur commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

openshift-ci bot commented Feb 10, 2026

Uh oh!

xueqzhan commented Feb 10, 2026

Uh oh!

openshift-ci bot commented Feb 10, 2026

Uh oh!

mgencur commented Feb 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

mgencur commented Feb 10, 2026 •

edited

Loading