Bug 1507040

Summary: [RFE]: Validate the RHGS <3.4 upgrade from RHEL6 to RHGS 3.4 RHEL7
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rahul Hinduja <rhinduja>
Component: coreAssignee: Vijay Bellur <vbellur>
Status: CLOSED ERRATA QA Contact: Sweta Anandpara <sanandpa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: amukherj, asriram, rhinduja, rhs-bugs, sanandpa, sheggodu, storage-qa-internal
Target Milestone: ---Keywords: FutureFeature
Target Release: RHGS 3.4.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 06:52:37 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1503132    

Description Rahul Hinduja 2017-10-27 13:48:24 UTC
Description of problem:
=======================

Raising against core, as there seem to be no specific component for upgrade or test effort only. 

To support the RHEL6 to RHEL7 upgrade path, there exists two scenario: 

1. RHGS version is <= RHGS 3.3.x and underlying RHEL version is <= latest version of RHEL6 . Upgrade process should update the RHGS version to 3.4 and underlying RHEL version to the latest version of RHEL7.

2. RHGS version is RHGS 3.4 and underlying RHEL version is the latest version of RHEL6. Upgrade process should keep the RHGS version to 3.4 and underlying RHEL version to the latest version of RHEL7.

This bug is raised to track the testing effort and validation comments to address for Scenario 1

Comment 7 errata-xmlrpc 2018-09-04 06:52:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2608