What were you trying to do that didn't work?

The user story is present in https://github.com/oamg/leapp-repository/issues/1183 .

Red Hat Satellite 6.16 on RHEL 8.10 comes with Postgresql 13 installed already. So when leapp`ing the system to RHEL, We will still see the recommendation provided by leapp about upgrading the database after the IPU completes. 

But if someone mistakenly follows that for satellite, It will result in an FATAL error when using the application later on. 

What is the impact of this issue to you?

The in place upgrade of satellite 6.16 may not be able to recover the application if someone tries to stop postgresql service later on and attempts to upgrade the database again

Please provide the package NVR for which the bug is seen:

leapp-0.18.0-1.el8_10

How reproducible is this bug?:

Always

Steps to reproduce

1.  Install a Satellite 6.16 on RHEL 8
2.  Note down the version of postgres installed
3.  Try to do "leapp preupgrade" on the same.

Expected results

Either it should not suggest doing any db upgrade at all when postgres 13 already is there or the statement in the message needs to be improved in leapp report. The proposal can be found in https://github.com/oamg/leapp-repository/issues/1183#issuecomment-2478323208 

Actual results

Whether postgres 13 is installed or not, leapp will still recommend the manual db upgrade after the IPU has been completed.