Project

Profile

Help

Issue #9229

closed

push operation does not save config blob with the correct media_type

Added by ipanova@redhat.com over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulp_container/493":https://github.com/pulp/pulp_container/issues/493


After push operation Config Blob is saved with media_type from a Regular Blob. This issue does not seem to affect pull operation hence priority is not 'everything is on fire ' :)

After podman push :


In [5]: Manifest.objects.first().config_blob.media_type
Out[5]: 'application/vnd.docker.image.rootfs.diff.tar.gzip'

In [6]: Blob.objects.distinct("media_type").values_list('media_type', flat=True)
Out[6]: <QuerySet ['application/vnd.docker.image.rootfs.diff.tar.gzip']>

https://github.com/pulp/pulp_container/blob/master/pulp_container/app/registry_api.py#L685

Actions #1

Updated by ipanova@redhat.com over 1 year ago

  • Description updated (diff)
Actions #2

Updated by ipanova@redhat.com over 1 year ago

  • Description updated (diff)
Actions #3

Updated by mdellweg over 1 year ago

  • Triaged changed from No to Yes
Actions #4

Updated by pulpbot over 1 year ago

  • Status changed from NEW to POST
Actions #5

Updated by ipanova@redhat.com about 1 year ago

  • Status changed from POST to NEW

moving this back to NEW. We might want to deprecate media_type for blob in general, clients do not look at this information at all https://github.com/pulp/pulp_container/pull/414#discussion_r749731354

Actions #6

Updated by pulpbot about 1 year ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF