Open evgeni opened 6 months ago
Discussed with database team, the report is still wanted, as one of actions prior the upgrade (in general) is the complete backup of the system. In case of databases, it's better to have the warning still present so users have the backup of their data (ideally, dump of current database). So in case of any issues, they can recover it. The way here would an update of the text, so people are aware that possibly they will not need to recover the database after the upgrade, but they should still be informed the dump is recommended anyway.
Actual behavior When upgrading an EL8 system with PostgreSQL 13 installed, a warning is issued that manual steps are required when on EL9. This is however not correct, as EL9 also ships PostgreSQL 13 by default and the upgrade "just works"
To Reproduce Steps to reproduce the behavior
HIGH and MEDIUM severity reports: …
Expected behavior Given that I am already on PostgreSQL 13, I would expect not to see the PostgreSQL warning (by checking the version of the
postgresql-server
package and only emitting the above warning if it's not 13.x).Continuing with the upgrade, ignoring this warning, indeed produces a system with a working PostgreSQL 13 from EL9 running.
System information (please complete the following information):
leapp-repository is v0.20.0 plus my CentOS patches (https://github.com/evgeni/leapp-repository/pull/2)