Description of problem:
Satellite 6.2 upgrade requires existing Sat 6 installation to be at least 6.1.9 update level, otherwise it may fail, or end up removing content nodes which would prevent updates post-upgrade. Satellite 6.2 upgrade tooling needs to first check if underlying Satellite is at 6.1.9 or newer. If not, exit and explain to user how to update to 6.1.9 first before re-attempting upgrade to 6.2.0.
Version-Release number of selected component (if applicable):
Satellite 6.2
How reproducible:
always
Steps to Reproduce:
1. upgrade to Satellite 6.2 from unsupported version
2.
3.
Actual results:
upgrade fails, or succeed but with severe support or functionality ramifications
Expected results:
Check current Satellite version first to make sure customer is upgrading from 6.1.9 or newer Sat 6.1 GA version to 6.2.0 GA version. If older than 6.1.9, message user to update to 6.1.9 first (and how).
Additional info:
Can't find a particularly good way to do this - what's the reason we need to do it?
There's no RPM facility to prevent this that I can think of, and tried a few ways and none of them really work. I thought about failing in %pre but that only affects 1 rpm, not the entire transaction (PR discussion here: https://github.com/Katello/katello-packaging/pull/224).