Project

Profile

Help

Issue #2441

closed

unassociating a docker_manifest removes docker_blob regardless of whether or not other docker_manifest in repo reference it

Added by jluza over 7 years ago. Updated about 5 years ago.

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

Description

reproducer:

repo content:
Manifest: sha256:70753876404a22bc39af3ddcae831f9f2d32950f27f964dd781c66da051be957
 |- Blob: sha256:6e0419422ad90f146b41a787cbfa826ee3dd372b1dc0e3f100dbd71d5b63d47d
 |- Blob: sha256:16dc1f96e3a1bb628be2e00518fec2bb97bd5933859de592a00e2eb7774b6ecf

Manifest: sha256:c7a76dc3a509a42c9af781674826ed5c107017299aea2f10b06e658abbe5299f
 |- Blob: sha256:c157e91881d411d2e1847078ae5635d2b52f947ad07c218e248806768700fcdb
 |- Blob: sha256:16dc1f96e3a1bb628be2e00518fec2bb97bd5933859de592a00e2eb7774b6ecf

1. unassociate {"filters": {"unit": {"digest": "sha256:c7a76dc3a509a42c9af781674826ed5c107017299aea2f10b06e658abbe5299f"}}}
2. Result:
repo doesn't have sha256:c157e91881d411d2e1847078ae5635d2b52f947ad07c218e248806768700fcdb
repo doesn't have sha256:16dc1f96e3a1bb628be2e00518fec2bb97bd5933859de592a00e2eb7774b6ecf

Expected behaviour:
repo doesn't have sha256:c157e91881d411d2e1847078ae5635d2b52f947ad07c218e248806768700fcdb
repos DOES have sha256:16dc1f96e3a1bb628be2e00518fec2bb97bd5933859de592a00e2eb7774b6ecf

Also available in: Atom PDF