Just stumbled across a problem that had me resorting to the power of Google for a fix today...
Cobbler server OS is CentOS 6.5 x86_64
Cobbler itself is installed from the packages in the EPEL repository and was upgraded from 2.4 to 2.6 overnight.
# rpm -qa|grep -i cobbler cobbler-web-2.6.3-1.el6.noarch cobbler-2.6.3-1.el6.noarch
On restarting httpd and cobblerd, I was getting an exception when accessingthe web interface:
Exception Type: ImportError Exception Value: cannot import name patterns Exception Location: /usr/share/cobbler/web/cobbler_web/urls.py in <module>, line 1 Python Executable: /usr/bin/python Python Version: 2.6.6
It turns out that this is caused by the fact that the Django package version in EPEL is still at 1.3.7. The fix is to change the line at the top of /usr/share/cobbler/web/cobbler_web/urls.py from:
from django.conf.urls import patterns
to:
from django.conf.urls.defaults import *
And, of course, wait for the EPEL maintainers to get Django 1.4 packaged! The only question I have is whether there s nay other functionality in v2.6 that relies upon something specific to Django 1.4?
On 08/13/2014 10:18 AM, Phil Edwards wrote:
Just stumbled across a problem that had me resorting to the power of Google for a fix today...
Cobbler server OS is CentOS 6.5 x86_64
Cobbler itself is installed from the packages in the EPEL repository and was upgraded from 2.4 to 2.6 overnight.
# rpm -qa|grep -i cobbler cobbler-web-2.6.3-1.el6.noarch cobbler-2.6.3-1.el6.noarch
On restarting httpd and cobblerd, I was getting an exception when accessingthe web interface:
Exception Type: ImportError Exception Value: cannot import name patterns Exception Location: /usr/share/cobbler/web/cobbler_web/urls.py in <module>, line 1 Python Executable: /usr/bin/python Python Version: 2.6.6
It turns out that this is caused by the fact that the Django package version in EPEL is still at 1.3.7. The fix is to change the line at the top of /usr/share/cobbler/web/cobbler_web/urls.py from:
from django.conf.urls import patterns
to:
from django.conf.urls.defaults import *
And, of course, wait for the EPEL maintainers to get Django 1.4 packaged! The only question I have is whether there s nay other functionality in v2.6 that relies upon something specific to Django 1.4?
Django 1.4 is packaged as Django14 for EPEL. I suppose we should change the requires for the EPEL package.
It seems to be okay in the upstream specfile. I suppose there's some specfile drift between downstream and upstream?
On Wed, Aug 13, 2014 at 11:46 PM, Orion Poplawski orion@cora.nwra.com wrote:
On 08/13/2014 10:18 AM, Phil Edwards wrote:
Just stumbled across a problem that had me resorting to the power of Google for a fix today...
Cobbler server OS is CentOS 6.5 x86_64
Cobbler itself is installed from the packages in the EPEL repository and was upgraded from 2.4 to 2.6 overnight.
# rpm -qa|grep -i cobbler cobbler-web-2.6.3-1.el6.noarch cobbler-2.6.3-1.el6.noarch
On restarting httpd and cobblerd, I was getting an exception when accessingthe web interface:
Exception Type: ImportError Exception Value: cannot import name patterns Exception Location: /usr/share/cobbler/web/cobbler_web/urls.py in <module>, line 1 Python Executable: /usr/bin/python Python Version: 2.6.6
It turns out that this is caused by the fact that the Django package version in EPEL is still at 1.3.7. The fix is to change the line at the top of /usr/share/cobbler/web/cobbler_web/urls.py from:
from django.conf.urls import patterns
to:
from django.conf.urls.defaults import *
And, of course, wait for the EPEL maintainers to get Django 1.4 packaged! The only question I have is whether there s nay other functionality in v2.6 that relies upon something specific to Django 1.4?
Django 1.4 is packaged as Django14 for EPEL. I suppose we should change the requires for the EPEL package.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com
cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler
On 08/16/2014 12:52 AM, Jörgen Maas wrote:
It seems to be okay in the upstream specfile. I suppose there's some specfile drift between downstream and upstream?
Yes, there are some (necessary) differences.
cobbler@lists.fedorahosted.org