← Problem Library
CI/CD L3 CICD-381 · 15 min

A pipeline pins the runner image while the fetched bootstrap script still resolves the latest policy bundle from a mutable channel during a staged decommission

The execution environment is frozen and its policy input is not. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.

CI/CDFoundation OpsLevel 3Free15 min
Scenario

The execution environment is frozen and its policy input is not. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.

What to check first
  • Identify the primary failure signal in the Pinned Runner, Floating Policy Bundle 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

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

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.