Bug 1316309

Summary: Satellite 6.2 upgrade: check current Sat 6 version and fail/exit if below 6.1.9 with instructions to update first
Product: Red Hat Satellite Reporter: Xixi <xdmoon>
Component: UpgradesAssignee: David Davis <daviddavis>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: bbuckingham, bkearney, chrobert, daviddavis, dcaplan, ehelms, mmccune, sthirugn, xdmoon
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14306
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-16 22:06:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1315269    
Bug Blocks: 1115190    

Description Xixi 2016-03-09 23:13:25 UTC 
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:
Comment 5 Stephen Benjamin 2016-03-21 19:29:24 UTC 
Created redmine issue http://projects.theforeman.org/issues/14306 from this bug
Comment 6 Stephen Benjamin 2016-05-17 15:28:05 UTC 
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).
Comment 7 David Davis 2016-06-02 18:09:37 UTC 
Handling this as part of https://bugzilla.redhat.com/show_bug.cgi?id=1315269
Comment 8 Bryan Kearney 2016-06-02 18:13:11 UTC 
Upstream bug assigned to stbenjam
Comment 9 Bryan Kearney 2016-06-02 18:13:15 UTC 
Upstream bug assigned to stbenjam
Comment 10 Bryan Kearney 2016-06-07 14:13:50 UTC 
Upstream bug assigned to daviddavis
Comment 11 Bryan Kearney 2016-06-07 14:13:53 UTC 
Upstream bug assigned to daviddavis
Comment 14 Mike McCune 2016-09-16 22:06:52 UTC 
we shipped this in RHBA-2016:1499-03