Project

Profile

Help

Story #2517

closed

As a user I can continue to sync rest of the repo after corrupted manifest is encountered

Added by ipanova@redhat.com over 7 years ago. Updated about 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Target Release - Docker:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

During download of manifests step if one of the manifests is corrupted we finish the sync right away without giving the possibility to sync subsequent manifests in the repo.
We should log the error in the task progress report and continue to sync other manifests.
When sync completes we should mark the task status as failed with logged errors and problematic manifests.


$ pulp-admin docker  repo  sync run --repo-id=synctest

+----------------------------------------------------------------------+
                  Synchronizing Repository [synctest]
+----------------------------------------------------------------------+

This command may be exited via ctrl+c without affecting the request.

Downloading manifests
[-]

Task Failed

The Manifest digest does not match the expected value. The remote feed announced
a digest of
sha256:aaaaaaaaaaaaaaaa but the
downloaded digest was
sha256:bbbbbbbbbbbbbbbb.

$ pulp-admin -v docker repo list

+----------------------------------------------------------------------+
                          Docker Repositories
+----------------------------------------------------------------------+

Id:                  synctest
Display Name:        None
Description:         None
Content Unit Counts: 

As you can see no content at all was synced because first processed manifest was corrupted and this prevented us to sync the rest of the content. We should change the behaviour.

Also available in: Atom PDF