-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PodVolumeRestore
remains InProgress
after status reports that all data has been processed
#7798
Comments
I'll add that this is with Kopia, but I observed similar behavior when using Restic where it remained |
This may be related to your file system data, e.g., are there many actually-zero-byte items (empty dirs, symbol links, sparse files)? |
@Lyndon-Li For some context, this particular volume is the backend for a Distribution OCI registry. I've done a more recent test today with some different images and still see similar behavior with regards to the progress status:
bundle-2024-05-16-14-19-20.tar.gz Here's some details on the filesystem - a few empty dirs, several small (non-empty) files, and some larger files
|
Here are two reasons that
Therefore, with the current behavior, it is not reliable to decide the completion by comparing |
What steps did you take and what happened:
Hello, my goal is to be able to present the progress of a restore to a user. One piece of this is the
PodVolumeRestores
that are executed during the restore process. I've noticed that theTotalBytes
andBytesDone
status fields don't seem to represent the progress as I would expect and am wondering if this is a bug or if there is some other details that I should be looking at during the volume restore?For example, I have a roughly 10G volume that I am restoring and the progress shows 100% after a rather short time, but the
PodVolumeRestore
remains with anInProgress
status for several more minutes before becomingCompleted
.In the node-agent logs I see the following that seems to indicate the actual Kopia restore for this volume took ~8 minutes:
Is this expected that the
BytesDone
would be 100% of theTotalBytes
while the restore still appears to beInProgress
for a while longer?What did you expect to happen:
I would expect that the
PodVolumeRestore
would reach aCompleted
state shortly after all bytes have been processed and that theBytesDone
indicates the relative progress of the volume restore.The following information will help us better understand what's going on:
bundle-2024-05-15-18-04-26.tar.gz
Anything else you would like to add:
As mentioned, my goal is to display some sort of progress indicator to the user during a volume restore. Are thare any other resources outside of
PodVolumeRestore
that I should be considering?Environment:
velero version
):velero client config get features
):kubectl version
):/etc/os-release
):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: