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.
If you promote a product from the Locker to the 1st environment and then come back later and re-promote that product again you won't see any calls to sync the cloned repositories from that product in the 1st environment.
This is needed to mass sync any new content from the Product in the Locker into the target environment. Otherwise the user has to selectively find things that are new and manually promote them.
Example:
1) Setup
Locker -> DEV
ProdA
2) Promote
Locker -> DEV
ProdA -> ProdA-clone
3) re-sync new content to Locker that ends up in ProdA
4) Create new changeset for Locker -> DEV and add ProdA
5) Promote changeset
In the above case there aren't any calls to sync ProdA-clone and the new content that landed in step 3) never shows up in DEV.
Verified with following katello build:
[root@dhcp201-167 repo]# rpm -qa | grep katello
katello-cli-0.1.5-1.git.15.654a7df.fc15.noarch
katello-0.1.70-1.git.7.ca8d03c.fc15.noarch
I created a repo and then promote it from 'Locker' to Dev.
Then later added few more updates in that repo and again created a new changeset to promote that from 'Locker to 'dev'.
Locker ==> Dev
prodA ==> ProdA_clone.
Added updates in prodA and Created a new changeset.
Locker ==> Dev
prodA ==>prodA_clone
I can see newly added updates in the Dev and under the prodA_clone.