Resolved Plesk core dependency issues after upgrade 12.5.30 -> 17.5

[Bitpalast]

After upgrade of Plesk 12.5.30 to 17.5 on CentOS 7.3:

# package-cleanup --problems

Loaded plugins: fastestmirror
Package plesk-service-node-utilities-17.5.3-cos7.build1705170317.16.x86_64 has installed conflicts plesk-core < ('0', '17.0.17', None): plesk-core-12.5.30-cos7.build1205150826.19.x86_64
Package psa-drweb-configurator-17.5.3-cos7.build1705170317.16.x86_64 has installed conflicts plesk-core < ('0', '13.0.1', None): plesk-core-12.5.30-cos7.build1205150826.19.x86_64
Package psa-libpam-plesk-17.5.3-cos7.build1705170317.16.x86_64 has installed conflicts plesk-core < ('0', '17.5.3', None): plesk-core-12.5.30-cos7.build1205150826.19.x86_64

How to resolve?

Probably linked with this issue of the same upgrade:
Issue - Update from 12.5 to 17.5 leaves very many "duplicate" packages

 

[Bitpalast]

Oh great, now seeing that while Plesk thinks it is version 17.5, the server components mostly show 12.5.30. This is all so bad.

 

[Bitpalast]

I have asked Plesk support to solve this - and thanks to an awesome knowledgable support person it was fixed. The solution was individually designed for the situation on that system. Basically it was about removing the duplicates entries by "# rpm -e --nodeps" commands. It is not said that this is the correct approach for others. I once again made an excellent experience with Plesk support and can only recommend to open a ticket when running into difficult issues that are not really documented or clear.

Linked to this case: Resolved - Update from 12.5 to 17.5 leaves very many "duplicate" packages