Bug 1221960 - [Build 71.1] openQA test fails in django
Summary: [Build 71.1] openQA test fails in django
Status: RESOLVED WONTFIX
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP6
Classification: openSUSE
Component: Python (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Daniel Garcia
QA Contact: E-mail List
URL: https://openqa.suse.de/tests/13873460...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-26 10:11 UTC by Michael Grifalconi
Modified: 2024-05-06 12:16 UTC (History)
4 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grifalconi 2024-03-26 10:11:05 UTC
## Observation

Hello, django test fails with the error:
   File '/media.1/media' not found on medium 'https://updates.suse.com/SUSE/Backports/SLE-15-SP6_x86_64/standard?[token-redacted]'



openQA test in scenario sle-15-SP6-Online-x86_64-stack_tests_python@64bit fails in
[django](https://openqa.suse.de/tests/13873460/modules/django/steps/26)

## Test suite description
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml.


## Reproducible

Fails since (at least) Build [57.1](https://openqa.suse.de/tests/13548994)


## Expected result

Last good: (unknown) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=stack_tests_python&version=15-SP6)
Comment 1 Daniel Garcia 2024-04-02 07:20:24 UTC
Is this because python3-Django can't be found in?

Right now we don't have python3-Django in Backports, for SP6 we've the python311-Django, package and the python3-Django package, that can be found on Leap is from SUSE:SLE-15:Update, version 2.0.7.
Comment 2 Daniel Garcia 2024-04-02 07:22:06 UTC
Should we copy the python3-Django package from SP5 Backports to SP6 Backports to provide also the python 3.6 updated version? or it's okay to just provide the python 3.11 version for Leap from now on?
Comment 3 Santiago Zarate 2024-04-23 15:13:26 UTC
(In reply to Daniel Garcia from comment #2)
> Should we copy the python3-Django package from SP5 Backports to SP6
> Backports to provide also the python 3.6 updated version? or it's okay to
> just provide the python 3.11 version for Leap from now on?

I can't say for sure, at the moment 3.11 version would be what my gut feeling says, but I don't have data to back this up. My thinking is that somebody is likely to use django on 3.10+ than on 3.6
Comment 4 Daniel Garcia 2024-05-06 12:11:07 UTC
Nothing to do at package level. The django package provided in SP6 is python311-Django. There's no python3-Django there.
Comment 5 Santiago Zarate 2024-05-06 12:16:37 UTC
(In reply to Daniel Garcia from comment #4)
> Nothing to do at package level. The django package provided in SP6 is
> python311-Django. There's no python3-Django there.

Created https://progress.opensuse.org/issues/159972 as a follow up