Can you try to execute following SQL request on ‘centreon’ database and continue upgrade process:

ALTER TABLE `provider_configuration` ADD COLUMN `custom_configuration` JSON NOT NULL AFTER `name`

@Laurent 
Thanks for your answer, I did that, but I always get the same result on the web interface:
 

And on the /var/log/centreon/upgrade.log:

2024-05-22 13:32|0|0|UPGRADE - 22.04.1: Unable to update 'custom_configuration' column on 'provider_configuration' table - Code : 0 - Error : No custom_configuration for open_id has been found - Trace : #0 /usr/share/centreon/www/install/php/Update-22.04.1.php(36): updateOpenIdConfiguration()
#1 /usr/share/centreon/src/Core/Platform/Infrastructure/Repository/DbWriteUpdateRepository.php(144): include_once('...')
#2 /usr/share/centreon/src/Core/Platform/Infrastructure/Repository/DbWriteUpdateRepository.php(61): Core\Platform\Infrastructure\Repository\DbWriteUpdateRepository->runScript()
#3 /usr/share/centreon/www/install/step_upgrade/process/process_step4.php(46): Core\Platform\Infrastructure\Repository\DbWriteUpdateRepository->runUpdate()
#4 {main}

/var/log/centreon/sql-error.log is empty…

Hi, can ou try to comment line 36 and refresh?

#updateOpenIdConfiguration($pearDB);

Thanks a lot !
GOOD, we go on, but not totally…
Now I’ve got:
 

Nothing more in upgrade.log, but in sql-error.log, I have now:

2024-05-23 09:00|0|0|SQLSTATEL42S22]: Column not found: 1054 Unknown column 'sat.token_type' in 'where clause' QUERY : DELETE st FROM security_token st
WHERE st.expiration_date < UNIX_TIMESTAMP(NOW())
AND EXISTS (
    SELECT 1
    FROM security_authentication_tokens sat
    WHERE sat.provider_token_refresh_id = st.id
    AND sat.token_type = 'auto'
    LIMIT 1
)
2024-05-23 09:00|0|0|TokenRemoval CRON: failed to delete old tokens

The table, security_authentication_tokens contains 0 row !

This seems to be, once again related to openid…
Where does that come from ?

@Laurent 
Any idea ?