Bug 646976

Summary: Pulp Consumer List - Subscribed Repos shown incorrectly.
Product: [Retired] Pulp Reporter: Todd Sanders <tsanders>
Component: user-experienceAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED DUPLICATE QA Contact: Preethi Thomas <pthomas>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: jason.dobies
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-13 20:23:59 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:

Description Todd Sanders 2010-10-26 19:11:53 UTC
Description of problem:

1. Registered Consumer:

[master]$ pulp-admin consumer create --id tsanders-x201 --description 'This is my Pulp Server'
Successfully created consumer [ tsanders-x201 ]

2. List Consumers:

[master]$pulp-admin consumer list
+------------------------------------------+
           Consumer Information
+------------------------------------------+

Id                 tsanders-x201            
Description        This is my Pulp Server   
Subscribed Repos   /pulp/api/consumers/tsanders-x201/repoids/
Profile            https://tsanders-x201:443/pulp/api/consumers/tsanders-x201/package_profile/
Additional info    {}

It looks like we are trying to present the user with a properly formatted url to retrieve the subscribed repos.  I would prefer this to just list out the repos as part of this output, as I imagine the number of bound repos by a consumer will be a relatively small number (<10):

Subscribed Repos   fedora13-x86-releases, fedora13-x86-updates, 
                   fedora13-dell-firmware
      






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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jay Dobies 2011-01-13 20:23:59 UTC

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