Sandbox Handbook·2 min read

Scenario 6: checkout-service-pod — Verification Failed

CPU contention from a noisy neighbor — the fix runs, but verification correctly reports NO_IMPROVEMENT.

Latency degraded sharply with no traffic increase — CPU contention from a noisy neighbor on the shared Kubernetes node. A human approves migrating the pod, but it lands on another node in the same contended rack.

Steps to test

  1. Open INC0000006.
  2. Steps 4–7: node_cpu_usage_percent steps up with no matching traffic change.
  3. Steps 10–12: hypothesis at 0.70 confidence, approved.
  4. Steps 13–14: pod migration executed live — verification outcome NO_IMPROVEMENT (error rate 40% to 38%, essentially unchanged).
Outcome: compare this to Scenario 1 — a completed remediation step doesn't always mean success.
Back to Sandbox Handbook overview
← PreviousScenario 5: notification-dispatch-svc — RCA RefinedNext →Scenario 7: dns-resolver-primary — Blocked, No Telemetry