[PATCH proxmox-backup 0/2] fix #7606: verify: s3: handle transient fetch errors and add retry

[Christian Ebner <c.ebner@proxmox.com>]

Transient errors during fetching of object from s3 backend currently
lead to snapshots being marked as verify failed. Subsequent runs of
verification on the same snapshot might succeed without issues, since
chunks are only flagged as bad if the chunk blob object could not be
decoded or content verification failed.

To fix this, discriminate between transient errors and permanent
errors and account for these separately. For snapshots encountering
only transient errors, but no permanent errors during verification,
do not set or strip the verify okay state, but always keep a
pre-existing verification failed state. This is to never allow reuse
of a snapshot as reference for backup/sync jobs, when the state
was bad before and could not be verified again. For the other case
there is not much to loose, if it was okay or not verified before
falling back to not verified reflects the current snapshot state.

Link to the bugtracker issue:
https://bugzilla.proxmox.com/show_bug.cgi?id=7606


proxmox-backup:

Christian Ebner (2):
  fix #7606: verify: s3: handle transient chunk load errors
  verify: s3: retry on transient response body collection errors

 src/backup/verify.rs | 235 ++++++++++++++++++++++++++++++-------------
 1 file changed, 165 insertions(+), 70 deletions(-)


Summary over all repositories:
  1 files changed, 165 insertions(+), 70 deletions(-)

-- 
Generated by murpp 0.11.0