Scenario
A deny rule that should be gone continues firing after a successful policy bundle rollout.
An OPA bundle rollout succeeds and one deny rule still fires because removed package paths fall back to the last good policy on partial sync
The new bundle is mostly present, but a removed path still resolves to the previous package under partial load semantics.
What to check first
- Identify the primary failure signal in the The New Bundle Arrived and the One Rule That Should Have Left Stayed Behind in the Empty Room scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect partial bundle semantics before rebuilding the whole policy distribution path.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field