Red Hat Bugzilla – Bug 475854
Django requires MySQLdb-1.2.1p2 t run properly.
Last modified: 2013-07-02 23:20:12 EDT
Description of problem: bcfg2-info can not run properly and shows the following output problem: [root@mako ~]# bcfg2-info Traceback (most recent call last): File "/usr/sbin/bcfg2-info", line 314, in ? setup['encoding'], False) File "/usr/sbin/bcfg2-info", line 32, in __init__ passwd, svn, encoding) File "/usr/lib/python2.4/site-packages/Bcfg2/Server/Core.py", line 59, in __init__ self.init_plugins(plugin) File "/usr/lib/python2.4/site-packages/Bcfg2/Server/Core.py", line 108, in init_plugins mod = getattr(__import__("Bcfg2.Server.Plugins.%s" % File "/usr/lib/python2.4/site-packages/Bcfg2/Server/Plugins/DBStats.py", line 2, in ? import Bcfg2.Server.Reports.importscript File "/usr/lib/python2.4/site-packages/Bcfg2/Server/Reports/importscript.py", line 19, in ? from Bcfg2.Server.Reports.reports.models import Client, Interaction, Entries, Entries_interactions, Performance, Reason, Ping, TYPE_CHOICES, InternalDatabaseVersion File "/usr/lib/python2.4/site-packages/Bcfg2/Server/Reports/reports/models.py", line 4, in ? from models_new import * File "/usr/lib/python2.4/site-packages/Bcfg2/Server/Reports/reports/models_new.py", line 2, in ? from django.db import models File "/usr/lib/python2.4/site-packages/django/db/__init__.py", line 16, in ? backend = __import__('%s%s.base' % (_import_path, settings.DATABASE_ENGINE), {}, {}, ['']) File "/usr/lib/python2.4/site-packages/django/db/backends/mysql/base.py", line 22, in ? raise ImproperlyConfigured("MySQLdb-1.2.1p2 or newer is required; you have %s" % Database.__version__) django.core.exceptions.ImproperlyConfigured: MySQLdb-1.2.1p2 or newer is required; you have 1.2.1 Version-Release number of selected component (if applicable): MySQL-python-1.2.1-1 bcfg2-server-0.9.6-1.el5 How reproducible: every time you run bcfg2-info when bcfg2 is running w/ mysql backend Steps to Reproduce: 1. enable epel 2. install bcfg2-server, mysql-server and MySQL-python 3. try to run bcfg2-info when running w/ a mysql back end. Actual results: will not run, see above Expected results: no errors and normal output Additional info: fully updated centos5.2 and epel. No other repos enabled.
One way out is to upgrade MySQL-python; either way, it's either a bcfg2-server bug (if it can only use MySQL backend) or a MySQL-python bug. Unless we are to split out Django's database backends, and disable the mysql backend on EPEL for the time being. Seems rather drastic, given that the other backends work just fine.
Don't hold your breath waiting for a MySQL-python rebase in RHEL-5; in previous go-rounds it's taken literally years to get permission to fix anything in that package :-( Still, we seem to have managed to get into a state where RHEL-5 is shipping an older version than RHEL-4 (1.2.1 vs 1.2.1p2), which is definitely a bad thing. I'll put this into the request queue for 5.4 and we'll see what happens.
From what I understand, these are the issues with 1.2.1 http://groups.google.com/group/django-developers/browse_thread/thread/490b8f7eea86873f http://wolfram.kriesing.de/blog/index.php/2006/multithreading-with-mysqldb-and-weakrefs
Hmph. So the actual problem here is that the django people completely failed to think about whether their minimum requirement was 1.2.1, or 1.2.1_p2. As per our mailing list discussion just now, the two versions are equivalent if you're talking to a 4.1 or newer mysql server; or at least that's what the author says. If we were going to do a rebase in RHEL-5, the appropriate target would be 1.2.2 (or maybe 1.2.3, if it's final by the time permission comes through). This would fix a few bugs, but the odds of it happening are not good unless a few requests get escalated through the Proper Channels :-(
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
*** Bug 472195 has been marked as a duplicate of this bug. ***
*** Bug 622370 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
could we have the steps to reproduce clarified? I've tried to install the packages, run "bcfg2-admin init", changed database_* records in /etc/bcfg2.conf, started mysqld, created user & database according to those settings, started bcfg2-server service, run bcfg-info ... and no traceback happened
Same problem here with django. Just create a new django project. Modify the settings.py to use your mysql-server. Try to sync the database (./manage.py syncdb): ./manage.py syncdb --noinput Traceback (most recent call last): File "./manage.py", line 11, in ? execute_manager(settings) File "/usr/lib/python2.4/site-packages/django/core/management/__init__.py", line 362, in execute_manager utility.execute() File "/usr/lib/python2.4/site-packages/django/core/management/__init__.py", line 303, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.4/site-packages/django/core/management/base.py", line 195, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.4/site-packages/django/core/management/base.py", line 221, in execute self.validate() File "/usr/lib/python2.4/site-packages/django/core/management/base.py", line 249, in validate num_errors = get_validation_errors(s, app) File "/usr/lib/python2.4/site-packages/django/core/management/validation.py", line 22, in get_validation_errors from django.db import models, connection File "/usr/lib/python2.4/site-packages/django/db/__init__.py", line 41, in ? backend = load_backend(settings.DATABASE_ENGINE) File "/usr/lib/python2.4/site-packages/django/db/__init__.py", line 17, in load_backend return import_module('.base', 'django.db.backends.%s' % backend_name) File "/usr/lib/python2.4/site-packages/django/utils/importlib.py", line 35, in import_module __import__(name) File "/usr/lib/python2.4/site-packages/django/db/backends/mysql/base.py", line 22, in ? raise ImproperlyConfigured("MySQLdb-1.2.1p2 or newer is required; you have %s" % Database.__version__) django.core.exceptions.ImproperlyConfigured: MySQLdb-1.2.1p2 or newer is required; you have 1.2.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0181.html