Bug 671203 - Custom RHEL6 channel - Add "Red Hat Enterprise Linux 6" to Channel Version pulldown
Summary: Custom RHEL6 channel - Add "Red Hat Enterprise Linux 6" to Channel Version pu...
Keywords:
Status: CLOSED DUPLICATE of bug 664717
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 540
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-20 18:28 UTC by Cale Bouscal
Modified: 2015-03-05 00:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-21 09:20:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Cale Bouscal 2011-01-20 18:28:40 UTC
Description of problem:
Pulldown doesn't display version 6 as an option from which to select errata when creating a custom channel.

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

How reproducible:

Always


1. Manage Software Channels
 1a. Clone Channel
 1b. Clone From base channel (RHEL v6 32-bit)
 1c. Clone: Original State
 1d. Create Channel
 1e. Create Channel

2. Select "errata"
 2a. Add Errata
 2b. Add Red Hat Errata

Actual results:
In the "Channel Version" pulldown, RHEL ver. 2.1,3,4 and 5 are present,
but not 6. 

- if you were to click "View associated channels", you would no longer be able to see the RHEL6 channels in the second "Channel:" pulldown.

Expected results:
- '6' should be present in the "Channel Version" pulldown
- RHEL6 child channels sync'd to the satellite should be displayed in the "Channel:" pulldown such that their errata may be sync'd with the custom channel.

Additional info:
- 32-bit and 64-bit RHEL6 channels have been sync'd to this satellite, with several child channels.

Comment 1 Tomas Lestach 2011-01-21 09:20:56 UTC
Closing a duplicate of BZ#664717

*** This bug has been marked as a duplicate of bug 664717 ***


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