Bug 787719 - RHEL repos shouldn't be listed under custom repos
Summary: RHEL repos shouldn't be listed under custom repos
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: RHUA
Version: 2.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: James Slagle
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-06 15:31 UTC by Sachin Ghai
Modified: 2012-03-12 19:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-12 19:38:55 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Sachin Ghai 2012-02-06 15:31:49 UTC
Description of problem:
I added a RHUI 2.0 x86_64 and rhel6  repos. However when I list the repositories. I found the same repo was listed under 'Custom repositories'.

rhui (repo) => l

Custom Repositories
  Red Hat Enterprise Linux 6 Server (RPMs) from RHUI (6Server-i386)
  Red Hat Enterprise Linux 6 Server (RPMs) from RHUI (6Server-x86_64)
  Red Hat Update Infrastructure 2.0 (RPMs) (6Server-x86_64)

Red Hat Repositories
  Red Hat Enterprise Linux 6 Server (RPMs) from RHUI (6Server-i386)
  Red Hat Enterprise Linux 6 Server (RPMs) from RHUI (6Server-x86_64)
  Red Hat Update Infrastructure 2.0 (RPMs) (6Server-x86_64)


------------------------------------------------------------------------------
rhui (repo) => 



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


How reproducible:
always

Steps to Reproduce:
1. Add any rhel repo
2. List the rhui managed repo
3.
  
Actual results:
RHEL repos are listed under custom repos

Expected results:
RHEL repo's shouldn't be listed under custom repos section

Additional info:

Comment 1 Sachin Ghai 2012-02-06 15:35:41 UTC
Found it with following rhui iso:

RHEL-6.2-RHUI-2.0.2-20120203.1-Server-x86_64-DVD1.iso

Comment 2 James Slagle 2012-02-06 21:17:49 UTC
committed fix to rh-rhui-tools: 0c7277d4310ee95e2b5ad26a7c7b614885f835f9

Comment 3 James Slagle 2012-02-06 21:34:10 UTC
The fix has been built into a new rh-rhui-tools.  You can install it from:
http://download.devel.redhat.com/brewroot/packages/rh-rhui-tools/2.0.53/1.el6/noarch/rh-rhui-tools-2.0.53-1.el6.noarch.rpm

Comment 4 Sachin Ghai 2012-02-07 11:13:35 UTC
After updating the rh-rhui-tools rpm from the location in comment3,  I can see the repo listing correctly.

------------------------------------------------------------------------------
             -= Red Hat Update Infrastructure Management Tool =-


-= Repository Management =-

   l   list repositories currently managed by the RHUI
   i   display detailed information on a repository
   a   add a new Red Hat content repository
   c   create a new custom repository
   d   delete a repository from the RHUI
   u   upload content to a custom repository
   p   list packages in a repository

                                  Connected: dhcp201-142.englab.pnq.redhat.com
------------------------------------------------------------------------------
rhui (repo) => l

Custom Repositories
  pulp

Red Hat Repositories
  Red Hat Update Infrastructure 2.0 (RPMs) (6Server-x86_64)


------------------------------------------------------------------------------


Still keeping this on_qa, will retest this with new rhui ISO

Comment 5 Sachin Ghai 2012-02-10 09:53:00 UTC
Re-verified with new iso (RHEL-6.2-RHUI-2.0.2-20120209.0-Server-x86_64-DVD1.iso)

Now RHEL repo's are not listing under custom repo.
-
rhui (repo) => l

Custom Repositories
  pulp

Red Hat Repositories
  Red Hat Update Infrastructure 2.0 (RPMs) (6Server-i386)
  Red Hat Update Infrastructure 2.0 (RPMs) (6Server-x86_64)
  Red Hat Enterprise Linux 6 Server (RPMs) from RHUI (6Server-i386)
  Red Hat Enterprise Linux 6 Server (RPMs) from RHUI (6Server-x86_64)


------------------------------------------------------------------------------
rhui (repo) =>

Comment 6 James Slagle 2012-03-12 19:38:55 UTC
Released in RHUI 2.0.2


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