Add `bootc discard-staged` to safely cancel a pending deployment

Aperta
#2,660 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Start by reading the deployment and rollback paths for both OSTree and composefs, then trace how ordinary and --download-only stages affect the next-boot selection and tracked image reference. Add bootc discard-staged with safe handling for concurrent staging and no-stage cases. Done means tests cover both backends and next-boot behavior, bootc status reports no staged deployment, and an unrelated reboot cannot apply the discarded image.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Description

Bootc currently lacks a dedicated way to discard a staged deployment while keeping the currently booted image as the next-boot default. bootc rollback discards staging but queues the rollback image instead. This matters when a staged image fails a newly applied signature policy: skipping an agent-initiated reboot is insufficient because an unrelated reboot may still apply it. See CVE-2026-16460. This mechanism will also benefit the bootc-operator, since a signature policy could change between the time the deployment was staged and the reboot, this will enable the bootc-operator to discard the deployment.

Expected behavior
  • Works with OSTree and composefs backends, including ordinary and --download-only stages.
  • Leaves booted image selected for next boot; preserves rollback deployment.
  • Is safe and idempotent when no stage exists.
  • Handles concurrent staging safely and documents how the tracked image reference changes.
  • After success, bootc status shows no staged deployment; an unrelated reboot cannot apply the discarded image.
  • Includes tests for both backends and next-boot behavior.
Lingua principale
Rust
Stelle
2.3k
Fork
230
Merge medio
2g 11h
PR unite (30g)
42

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di bootc-dev/bootc

Tutte le issue di bootc-dev/bootc

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.