Erreur lors d'une mise à jour Pod V4 (python3 manage.py migrate)

[gmanaud]

Bonjour,

Sur une instance de test de Pod v4 (neuve), je n'arrive pas à faire de mise à jour d'une version mineure à une autre (4.0.0 vers 4.0.1 par exemple).

J'ai une erreur avec les migrations flatpages :

$ python3 manage.py migrate
Operations to perform:
  Apply all migrations: admin, ai_enhancement, auth, authentication, authtoken, captcha, chapter, chunked_upload, completion, contenttypes, cut, django_cas_ng, dressing, enrichment, flatpages, hyperlinks, import_video, live, main, meeting, playlist, podfile, quiz, recorder, sessions, sites, speaker, thumbnail, video, video_encode_transcript, webpush
pre_migrate - Start save_previous_data
pre_migrate - save_previous_data --> OK
Start save_previous_data | playlists
(1054, "Unknown column 'title' in 'SELECT'")
(1146, "Table 'pod.playlist_playlistelement' doesn't exist")
(1146, "Table 'pod.favorite_favorite' doesn't exist")
save_previous_data --> OK | playlists
Running migrations:
  Applying flatpages.0002_flatpage_content_en_flatpage_content_fr_and_more...Traceback (most recent call last):
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/mysql/base.py", line 75, in execute
    return self.cursor.execute(query, args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/MySQLdb/cursors.py", line 179, in execute
    res = self._query(mogrified_query)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/MySQLdb/cursors.py", line 330, in _query
    db.query(q)
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/MySQLdb/connections.py", line 280, in query
    _mysql.connection.query(self, query)
MySQLdb.OperationalError: (1060, "Duplicate column name 'content_en'")

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/django_projects/podv4/manage.py", line 39, in <module>
    execute_from_command_line(sys.argv)
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/core/management/base.py", line 412, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/core/management/base.py", line 458, in execute
    output = self.handle(*args, **options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/core/management/base.py", line 106, in wrapper
    res = handle_func(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/core/management/commands/migrate.py", line 356, in handle
    post_migrate_state = executor.migrate(
                         ^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/migrations/executor.py", line 135, in migrate
    state = self._migrate_all_forwards(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards
    state = self.apply_migration(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/migrations/executor.py", line 252, in apply_migration
    state = migration.apply(state, schema_editor)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/migrations/migration.py", line 132, in apply
    operation.database_forwards(
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/migrations/operations/fields.py", line 108, in database_forwards
    schema_editor.add_field(
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/mysql/schema.py", line 107, in add_field
    super().add_field(model, field)
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 713, in add_field
    self.execute(sql, params)
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 201, in execute
    cursor.execute(sql, params)
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/utils.py", line 102, in execute
    return super().execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/utils.py", line 67, in execute
    return self._execute_with_wrappers(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
    return executor(sql, params, many, context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/utils.py", line 84, in _execute
    with self.db.wrap_database_errors:
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/db/backends/mysql/base.py", line 75, in execute
    return self.cursor.execute(query, args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/MySQLdb/cursors.py", line 179, in execute
    res = self._query(mogrified_query)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/MySQLdb/cursors.py", line 330, in _query
    db.query(q)
  File "/home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/MySQLdb/connections.py", line 280, in query
    _mysql.connection.query(self, query)
django.db.utils.OperationalError: (1060, "Duplicate column name 'content_en'")

La migration ne semble pas effectuée, et pourtant le schéma de la table semble correspondre à ce qui est attendu après :

$ python3 manage.py showmigrations flatpages
flatpages
 [X] 0001_initial
 [ ] 0002_flatpage_content_en_flatpage_content_fr_and_more

DESCRIBE django_flatpage;
+-----------------------+--------------+------+-----+---------+----------------+
| Field                 | Type         | Null | Key | Default | Extra          |
+-----------------------+--------------+------+-----+---------+----------------+
| id                    | int(11)      | NO   | PRI | NULL    | auto_increment |
| url                   | varchar(100) | NO   | MUL | NULL    |                |
| title                 | varchar(200) | NO   |     | NULL    |                |
| title_fr              | varchar(200) | YES  |     | NULL    |                |
| title_en              | varchar(200) | YES  |     | NULL    |                |
| content               | longtext     | NO   |     | NULL    |                |
| content_fr            | longtext     | YES  |     | NULL    |                |
| content_en            | longtext     | YES  |     | NULL    |                |
| enable_comments       | tinyint(1)   | NO   |     | NULL    |                |
| template_name         | varchar(70)  | NO   |     | NULL    |                |
| registration_required | tinyint(1)   | NO   |     | NULL    |                |
+-----------------------+--------------+------+-----+---------+----------------+

Contenu du fichier .virtualenvs/django_pod4/lib/python3.12/site-packages/django/contrib/flatpages/migrations/0002_flatpage_content_en_flatpage_content_fr_and_more.py

# Generated by Django 4.2.26 on 2025-11-13 12:33

from django.db import migrations, models


class Migration(migrations.Migration):

    dependencies = [
        ('flatpages', '0001_initial'),
    ]

    operations = [
        migrations.AddField(
            model_name='flatpage',
            name='content_en',
            field=models.TextField(blank=True, null=True, verbose_name='content'),
        ),
        migrations.AddField(
            model_name='flatpage',
            name='content_fr',
            field=models.TextField(blank=True, null=True, verbose_name='content'),
        ),
        migrations.AddField(
            model_name='flatpage',
            name='title_en',
            field=models.CharField(max_length=200, null=True, verbose_name='title'),
        ),
        migrations.AddField(
            model_name='flatpage',
            name='title_fr',
            field=models.CharField(max_length=200, null=True, verbose_name='title'),
        ),
    ]

Savez-vous d'où peut venir le problème et comment le corriger ?

[Badatos]

L'erreur "Duplicate column name 'content_en'"semble dire qu'il ne s'attend pas à avoir cette colonne, alors qu'elle est bien présente, donc je pense à une éventuelle erreur lors d'une migration précédente qui n'aurait pas été finalisée.
Pour corriger, je tenterais de supprimer la colonne content_en(attention cela supprime aussi tout son contenu, donc sauvegarder avant), avant de retenter la migration.

[gmanaud]

En alternative, j'ai trouvé la commande python3 manage.py migrate flatpages 0002_flatpage_content_en_flatpage_content_fr_and_more --fake qui permet de marquer cette migration comme étant déjà effectuée et de continuer la mise à jour normalement avec python3 manage.py migrate.

Mais ce qui m'étonne toutefois, c'est qu'à partir d'une installation neuve d'une version 4.0.x, ces tables sont déjà présentes. Je ne comprends donc pas pourquoi cette création de colonnes est proposée.

Exemple :
Sur une version 4.0.2 nouvellement installée (sans précédente mise à jour), j'ai :

DESCRIBE django_flatpage;
+-----------------------+--------------+------+-----+---------+----------------+
| Field                 | Type         | Null | Key | Default | Extra          |
+-----------------------+--------------+------+-----+---------+----------------+
| id                    | int(11)      | NO   | PRI | NULL    | auto_increment |
| url                   | varchar(100) | NO   | MUL | NULL    |                |
| title                 | varchar(200) | NO   |     | NULL    |                |
| title_fr              | varchar(200) | YES  |     | NULL    |                |
| title_en              | varchar(200) | YES  |     | NULL    |                |
| content               | longtext     | NO   |     | NULL    |                |
| content_fr            | longtext     | YES  |     | NULL    |                |
| content_en            | longtext     | YES  |     | NULL    |                |
| enable_comments       | tinyint(1)   | NO   |     | NULL    |                |
| template_name         | varchar(70)  | NO   |     | NULL    |                |
| registration_required | tinyint(1)   | NO   |     | NULL    |                |
+-----------------------+--------------+------+-----+---------+----------------+

Les 4 colonnes proposées en ajout dans la migration flatpages sont donc déjà présentes dès le départ.

Lorsque je tente la mise à jour en 4.0.3 :

(django_pod4) $ git checkout 4.0.3
Previous HEAD position was 23802ac0 Update settings.py (version 4.0.2)
HEAD is now at 2907d8c9 Merge pull request #1376 from EsupPortail/dev_v4

(django_pod4) $ pip3 install -r requirements.txt
[je passe les dépendances déjà installées]
Downloading django-4.2.26-py3-none-any.whl (8.0 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.0/8.0 MB 86.5 MB/s eta 0:00:00
Installing collected packages: Django
  Attempting uninstall: Django
    Found existing installation: Django 4.2.25
    Uninstalling Django-4.2.25:
      Successfully uninstalled Django-4.2.25
Successfully installed Django-4.2.26

(django_pod4) $ python manage.py makemigrations
Migrations for 'flatpages':
  /home/pod/.virtualenvs/django_pod4/lib/python3.12/site-packages/django/contrib/flatpages/migrations/0002_flatpage_content_en_flatpage_content_fr_and_more.py
    - Add field content_en to flatpage
    - Add field content_fr to flatpage
    - Add field title_en to flatpage
    - Add field title_fr to flatpage

La commande python manage.py migrate renvoie ensuite l'erreur mentionnée dans mon post initial.

C'est visiblement la mise à jour de django qui pose problème car si je reste sur la même version (en modifiant manuellement le requirements.txt avant l'upgrade), je n'ai pas d'erreur.