Bug 1316309 - Satellite 6.2 upgrade: check current Sat 6 version and fail/exit if below 6.1.9 with instructions to update first
Summary: Satellite 6.2 upgrade: check current Sat 6 version and fail/exit if below 6.1...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: David Davis
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1315269
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2016-03-09 23:13 UTC by Xixi
Modified: 2017-02-23 19:38 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-16 22:06:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14306 0 None None None 2016-04-22 15:38:16 UTC

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


Note You need to log in before you can comment on or make changes to this bug.