Utilizzavo WAPT 1.8.2.7393-75a5de09-debian-10-amd64, quindi un server Debian 10. Vorrei migrare alla versione 2.4.0.14080
Ho aggiornato Debian alla versione 11, quindi PostgreSQL 13 (database migrato tramite pg_upgradecluster, tutto è andato bene...)
Ho quindi seguito la procedura di aggiornamento https://www.wapt.fr/it/doc/wapt-server-upgrade.html
Durante la fase di post-installazione, ottengo:
Codice: Seleziona tutto
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...
(Nota: sono tornato a WAPT 1.8.2 (senza effettuare il downgrade di Debian, quindi ancora Debian 11) e tutto funziona con questa versione (ho dovuto ripristinare il database da un backup, la migrazione del database dovuta alla post-installazione deve essersi interrotta a metà...)
Avete qualche idea?
Sinceramente
