Bootc status without sysroot lock
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 230
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 38
Description
When an automated upgrade is happening in the background, you are unable to query `bootc status` to see information about the current deployment (or to see the upgrade is in progress), since status requires a sysroot lock. I would expect such read-only commands (I can only think of status for now) to not require a system lock, and display the regular output regardless of whether another process is happening.
This could cause some confusion when you're blocked from seeing information about your system due to a command that's invoked without the user saying to do so.
If there's some context I am missing or a technical limitation, I'm more than happy for you to say "this is expected" and close this.
Contributor guide
Assessment
This issue has not been assessed yet.