Bug 487177 - Duplicate channels listed in activation keys channel selection boxes after custom channel creation
Summary: Duplicate channels listed in activation keys channel selection boxes after cu...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 530
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Justin Sherrill
QA Contact: Steve Salevan
URL:
Whiteboard:
Depends On:
Blocks: 456998
TreeView+ depends on / blocked
 
Reported: 2009-02-24 17:11 UTC by Steve Salevan
Modified: 2009-08-27 06:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-10 15:37:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steve Salevan 2009-02-24 17:11:03 UTC
Description of problem:
If a user creates a channel via:

/rhn/channels/manage/Edit.do

and then navigates to the Activation Key creation page:

/rhn/activationkeys/Create.do

then looks inside the 'Base Channels' selector, the selector will contain duplicate entries for all custom channels.

Version-Release number of selected component (if applicable):
530-re20090220.1

How reproducible:
Always

Steps to Reproduce:
1. Create a custom channel at /rhn/channels/manage/Edit.do
2. Navigate to /rhn/activationkeys/Create.do
3. Look inside the 'Base Channels' selector
  
Actual results:
Duplicate entries exist for all custom channels

Expected results:
Only single instances of each custom channel appear in selector

Additional info:

Comment 1 Brandon Perkins 2009-02-24 17:17:25 UTC
Feels like Multi-Org.

Comment 2 Justin Sherrill 2009-03-09 16:16:11 UTC
Looks fine to me, Steve are you still able to reproduce with the latest ISO?

Comment 3 Steve Salevan 2009-03-10 15:29:38 UTC
I no longer see this bug, but it appears we have a bit of a reversal of fortune, which I've documented in this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=489522

Comment 4 Brandon Perkins 2009-03-10 15:37:23 UTC
Closing based on Comment #3


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