j'étais sur WAPT 1.8.2.7393-75a5de09-debian-10-amd64, donc server debian 10. Je cherche à migrer vers la 2.4.0.14080
j'ai mis à jour debian vers la version 11, donc postgres 13 (database migrée à l'aide de pg_upgradecluster, tout s'est bien passé...)
J'ai suivi ensuite la procédure d'upgrade https://www.wapt.fr/en/doc/wapt-server-upgrade.html
Lors de l'étape post-install, j'obtiens:
Code : Tout sélectionner
root@host:~# sudo -u wapt /opt/wapt/bin/python -I /opt/wapt/waptserver/model.py upgrade-db -l info
initializing missing wapt tables without dropping data.
2023-08-06 17:21:57,559 INFO Connecting to waptdb explicitely. Count: 0
Unable to create tables, will try to upgrade step by step instead... : ProgrammingError('column "host_networking" does not exist\n')
2023-08-06 17:21:57,640 INFO Current DB: {'host': None, 'port': 5432, 'user': 'wapt', 'password': None} version: 1.9.0.4
2023-08-06 17:21:57,656 INFO Migrating from 1.9.0.4 to 1.9.0.12
Traceback (most recent call last):
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 3144, in execute_sql
cursor.execute(sql, params or ())
psycopg2.errors.UndefinedColumn: column t1.changelog does not exist
LINE 1: ...age", "t1"."icon_sha256sum", "t1"."is_available", "t1"."chan...
^
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/wapt/waptserver/model.py", line 2784, in <module>
init_db(False,server_config=conf)
File "/opt/wapt/waptserver/model.py", line 2156, in init_db
upgrade_db_structure(server_config=server_config)
File "/opt/wapt/waptserver/model.py", line 2245, in upgrade_db_structure
Packages.update_from_repo(r)
File "/opt/wapt/waptserver/model.py", line 585, in update_from_repo
(rec, _isnew) = cls.update_from_control(pe,is_available=True)
File "/opt/wapt/waptserver/model.py", line 539, in update_from_control
(rec, _isnew) = Packages.get_or_create(**key)
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 6471, in get_or_create
return query.get(), False
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 6884, in get
return clone.execute(database)[0]
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 1907, in inner
return method(self, database, *args, **kwargs)
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 1978, in execute
return self._execute(database)
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 2150, in _execute
cursor = database.execute(self)
File "/opt/wapt/lib/python3.8/site-packages/playhouse/postgres_ext.py", line 490, in execute
cursor = self.execute_sql(sql, params, commit=commit)
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 3151, in execute_sql
self.commit()
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 2917, in __exit__
reraise(new_type, new_type(exc_value, *exc_args), traceback)
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 190, in reraise
raise value.with_traceback(tb)
File "/opt/wapt/lib/python3.8/site-packages/peewee.py", line 3144, in execute_sql
cursor.execute(sql, params or ())
peewee.ProgrammingError: column t1.changelog does not exist
LINE 1: ...age", "t1"."icon_sha256sum", "t1"."is_available", "t1"."chan...
(A noter: je suis repassé sous WAPT 1.8.2 (sans downgrader Debian, donc toujours Debian 11) et tout marche sous cette version (j'ai quand même dû restaurer la base de donnée depuis une sauvegarde, la migration de DB du au post-install a dû s'arrêter au milieu du chemin... )
Une ideé?
Cordialement
