Resolved Manual updates or re-installation?

[somemorestuff]

Hi all,

We have a dedicated Centos 7.3 server which came with Plesk Onyx 17.5.3 and MariaDB.

We followed this guide:

Database Server

to change the DB to Percona. The only step that wasn't carried out was the re-installation of Plesk, which seems to have been an optional step.

Everything works fine, except for automatic plesk updates.

Running 'plesk sbin pum --check' shows that some plesk components have dependencies for a mariadb library which has now been superseded by a percona library. Trying to resolve these manually has failed, as the percona library is newer.
We acknowledge that this issue may have been created because of the final (optional?) step where Plesk wasnt re-installed . However, as all but the auto update is working we thought it would be acceptable.

My questions are:
1) Can we periodically run 'plesk installer install-panel-updates' or 'plesk sbin pum --update' manually or via a cron as an alternative?
2) What is the difference between those two commands?
3) Should we just re-install Plesk?

If we do re-install Plesk, as per this thread - Resolved - reinstall plesk what do we need to backup? and will our current license key work with the new version? (We bought Plesk through our server provider). Can we save the license file somewhere and restore it for the new installation?

Thanks in advance for for any recommendations.

Edit: It looks like we're having similar issues to: Question - Replacing MariaDB with Percona on CentOS7

 

[somemorestuff]

Although we are still getting the message on the system update screen : Warning: Information on some packages might not be actual: inconsistencies were detected in the system's package manager database. Please resolve this issue manually.

Plesk seems to be updating itself without issue. So we are happy to ignore this warning message, perhaps the message will get removed automatically with an update from Plesk when it realises that Percona is installed instead of Mariadb