Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 454912 - RHEL EUS v5.2.z for 32bit x86 is not correctly identified as the newest EUS channel
Summary: RHEL EUS v5.2.z for 32bit x86 is not correctly identified as the newest EUS c...
Alias: None
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Channels
Version: rhn505
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dennis Gregorovic
QA Contact: Red Hat Network Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-10 18:52 UTC by Stephen Herr
Modified: 2008-09-05 19:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-09-05 19:11:41 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Stephen Herr 2008-07-10 18:52:58 UTC
Description of problem:
v5.1.z is currently identified as the newest EUS channel. It should be v5.2.z. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Log into RHN
2. select a server that it's okay to change the base entitlements on, from the
server details page go to software -> software channels.
3. set the normal base channel (for example RHEL 5; NOT the EUS version) and
view the drop-down to see available base channel changes.
Actual results:
RHEL 5 (currently selected)
RHEL EUS 5.1.z

Expected results:
RHEL 5 (currently selected)
RHEL EUS 5.2.z

Additional info:
You are allowed to upgrade from the base (RHEL 5) to the latest EUS version. The
fact that it's listing EUS 5.1.z means it thinks that's the latest, even though
there is a 5.2.z channel.

Comment 1 Dennis Gregorovic 2008-09-05 17:27:55 UTC
This should be fixed now.

Comment 2 Stephen Herr 2008-09-05 19:11:41 UTC
Looks good, thanks dgregor

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