Pod Volume Restore progress update miss under Kopia path

[Lyndon-Li]

Kopia restore processes several files (e.g., 4 files) in parallel, when each file processing completes, it updates the progress. Therefore, if the in parallel processes complete very close to each other, the progress will be updated for multiple times in a short time.

On the other hand, Velero uploader wrapper has a throttle to the progress update, if the current update request is close to the last update (< 10s), the current update will be ignored, as seen here.
Meanwhile, Velero's progress update is triggered directly by Kopia's update, as seen here.

Therefore, it is possible that the Kopia's progress update requests are ignored by Velero if they are close to one another.

As an example shown below, the progress update is very few:

NAME                           STATUS       TOTALBYTES   BYTESDONE   AGE
test-10-20230328161828-ht9p9   InProgress                            15s
test-10-20230328161828-ht9p9   InProgress   18253611008   8589934592   5m38s
test-10-20230328161828-ht9p9   InProgress   18253611008   17179869184   10m
test-10-20230328161828-ht9p9   InProgress   18253611008   18253611008   11m
test-10-20230328161828-ht9p9   Completed    18253611008   18253611008   11m

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

[Lyndon-Li]

The primary cause is Kopia restore updates the progress only after a file is completely restored. And issue #8158 fixes it.