zidz opened a new issue, #12460:
URL: https://github.com/apache/cloudstack/issues/12460

   ### problem
   
   I was following the upgrade walk through here: 
https://docs.cloudstack.apache.org/en/4.22.0.0/upgrading/upgrade/upgrade-4.21.html
   When there was time to start the management server again I get this error:
   ```
   2026-01-19 09:53:45,366 DEBUG [c.c.u.d.ScriptRunner] (main:[]) (logid:) CALL 
`cloud`.`INSERT_EXTENSION_IF_NOT_EXISTS`('MaaS', 'Baremetal Extension for 
Canonical MaaS written in Python', 'MaaS/maas.py') 
   2026-01-19 09:53:45,366 ERROR [c.c.u.d.ScriptRunner] (main:[]) (logid:) 
Error executing: CALL `cloud`.`INSERT_EXTENSION_IF_NOT_EXISTS`('MaaS', 
'Baremetal Extension for Canonical MaaS written in Python', 'MaaS/maas.py') 
   2026-01-19 09:53:45,366 ERROR [c.c.u.d.ScriptRunner] (main:[]) (logid:) 
java.sql.SQLSyntaxErrorException: PROCEDURE 
cloud.INSERT_EXTENSION_IF_NOT_EXISTS does not exist
   2026-01-19 09:53:45,367 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) 
(logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: 
PROCEDURE cloud.INSERT_EXTENSION_IF_NOT_EXISTS does not exist
   ```
   
   Resulting in fatal error and the management server won't start.
   
   ### versions
   
   ACS Upgrade 4.21 -> 4.22
   
   kvm --version
   QEMU emulator version 7.2.22 (Debian 1:7.2+dfsg-7+deb12u18)
   
   mariadb --version
   mariadb  Ver 15.1 Distrib 10.11.14-MariaDB, for debian-linux-gnu (x86_64) 
using  EditLine wrapper
   
   ### The steps to reproduce the bug
   
   Alter /etc/apt/sources.list.d/cloudstack.list to "deb 
[signed-by=/usr/share/keyrings/cloudstack.gpg] 
https://download.cloudstack.org/ubuntu/ noble 4.22"
   sudo service cloudstack-management stop
   sudo apt-get update; sudo apt-get upgrade cloudstack-management
   sudo service cloudstack-management start
   
   
   
   ### What to do about it?
   
   I'm trying to find the sql source of this missing procedure so I can add it. 
Can not find it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to