Hide Forgot
Description of problem: Under certain scenarios, the promotions UI will expose the 'add' link for packages whose repository has not yet been promoted. Based on discussion, the expectation is that before a package can be promoted, the product or repo must first be promoted. Only once that occurs, should the user be able to promote future packages to the repo. Version-Release number of selected component (if applicable): git master How reproducible: always Steps to Reproduce: 1. create provider/product/repo (e.g. spacewalk/spacewalk_product/spacewalk_f14_repo) 2. sync the repo (spacewalk_f14_repo) 3. promote the spacewalk_product 4. add another repo to the above product (e.g. spacewalk_f15_repo) 5. sync the repo (spacewalk_f15_repo) 6. navigate to Content Management -> Promotions 7. create a changeset 8. in the left breadcrumb, navigate to Products -> spacewalk_product -> Packages Actual results: View that there are packages listed for the spacewalk_f15_repo with an '+Add' link next to them. Expected results: There should be no '+Add' link. Additional info:
mass move to CFSE product.
64943589b7f125f5d9c662d5306bcae982a8f4aa This commit merges in a branch where package search is enabled via elasticsearch and brings with it new checks on whether packages are actually promotable to the next environment. '+Add' showing up under the above scenario should no longer occur.
mass move ON_QA after brewing
Following the scenario above, I am now seeing packages from both repos I created -- in this case, rpmfusion free and rpmfusion free - updates. I promoted the former repo earlier, and as such, each package from that repo reads "Promoted" next to it, versus those from the latter repo. That said, I don't get +Add for any package, for any repo.
Verified with following CFSE build: [root@perceptor ~]# rpm -qa | grep -ie katello-0 -ie katello-cli-0 katello-0.1.304-1.el6.noarch katello-cli-0.1.105-1.el6.noarch [root@perceptor ~]# I created product 'pulp' and added 'pulp_64, pulp_86 repos. I synced these repo and promoted the 'pulp' product to next env. Later, I created pulp_f15 repo under pulp product and synced. Then created a changeset to add the packages from pulp_f15 repo. +Add was not there for pulp_f15 repo packages. Please see the attachment in next comment.
Created attachment 571352 [details] no +Add link for fedora packages, as this repo was added later
getting rid of 6.0.0 version since that doesn't exist