Bug 679568

Summary: Child channel from another org is listed twice and cannot be subscribed
Product: Red Hat Satellite 5 Reporter: David Egts <degts>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 540CC: cperry
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-04 13:20:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Duplicate child channel screen shot
none
Duplicate child channel error message screen shot
none
Child channel settings from main org none

Description David Egts 2011-02-22 21:33:15 UTC 
Description of problem:

When creating a custom child software channel in a master org, shared orgs see duplicates of the channel in an activation key.  Adding this child channel in activation key is prevented and an error message results.


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

5.4.0 (latest patches)


How reproducible:

100%


Steps to Reproduce:

1. Create child channel on master org and establish trust so other orgs can use it.

2. Add packages to channel.
 
3. Log into another org and create an activation key and try to add a child channel to it.

 
Actual results:

1. The child channel is listed, but listed twice.  Selecting either or both and then updating the key results a failure to add the subscriptions to the key along with the following error page:

~~~
500 Error - Internal Server Error

You may have reached this page in one of the following ways:

   1. You've found an error in the site. Please report this error to your local administrator with details of how you received this message.
~~~

2. Creating an activation key on the master org with the child channel works just fine as expected (listed once and works).


Expected results:

Child channel from another org is listed once and can be subscribed.
Comment 1 Tomas Lestach 2011-02-23 16:03:52 UTC 
Hello David,
unfortunately I cannot reproduce your problem. I followed your reproducer steps, but I see the child channel listed only once and I can associate it without any issues with the activation key.
Is there anything else i need to do to reproduce?
Comment 2 David Egts 2011-02-23 17:02:21 UTC 
Thanks for helping Tomas!

I'm heading off for travel and I will try again when I get back on Friday and take thorough notes.

Maybe I skipped a step on the setup on my end which is causing the problem?

I'll try to make sure I thoroughly deleted the child channel and start from the ground up documenting all the way.

What's the best way to confirm the channels are deleted and no cruft is left behind?  Is just deleting the channels via the web UI good enough or should I query the database somehow?

Thanks!
Comment 3 Tomas Lestach 2011-02-24 11:11:07 UTC 
David, just delete the channel via WebUi, there're no special actions needed.
Comment 4 David Egts 2011-02-26 19:40:16 UTC 
Thanks Tomas!

I deleted it through the web ui.  I created another child channel (with a different label and name just to be sure no other cruft was mistakenly reused) and it is listed twice when another org tries to add it to an activation key as noted above.  I still get the 501 error when either or both are used.  Please see attached screen shots.
Comment 5 David Egts 2011-02-26 19:42:09 UTC 
Created attachment 481180 [details]
Duplicate child channel screen shot
Comment 6 David Egts 2011-02-26 19:42:46 UTC 
Created attachment 481182 [details]
Duplicate child channel error message screen shot
Comment 7 David Egts 2011-02-26 19:45:24 UTC 
Created attachment 481183 [details]
Child channel settings from main org
Comment 8 Clifford Perry 2011-03-04 13:20:25 UTC 
Going to close this out. We are unable to replicate, nor is reporter on fresh system. 

Cliff