Bug 1524560

Summary: Import error on django modules on epel.
Product: [Fedora] Fedora EPEL Reporter: Patrick Creech <pcreech>
Component: python-django16Assignee: Stephen Gallagher <sgallagh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: brian, sgallagh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django16-1.6.11.6-7.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-19 19:13:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Patrick Creech 2017-12-11 16:52:00 UTC 
Description of problem:

ImportError on django modules


How reproducible:
Very

Steps to Reproduce:
On a rhel7 System, install pulp which depends on python-django:

git clone https://github.com/pulp/pulp-ci
pushd pulp-ci/ci/ansible/
echo 'localhost' > hosts
ansible-playbook --connection local -i ./hosts pulp_server.yaml -e pulp_build=nightly -e pulp_version=2.15



Actual results:

Pulp services are not running, due to missing django dependencies

Dec 11 17:10:00 [machine] pulp_streamer[5928]: /usr/lib/python2.7/site-packages/celery/fixups/django.py:38: FixupWarning: Environment variable DJANGO_SETTINGS_MODULE is defined
Dec 11 17:10:00 [machine] pulp_streamer[5928]: but Django is not installed.  Will not apply Django fixups!
Dec 11 17:10:00 [machine] pulp_streamer[5928]: warnings.warn(FixupWarning(ERR_NOT_INSTALLED))
Dec 11 17:10:00 [machine] celery[5944]: File "/usr/lib/python2.7/site-packages/pulp/server/webservices/views/serializers/__init__.py", line 4, in <module>
Dec 11 17:10:00 [machine] celery[5944]: from django.core.urlresolvers import reverse
Dec 11 17:10:00 [machine] celery[5944]: ImportError: No module named django.core.urlresolvers

Expected results:

Django modules would import successfully


Additional info:

After installing python-django, our services could work again.

[pcreech@machine usr]$ rpm -qa python-django*
python-django-bash-completion-1.6.11.6-1.el7.noarch
python-django16-1.6.11.6-6.el7.noarch
python-django-1.6.11.6-1.el7.noarch



These errors started showing up on our automation jobs over the weekend, appearing to coincide with this bodhi update being pushed to stable:

https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-40b69d00b9
Comment 1 Fedora Update System 2017-12-11 17:19:29 UTC 
python-django16-1.6.11.6-7.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-b4207a980b
Comment 2 Fedora Update System 2017-12-12 16:12:55 UTC 
python-django16-1.6.11.6-7.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-b4207a980b
Comment 3 Brian J. Murrell 2017-12-13 11:12:54 UTC 
How long will this be in testing before it will pushed to GA?
Comment 4 Brian J. Murrell 2017-12-13 11:21:03 UTC 
Given this failure when using the python-django16 what is the future python-django and python-django16 in EPEL?

It looks like some kind of transition is in play here and I just want to understand what it is so that we can be prepared for it and not just know about it at some point in the future because things break for us due to the transition.

IOW, what should we be doing to survive any kind of transition without this kind of disruption in the future?  It seems that if I want to stay with Django 1.6 I will need to install python-django16 explicitly at some point.  Is that correct?

Will the problem described in this ticket then be worked on before such a need arises?
Comment 5 Stephen Gallagher 2017-12-13 13:33:24 UTC 
(In reply to Brian J. Murrell from comment #4)
> Given this failure when using the python-django16 what is the future
> python-django and python-django16 in EPEL?
> 
> It looks like some kind of transition is in play here and I just want to
> understand what it is so that we can be prepared for it and not just know
> about it at some point in the future because things break for us due to the
> transition.
> 

The purpose of python-django16 is *solely* to support the stack required to run ReviewBoard (whose upstream is continuing the security support for that EOL branch). No one else should be using it.

> IOW, what should we be doing to survive any kind of transition without this
> kind of disruption in the future?  It seems that if I want to stay with
> Django 1.6 I will need to install python-django16 explicitly at some point. 
> Is that correct?

Please don't, upstream is dead except for cases that affect Review Board.

> 
> Will the problem described in this ticket then be worked on before such a
> need arises?

The bug was that I mistakenly added Provides: python-django == 1.6.11.6 but other packages actually require modification to be able to access it. So I dropped that Provides; if they really want to use it, the'll need to follow instructions at https://fedoraproject.org/wiki/Packaging:Python_Eggs#Multiple_Versions
Comment 6 Stephen Gallagher 2017-12-13 13:34:48 UTC 
(In reply to Brian J. Murrell from comment #3)
> How long will this be in testing before it will pushed to GA?

Either 14 days or as soon as someone logs in via FAS and provides positive karma, since I set the autokarma at 1.
Comment 7 Fedora Update System 2017-12-19 19:13:37 UTC 
python-django16-1.6.11.6-7.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.