Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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.
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.