Issue Ubuntu 20 to 22 upgrade fails with RDS db

[Aldemir Akpinar]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

18.0.77 Update #2

Hi,
My upgrade failed because I'm using an RDS server. On RDS you can't have SUPER users, anyway here's my ERROR output:

ERROR: Upgrade step 2025-11-05-09-56-08_FixGrantPrivileges.php failed with code 1 and output:
INFO: Executing upgrade task: 2025-11-05-09-56-08
[2026-05-04 09:35:21.008] 10351:69f8685901d72 ERR [panel] SQLSTATE[42000]: Syntax error or access violation: 1044 Access denied for user 'remote-rds-user'@'%' to database 'mysql':
0: /opt/psa/admin/plib/Upgrade/upgrade.php:46
ERROR: Plesk\Upgrade\Exception: SQLSTATE[42000]: Syntax error or access violation: 1044 Access denied for user 'remote-rds-user'@'%' to database 'mysql' (upgrade.php:46)

Here are the grants for my user:

MySQL [(none)]> SHOW GRANTS FOR 'remote-rds-user'@'%';
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Grants for remote-rds-user@%                                                                                                                                                                                                                                                                                                                                      |
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, PROCESS, REFERENCES, INDEX, ALTER, SHOW DATABASES, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, REPLICATION SLAVE, REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, EVENT, TRIGGER, CREATE ROLE, DROP ROLE ON *.* TO `remote-rds-user`@`%` WITH GRANT OPTION |
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.002 sec)

 

[Sebahat.hadzhi]

Hi, @Aldemir Akpinar . An in-place upgrade is not the best option if you store websites databases in AWS RDS. In such a scenario, the recommended approach is a migration.

 

[Aldemir Akpinar]

Hi, @Aldemir Akpinar . An in-place upgrade is not the best option if you store websites databases in AWS RDS. In such a scenario, the recommended approach is a migration.

Thanks for the prompt reply, could you point me to do the docs for migration? Also how is my system impacted right now? Eveything apart from the problem above looks ok, and I can't restart my process now.
So If I understand correctly, is the problem with db server being elsewhere (not local) or RDS?

 

[Sebahat.hadzhi]

As far as I am aware, the dist-upgrade scripts have not been tested for compliancy with customizations, such as RDS, so unpredictable issues could arise. Here you can find the migration docs:

• Introduction

Eveything apart from the problem above looks ok, and I can't restart my process now.

I didn't quite catch that. Sorry. What process are you unable to restart?

 

[Aldemir Akpinar]

I mean the process of upgrading from 20 to 22. I can't restart that, or migrate as I'm having not a fully finished upgrade.

 

[learning_curve]

I mean the process of upgrading from 20 to 22. I can't restart that, or migrate as I'm having not a fully finished upgrade.

Presumably(?) You took a full server snapshot / backup of your Plesk/Ubuntu 20.04 LTS fully operational server, before you ran that upgrade, in which case: Restore that backup and then begin your Plesk Migration from your (restored) host server Plesk/Ubuntu 20.04 LTS over to your target server Plesk/Ubuntu 22.04 LTS, as per posts #2 and #4 in this thread.

IF you did not run a full server snapshot / backup, then a) Why? but more importantly b) You'll need to raise a ticket with Plesk support and to be fair, they're there to support Plesk (not Ubuntu release upgrades - usually) so you might need other assistance, as well as Plesk support.

Pretty sure that @Sebahat.hadzhi will post further, more specific details in due course