Bug 1273838

Summary: rhevm-appliance 3.6 should not use RHEL 6.7 Beta
Product: Red Hat Enterprise Virtualization Manager Reporter: Ying Cui <ycui>
Component: rhevm-applianceAssignee: Anatoly Litovsky <tlitovsk>
Status: CLOSED ERRATA QA Contact: Gonza <grafuls>
Severity: high Docs Contact:
Priority: urgent    
Version: 3.6.0CC: dfediuck, fdeutsch, gklein, mgoldboi
Target Milestone: ovirt-3.6.1Keywords: Regression
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhevm-appliance-20151029.2-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 21:43:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Ying Cui 2015-10-21 11:27:17 UTC 
Description:
  The platform OS of rhevm-appliance-20151019.0-1 is RHEL 6.7 Beta, but RHEL 6.7 GA already pushed on July. We can not ship this rhevm-appliance with RHEL 6.7 Beta OS with rhev 3.6.

Version:
rhevm-appliance-20151019.0-1 

Test Steps:
1. Boot up this appliance
2. 
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.7 Beta (Santiago)

# uname -r
2.6.32-573.el6.x86_64

Actual Result:
OS of rhevm-appliance-20151019.0-1 is RHEL 6.7 Beta

Expected Result:
Not Beta RHEL 6.7 for rhevm-appliance because RHEL 6.7 already was GA two months ago.
Comment 1 Ying Cui 2015-10-21 11:27:54 UTC 
Created attachment 1085093 [details]
screenshot
Comment 3 Fabian Deutsch 2015-10-21 11:31:10 UTC 
This is a valid point.

We probably just need to update the inheritance tree to use the right 6.7 trees.
Comment 5 Gonza 2015-11-04 16:34:51 UTC 
Verified with:
rhevm-appliance-20151029.2-1

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.7 (Santiago)
Comment 7 errata-xmlrpc 2016-03-09 21:43:59 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/RHBA-2016:0385