[bootc 1.15.2 - almalinux-bootc:10.2] Consecutive soft-reboot transitions do not activate the expected target deployment

未關閉
#2,387 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
55/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
rust

研究方向

先追蹤 crates/lib/src/bootc_composefs/soft_reboot.rs 中連續軟重啟的處理,接著追蹤 update.rs 和 rollback.rs 中的分階段升級與回滾流程。透過連續執行 bootc rollback --apply --soft-reboot=required 和升級操作來重現,並檢查 bootc status --verbose 與 ostree admin status。完成的標準是:要求的 deployment 在第二次轉換後被啟用,且狀態與使用者空間檔案系統一致。

由索引模型根據 Issue 內容生成。

描述

Summary

Consecutive bootc operations using --apply --soft-reboot=required on a ostree-backed system trigger systemd soft-reboots, but the expected target deployment is not activated on the second transition.

This reproduces with both bootc rollback and bootc upgrade.

Environment

  • Repository: bootc-dev/bootc
  • Backend: ostree with composefs enabled
  • Commands tested with --apply --soft-reboot=required
  • bootc status --verbose showed both booted and rollback deployments as Soft-reboot: yes
  • bootc --version -> 1.15.2 (almalinux-bootc:10.2)

Reproduction

Starting state:

  • Booted image: my-repo/my-project/my-image:A
  • Rollback image: my-repo/my-project/my-image:B
  • Both entries reported Soft-reboot: yes

Then run:

  1. bootc rollback --apply --soft-reboot=required
  2. Verify the system is now booted into my-image:B and rollback points to my-image:A
  3. Run bootc rollback --apply --soft-reboot=required again

A similar issue is observed with consecutive bootc upgrade --apply --soft-reboot=required operations.

Expected behavior

If both the current and target deployments are reported as Soft-reboot: yes, a second consecutive soft-reboot-capable transition should activate the requested target deployment.

For rollback specifically, the second rollback should return the system to the previous deployment.

Actual behavior

The second soft-reboot is triggered by systemd, but the expected target deployment seems not to be activated.

After the second rollback, bootc status --verbose still shows the same booted/rollback pair instead of flipping back.

However, the userspace filesystem seems to be the expected one. So, what is returned by bootc status doesn't match with what is actually done.

Journal output confirms that a second soft-reboot occurred:

Aug 18 14:24:08 ar-node-153 systemd[1]: Soft-rebooting.
Aug 18 14:25:01 ar-node-153 systemd[1]: Soft-reboot finished in 57.036s, counter is now at 1.
...
Aug 18 14:29:18 ar-node-153 systemd[1]: Soft-rebooting.
Aug 18 14:30:25 ar-node-153 systemd[1]: Soft-reboot finished in 1min 11.431s, counter is now at 2.

ostree admin status after preparing the second transition shows a pending soft-reboot deployment:

  default ddf9cef2ccbd4637f3f5b4fc9d366aa3273ca3c3b1d5ba9bbff0910d7f19d650.1 (pending) (soft-reboot)
    origin: <unknown origin type>
* default cbdc4faca29a53293e0f717abb4d387b89470cd5c618ff68a702de2ba99d233a.0
    origin: <unknown origin type>

So the soft-reboot appears to be prepared, but the resulting active deployment after the reboot does not match expectations.

Additional notes

This does not appear to be a generic systemd limitation, because systemd reports completing two consecutive soft-reboots successfully. The problem seems specific to how bootc prepares or consumes the pending deployment for a second consecutive soft-reboot-capable transition.

Relevant implementation areas in the repository include:

  • crates/lib/src/bootc_composefs/soft_reboot.rs
  • crates/lib/src/bootc_composefs/update.rs
  • crates/lib/src/bootc_composefs/rollback.rs

Possible direction

Investigate consecutive soft-reboot flows for both staged upgrades and rollback/revert flows, especially cases where a new pending (soft-reboot) deployment is prepared after a previous soft-reboot has already occurred.

主要語言
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 摘要。