← Problem Library
Security L5 SECURITY-1453 · 10 min

An OPA bundle signature verifies and the sidecar still serves stale decisions because it weak-compares the ETag and treats the new bundle as semantically identical

Integrity is fine, but the bundle cache keeps the older policy because the sidecar uses a weak ETag comparison.

SecurityPlatform ReliabilityLevel 5Pro10 min
Scenario

Policy changes deploy successfully and one sidecar keeps enforcing the old decisions until restart.

What to check first
  • Identify the primary failure signal in the The Bundle Was New and the Cache Decided It Felt Familiar Enough to Ignore scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Compare cache comparison rules before forcing full bundle redownloads.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.