Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

bootc-fetch-apply-updates.timer/service never run on the composefs backend (`/run/ostree-booted` condition)

Aperta
  • Qualcosa non va?
#2,578 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
linux, rust
Ambito
operating-systems

Direzione di ricerca

Start by inspecting bootc-fetch-apply-updates.timer and bootc-fetch-apply-updates.service, then trace the boot flow that creates /run/ostree-booted and the existing composefs marker. Verify the update units activate on both backends while retaining the intended bootc-managed-host safeguards, and add regression coverage for each backend.

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

Descrizione

Describe the bug

On a composefs-backend (sealed / UKI) install, the automatic update units never run:

$ systemctl status bootc-fetch-apply-updates.timer
○ bootc-fetch-apply-updates.timer - Apply bootc updates
     Loaded: loaded (/usr/lib/systemd/system/bootc-fetch-apply-updates.timer; enabled; preset: enabled)
     Active: inactive (dead)
    Trigger: n/a
   Triggers: ● bootc-fetch-apply-updates.service
  Condition: start condition unmet at ...; 8min ago
             └─ ConditionPathExists=/run/ostree-booted was not met

/run/ostree-booted is only created by the ostree backend (ostree-prepare-root). On the composefs backend that service is skipped (ConditionKernelCommandLine=ostree) and no equivalent marker is created, so both bootc-fetch-apply-updates.timer and bootc-fetch-apply-updates.service carry an unmet ConditionPathExists=/run/ostree-booted and stay inactive forever.

Impact

Hosts installed with the composefs backend (e.g. sealed images booting a signed UKI) never fetch or apply updates automatically; they need an explicit bootc upgrade. The units are shipped enabled and there is no composefs-specific equivalent, so this is silent.

Environment
  • bootc 1.16.13 (quay.io/fedora/fedora-bootc:44, systemd 259.9)
  • Installed with bootc install to-disk from a sealed (UKI + composefs + fs-verity) image with systemd-boot + Secure Boot
  • Running as a VM on Proxmox VE 9.2; reproduced on a plain composefs install too
Workaround
# /etc/systemd/system/bootc-fetch-apply-updates.timer.d/10-composefs.conf
[Unit]
ConditionPathExists=

and the same drop-in for bootc-fetch-apply-updates.service. Verified: the timer then becomes active and schedules normally.

Suggested fix

Either drop the condition and let bootc itself decide whether the host is bootc-managed, or use a marker both backends provide (the composefs backend already creates /ostree/bootc; a /run/bootc-booted-style marker or a bootc status check would work).

Lingua principale
Rust
Stelle
2.3k
Fork
230
Merge medio
2g 12h
PR unite (30g)
47

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.