Actions
Issue #8691
closedPulp fails against django 2.2.21
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 96
Quarter:
Description
Run the test suite and you'll hit errors such as these:
File name '/var/lib/pulp/media/artifact/2a/3123f84da036df8e4233e9d9e54bbc0c0b0a7655e45e874a80bf7d67e60f03' includes path elements
The cause is this fix in django:
https://github.com/django/django/commit/04ac1624bdc2fa737188401757cf95ced122d26d
Related issues
Updated by daviddavis over 3 years ago
- Priority changed from Normal to High
- Sprint/Milestone set to 3.13.0
- Triaged changed from No to Yes
- Sprint set to Sprint 96
Updated by bmbouter over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
Updated by alikins over 3 years ago
Can this get backported to 3.11 branch?
galaxy_ng is setup to use pulpcore-3.11.x at the moment, so runs into this issue.
Updated by alikins over 3 years ago
https://github.com/pulp/pulpcore/pull/1305 backport to 3.11 branch pr
Updated by bmbouter over 3 years ago
@alikins, we could merge your PR, but it could only unblock source installs since we can't release that commit. Is that what you desired?
Updated by pulpbot over 3 years ago
- Status changed from ASSIGNED to POST
Updated by ggainey over 3 years ago
- Related to Issue #8709: SuspiciousFileOperation: File name '/var/lib/pulp/tmp/..@.../tmpqe08qjln' includes path elements added
Updated by dalley over 3 years ago
- Related to Issue #8718: Repository sync is broken with django 2.2.22 added
Added by bmbouter over 3 years ago
Updated by bmbouter over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|446fc631cd148acd79a40ed0ee57c79e68f0b8c5.
Updated by ttereshc over 3 years ago
- Related to Backport #8758: Backport 8691 to pulpcore 3.11 added
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Fixes Pulp compatability with Django 2.2 LTS
Adjusts the upload machinery to be compatible with Django 2.2.21+. The 2.2.21 release was too strict in its checking, and 2.2.23 loosen it, so we require 2.2.23 with this PR.
closes #8691