Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 528923

Summary: Wrong "Parent Channel" list in creating custom software channel
Product: Red Hat Satellite 5 Reporter: Garik Khachikyan <gkhachik>
Component: WebUIAssignee: Justin Sherrill <jsherril>
Status: CLOSED DUPLICATE QA Contact: Brandon Perkins <bperkins>
Severity: medium Docs Contact:
Priority: medium    
Version: 530CC: cperry, mkoci, psklenar
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-14 13:08:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Base channels list none

Description Garik Khachikyan 2009-10-14 11:45:19 UTC 
Description of problem:
In installed Satellite 5.3.0 the action, when user creates a custom software channel and lists the parent channels list to select a parent channel to assign the creating one to be as a child, browses wrong list with "Parent Channel"s info: all the parent channels are duplicated by some numbers in a list. For example "Red Hat Enterprise Linux Desktop (v. 5 for 32-bit x86)" has appeared several times in that list.

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


How reproducible:
Always on installed Satellite 5.3.0


Steps to Reproduce:
1. Refer to "Channels"->"Manage Software Channels"
2. Do "create new channel"
3. List the "Parent Channel" listbox.
  
Actual results:
One instance of each base channel should be listed there.

Expected results:
Multiple instances of each base channel are listed there.

Additional info:
Comment 1 Garik Khachikyan 2009-10-14 11:49:08 UTC 
Created attachment 364741 [details]
Base channels list
Comment 2 Petr Sklenar 2009-10-14 13:08:38 UTC 

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