Hide Forgot
Description of problem: Removing the single repo from the changeset content seems however replicates the repo content to the next environment during changeset promote. Version-Release number of selected component (if applicable): katello-0.1.212-1.git.0.a584b15.el6.noarch katello-cli-0.1.50-1.git.0.e68e844.el6.noarch How reproducible: always Steps to Reproduce: 1.create an env for the ACME_Corporation (e.g.: dev) 2.make a product/repo. Sync the content (let's say pulp rhel6) 3.create changeset for that dev environment 4.update the changeset and add the product 5.do the second update: changeset update --from_product local-katello --remove_repo myrepo --name cs_dev --environment dev (remove the repo) 6. do the changeset promote Actual results: the repo and all packages in there are being promoted to the dev (package list --environment dev; repo list --environment dev) - shows content Expected results: no repo / package info for that environment. Additional info:
@bk - what is the expected behavior in this case? a) Not to allow removal of a repo that was included in a product. b) Change the promotion logic - have a list of "removed" repos that are still there as products.
Just a note: In changeset update cli we copy the ui approach. You can add/remove whole product. You cannot add a product and restrict it with removing single repos. You would have to add the product repos to a new changeset one by one. The parameter --from_product is probably quite misleading here. It's there to specify what product the repo (or other content items) we want to add/remove belongs to. I admit that in context with the verb 'remove' it really sounds like it is possible to filter the product.
Agree.. this is consitent with my understanding. If you have the product assigned, the repos have no effect. Tomas, you can close this.