Upgrade reports no changes when containers-storage tag is stale

Abierto
#2,519 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
58/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust

Línea de trabajo

Start by reproducing the stale local tag scenario from the listed boot and upgrade steps. Trace the unified pull path from the registry to bootc storage and compare it with the direct registry path used by --check. Done means the local tag refreshes to the remote digest and the upgrade stages the new image instead of reporting no changes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What happened

On bootc 1.16.13, with :testing at an older digest in local containers-storage and a newer digest published remotely, both plain update and update --apply printed a wall of Already exists lines and then concluded with No changes in => and No update available. Meanwhile status showed a cached update and upgrade --check correctly reported the newer version and digest as available.

Inspecting the local tag afterward showed it still pointed at the old digest: the pull step never refreshed it, so the import step compared stale-local against booted and found nothing to do.

What I expected

The pull step to refresh the local tag to the remote digest and the upgrade to stage, since --check proved the update existed.

Steps to reproduce

  1. Boot an image whose tag also exists in local containers-storage at the booted (older) digest.
  2. Publish a newer digest under the same remote tag.
  3. Run the update with apply. Observe Already exists spam followed by No changes pointing at the old digest.
  4. Confirm the local tag still resolves to the old digest.
  5. Run a plain container pull of the same tag, then retry the upgrade: it stages correctly (in my case, 18 changed layers, new ostree commit queued for next boot).

Additional context

System log lines during the failed runs show the unified pull path: pulling from transport registry to bootc storage, then importing from the containers-storage transport by tag name. The check path instead fetches from the registry directly, which is why --check saw the update while the real pull did not. Workaround is a manual container pull of the tag before upgrading. Seen twice in a row, five minutes apart, so unlikely to be a transient registry read.

Lenguaje dominante
Rust
Estrellas
2.3k
Forks
230
Merge medio
2 d 11 h
PR fusionados (30 d)
42

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de bootc-dev/bootc

Todos los issues de bootc-dev/bootc

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.