← Problem Library
Linux L4 LINUX-381 · 17 min

An SELinux file context restore fixes the target path while a transient tmpfiles rule recreates it at boot with the wrong type again during a staged decommission

Manual recovery works and the next boot silently undoes it. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.

LinuxFoundation OpsLevel 4Free17 min
Scenario

Manual recovery works and the next boot silently undoes it. 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 Context Fixed, Boot Automation Re-broke It 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.