Bug 755675

Summary:	New repo added to product does not show up at RHSM client end
Product:	Red Hat Satellite	Reporter:	Jeff Weiss <jweiss>
Component:	Subscription Management	Assignee:	Tomas Strachota <tstrachota>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Og Maciel <omaciel>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	dajohnso, dgoodwin, gkhachik, omaciel
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	candlepin-0.5.20-1, subscription-manager-0.99.6-1, katello-0.1.242-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-22 18:08:05 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:
Bug Depends On:
Bug Blocks:	747354, 755097

Description Jeff Weiss 2011-11-21 18:10:04 UTC

Description of problem:


Version-Release number of selected component (if applicable):
katello-0.1.111-2.el6.x86_64

How reproducible:


Steps to Reproduce:
1. Create a product, add 1 repo. 
2. Sync the repo
3. Promote the product to 1st env
4. Register a client to first env, subscribe to product
5. Create a 2nd repo in the product, sync it
6. Promote the product from locker to first env again

  
Actual results:
On the client end, yum repolist does not show the new repo.  No amount of refreshing will help, short of unsubscribing and resubscribing to the product.

Expected results:
Repo should just show up in 'yum repolist' without having to do anything else on the client end.

Additional info:

Comment 5 Tomas Strachota 2012-02-20 13:07:34 UTC

*** Bug 790616 has been marked as a duplicate of this bug. ***

Comment 6 Og Maciel 2012-02-22 18:16:02 UTC

This doesn't work with RH providers. As per conversation with Tomas, re-assigning it.

Comment 8 Og Maciel 2012-02-27 15:39:53 UTC

Saw the same behavior but using a RHEL custom content (not from manifest). If I subscribed my system to anything other than RHEL content, my client's repo file got updated, but the moment I added a RHEL content, the repo file did not add it in the client.

Comment 9 Og Maciel 2012-02-27 18:26:55 UTC

Please disregard my comment. Apparently I confused myself with all the numerous promotions I did the day before and forgot to promote this new content to my environment. As the web ui does not prevent me from subscribing to content that is not promoted to an environment (see BZ 797242), I was confused.

Comment 10 Og Maciel 2012-03-01 01:58:33 UTC

Validated:
* candlepin-0.5.23-1.el6.noarch
* candlepin-tomcat6-0.5.23-1.el6.noarch
* katello-0.1.300-1.el6.noarch
* katello-all-0.1.300-1.el6.noarch
* katello-certs-tools-1.0.2-2.el6.noarch
* katello-cli-0.1.100-2.el6.noarch
* katello-cli-common-0.1.100-2.el6.noarch
* katello-common-0.1.300-1.el6.noarch
* katello-configure-0.1.100-7.el6.noarch
* katello-glue-candlepin-0.1.300-1.el6.noarch
* katello-glue-foreman-0.1.300-1.el6.noarch
* katello-glue-pulp-0.1.300-1.el6.noarch
* katello-httpd-ssl-key-pair-1.0-1.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-repos-0.1.5-1.el6.noarch
* katello-selinux-0.1.7-1.el6.noarch
* katello-trusted-ssl-cert-1.0-1.noarch
* pulp-1.0.0-4.el6.noarch
* pulp-common-1.0.0-4.el6.noarch
* pulp-selinux-server-1.0.0-4.el6.noarch