Container native chunk count is zero-indexed #5238
Labels
area/client
Issues related to client-side operations (upgrades, karg changes, etc)
container-native
good-first-issue
good issue for someone new
triaged
This issue was triaged
Describe the bug
I am running a container-based image:
ostree-unverified-registry:quay.io/fedora-ostree-desktops/cosmic-atomic:41
When I run
rpm-ostree upgrade
, there is an output that states the number of chunks needed, followed by each chunk being downloaded. The number of chunks being downloaded begins with "0" and ends with N-1/N.This isn't a huge issue, but it did make me think that my download had stalled at N-1 chunks when in reality it had completed and was processing the next step in the upgrade. I ended up issuing a
rpm-ostree cancel
command because of this confusion.Reproduction steps
rpm-ostree upgrade
Expected behavior
"Fetching ostree chunk" messages should start with "[1/N]" and end with "[N/N]".
Actual behavior
"Fetching ostree chunk" begins with "[0/N]" and ends with "[N-1/N]"
System details
rpm-ostree --version
rpm-ostree:
Version: '2024.9'
Git: bd152998332c2b11af671447d3fd311319d5b3a8
Features:
Additional information
Sample output:
The text was updated successfully, but these errors were encountered: