Task #9171: Remove workaround in RemoteArtifactSaver now that we're on Django 3.2 - Pulp

Actions

Send by e-mail Copy link

Task #9171

closed

Task #8488: [EPIC] Upgrade to django 3.2

Remove workaround in RemoteArtifactSaver now that we're on Django 3.2

Added by bmbouter over 3 years ago. Updated about 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

-

Category:

-

Sprint/Milestone:

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

No

Sprint Candidate:

No

Tags:

Sprint:

Quarter:

Description

The workaround is here: https://github.com/pulp/pulpcore/blob/master/pulpcore/plugin/stages/artifact_stages.py#L290-L292

The upstream Django ticket is here: https://code.djangoproject.com/ticket/32089

The corresponding commit in Django shows it's fixed with 3.2.0+.

Actions

#1

Updated by pulpbot over 3 years ago

Status changed from NEW to POST

PR: https://github.com/pulp/pulpcore/pull/1530

Added by dkliban@redhat.com over 3 years ago

Revision fb7fc09c | View on GitHub

Removes workaround in RemoteArtifactSaver

Django 3.2 contains a fix for the bug that required a workaround. https://code.djangoproject.com/ticket/32089

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

Actions

#2

Updated by dkliban@redhat.com over 3 years ago

Status changed from POST to MODIFIED
% Done changed from 0 to 100

Applied in changeset pulpcore|fb7fc09ce4878e5d698773330d43b196857ca2eb.

Actions

#3

Updated by pulpbot about 3 years ago

Sprint/Milestone set to 3.15.0

Actions

#4

Updated by pulpbot about 3 years ago

Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Actions

Send by e-mail Copy link

Also available in: Atom PDF