Project

Profile

Help

Issue #3286

closed

Sync logic should not assume on schema1 by default existence

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

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Start date:
Due date:
Estimated time:
Severity:
3. High
Version - Docker:
Platform Release:
2.15.3
Target Release - Docker:
OS:
Triaged:
Yes
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 32
Quarter:

Description

We should change logic of the repo sync, so it would not fail when there is not available image manifest schema1, it should try to fetch schema1 and save it in case it's available, and continue to sync in case image is stored just in schema2 version.

When an older client would pull image which is stored only in a newer format, it will get 404.


Related issues

Related to Docker Support - Issue #3258: Update with new recipe for v2s1 manifest upload CLOSED - CURRENTRELEASEipanova@redhat.comActions
Actions #1

Updated by ipanova@redhat.com almost 7 years ago

  • Related to Issue #3258: Update with new recipe for v2s1 manifest upload added
Actions #2

Updated by dkliban@redhat.com almost 7 years ago

  • Groomed changed from No to Yes
Actions #3

Updated by ipanova@redhat.com almost 7 years ago

  • Status changed from NEW to ASSIGNED
  • Priority changed from Normal to High
  • Severity changed from 2. Medium to 3. High
Actions #4

Updated by ipanova@redhat.com almost 7 years ago

  • Sprint/Milestone set to 53
Actions #5

Updated by ipanova@redhat.com almost 7 years ago

  • Assignee set to ipanova@redhat.com
Actions #6

Updated by dalley almost 7 years ago

  • Triaged changed from No to Yes
Actions #7

Updated by jortel@redhat.com almost 7 years ago

  • Sprint/Milestone changed from 53 to 54

Added by ipanova@redhat.com almost 7 years ago

Revision eba63782 | View on GitHub

Sync logic should not assume on schema1 by default existence.

closes #3286 https://pulp.plan.io/issues/3286

Added by ipanova@redhat.com almost 7 years ago

Revision eba63782 | View on GitHub

Sync logic should not assume on schema1 by default existence.

closes #3286 https://pulp.plan.io/issues/3286

Added by ipanova@redhat.com almost 7 years ago

Revision eba63782 | View on GitHub

Sync logic should not assume on schema1 by default existence.

closes #3286 https://pulp.plan.io/issues/3286

Added by ipanova@redhat.com almost 7 years ago

Revision eba63782 | View on GitHub

Sync logic should not assume on schema1 by default existence.

closes #3286 https://pulp.plan.io/issues/3286

Actions #8

Updated by ipanova@redhat.com almost 7 years ago

  • Status changed from ASSIGNED to POST
Actions #9

Updated by ipanova@redhat.com almost 7 years ago

  • Status changed from POST to MODIFIED
Actions #10

Updated by bmbouter almost 7 years ago

  • Platform Release set to 2.15.3
Actions #11

Updated by bmbouter almost 7 years ago

  • Sprint set to Sprint 32
Actions #12

Updated by bmbouter almost 7 years ago

  • Sprint/Milestone deleted (54)

Added by ipanova@redhat.com almost 7 years ago

Revision ab869e24 | View on GitHub

Sync logic should not assume on schema1 by default existence.

closes #3286 https://pulp.plan.io/issues/3286

(cherry picked from commit eba63782c49d03fde29ea20d0481dc49fe0b73a0)

Added by ipanova@redhat.com almost 7 years ago

Revision ab869e24 | View on GitHub

Sync logic should not assume on schema1 by default existence.

closes #3286 https://pulp.plan.io/issues/3286

(cherry picked from commit eba63782c49d03fde29ea20d0481dc49fe0b73a0)

Actions #14

Updated by bmbouter almost 7 years ago

  • Status changed from MODIFIED to 5
Actions #15

Updated by bmbouter almost 7 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions #17

Updated by bmbouter over 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF