Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

Created redmine issue http://projects.theforeman.org/issues/14306 from this bug

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).

Handling this as part of https://bugzilla.redhat.com/show_bug.cgi?id=1315269

Upstream bug assigned to stbenjam

Upstream bug assigned to stbenjam

Upstream bug assigned to daviddavis

Upstream bug assigned to daviddavis

we shipped this in RHBA-2016:1499-03