Bug 840432

Summary: Custom repository assigned to default cluster automatically
Product: Red Hat Update Infrastructure for Cloud Providers Reporter: mkovacik
Component: RHUAAssignee: James Slagle <jslagle>
Status: CLOSED DUPLICATE QA Contact: mkovacik
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.1CC: kbidarka, sghai, tsanders, whayutin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-18 18:27:38 UTC Type: Bug
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
Screen log none

Description mkovacik 2012-07-16 11:27:02 UTC 
Created attachment 598423 [details]
Screen log

Description of problem:
Having created a custom repository one is unable to assign to a custom CDS cluster because it is automatically assigned to the default cluster. Details attached in the screen log.

Version-Release number of selected component (if applicable):
RHEL-6.3-RHUI-2.1-20120705.0-Server-x86_64-DVD1.iso

How reproducible:
Always

Steps to Reproduce:
1. create a CDS cluster 
2. create a custom repository
3. try to assign the repository to the cluster
4. Info screen says: no repositories available for assignment
  
Actual results:
One can't assign a custom repository to a cluster of ones choice

Expected results:
Having created a custom repository one decides what cluster it should be assigned to

Additional info:
- see also screen log in the attachment
- most likely a duplicate of bug 840005
Comment 1 wes hayutin 2012-07-18 18:27:38 UTC 

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