Upgrade reports no changes when containers-storage tag is stale

未关闭
#2,519 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
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 小时
30 天内合并 PR
42

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

bootc-dev/bootc 的其他 Issue

查看 bootc-dev/bootc 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。