Closed dani closed 1 year ago
Hi,
Indeed, non interactive mode will block the update as schema produced by 10.0.8 update is different than expected.
CLI migration from to from GLPI 10.0.7 to GLPI 10.0.8 was certainly returning an error code. If you process updates using a script in non-interactive mode, you should probably handle error result code to detect update issues and fix them.
Anyway, we will not solve this specific case as it would require too many code, and we expect administrators to have fix the 10.0.7->10.0.8 migration issue when command tell them that there was a problem.
The database:update was not returning an error code (exit code 0), as the error wasn't catched by my ansible playbook. Anyway, not a big deal
The database:update was not returning an error code (exit code 0), as the error wasn't catched by my ansible playbook.
My bad. #15193 should fix this bad behaviour in the future.
Code of Conduct
Is there an existing issue for this?
Version
10.0.8
Bug description
I've updated my 10.0.7 instance to 10.0.8 last week, and everything was fine. Today, trying to update to 10.0.9 fails
If I run database:check_schema_integrity
It looks like the update from 10.0.7 to 10.0.8 did not create the event column in the glpi_queuednotifications table, which is now preventing further upgrades. Only uninteractive update are affected. I can upgrade the DB from the web interface (and most likely from the cli if I omit -n and validate the upgrade)
Relevant log output
No response
Page URL
No response
Steps To reproduce
Your GLPI setup information
Informations sur le système, l'installation et la configuration
Server
GLPI constants
Libraries
LDAP directories
SQL replicas
Notifications
Plugins list
Anything else?
No response