Bug 1019223 - 'Beta Release' warning should be removed from RHS 2.1 Update 1 ISO at GA.
Summary: 'Beta Release' warning should be removed from RHS 2.1 Update 1 ISO at GA.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: distribution
Version: 2.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: ---
Assignee: Anthony Towns
QA Contact: Rejy M Cyriac
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-15 10:21 UTC by Gowrishankar Rajaiyan
Modified: 2014-07-11 06:40 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.4.0.36rhs-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-09 16:45:30 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Gowrishankar Rajaiyan 2013-10-15 10:21:00 UTC 
Filing as a tracker bug.

Description of problem:
The RHS 2.1 Update 1 ISO - RHSS-2.1-20131015.n.0-RHS-x86_64-DVD1.iso - shows warning that it is 'pre-release software' at initial installation screen. This has to be removed when this ISO is made externally available at GA.

Version-Release number of selected component (if applicable):
RHSS-2.1-20131015.n.0-RHS-x86_64-DVD1.iso

How reproducible:


Steps to Reproduce:
1.Start install of RHS 2.1 Update 1 from RHSS-2.1-20131015.n.0-RHS-x86_64-DVD1.iso
2.Observe warning at initial screen.

Expected results:
The warning of being 'pre-release software', shown at initial installation screen should be removed for GA.
Comment 3 Rejy M Cyriac 2013-11-14 14:43:44 UTC 
RHSS-2.1-20131114.n.0-RHS-x86_64-DVD1.iso has the 'Beta Release' warning, so assuming that it is not an RC compose.
Comment 4 Gowrishankar Rajaiyan 2013-11-14 14:52:37 UTC 
That is correct. This is not an RC compose.
Comment 5 Rejy M Cyriac 2013-11-18 12:15:22 UTC 
The RC Candidate 'RHSS-2.1-20131114.0-RHS-x86_64-DVD1.iso' *does not* have the 'Beta Release' warning.

Marking this BZ as 'VERIFIED'.
Note You need to log in before you can comment on or make changes to this bug.