Upgrade reports no changes when containers-storage tag is stale

オープン
#2,519 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
58/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
rust

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Rust
スター
2.3k
フォーク
230
平均マージ
2日 11時間
マージ済み PR(30日)
42

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

bootc-dev/bootc のほかの issue

bootc-dev/bootc の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。