Project

Profile

Help

Issue #6450

Checking storage in tests uses incorrect value

Added by daviddavis about 2 months ago. Updated about 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 70

Description

In our tests, we check settings.DEFAULT_FILE_STORAGE against 'django.core.files.storage.FileSystemStorage' when it should be 'pulpcore.app.models.storage.FileSystem'. Here's an example[0].

[0] https://git.io/JvNbd


Related issues

Related to Pulp - Issue #6451: Our functional tests use settings from django.conf which may not be accurate CLOSED - CURRENTRELEASE Actions

Associated revisions

Revision 0b8383ac View on GitHub
Added by mdellweg about 2 months ago

Change storage checking in tests to use the correct value

[noissue]

History

#1 Updated by daviddavis about 2 months ago

  • Related to Issue #6451: Our functional tests use settings from django.conf which may not be accurate added

#2 Updated by daviddavis about 2 months ago

Note that if you fix this, the tests will probably fail in Travis due to #6451.

#3 Updated by fao89 about 2 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 70

#4 Updated by mdellweg about 2 months ago

  • Assignee set to mdellweg

#5 Updated by mdellweg about 2 months ago

  • Status changed from NEW to POST

#7 Updated by ttereshc about 2 months ago

  • Status changed from POST to MODIFIED

#8 Updated by ttereshc about 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
  • Sprint/Milestone set to 3.3.0

Please register to edit this issue

Also available in: Atom PDF