Due to BZ 738657 pulp is making a change to require that if you manually add or remove a package or errata you much explicitly call /repositories/id/generate_metadata to update the metadata of the repository. This will hit on pulp version 238 most likely. We need to update promotions to handle this. irc log: prad | jsherrill, ping @jsherrill | prad: pong prad | jsherrill, hey just heads up on some of the selective sync changes i'm making on pulp | side .. if you're using add/remove on packages or errata you'll need to call | generate_metadata to update the underlying metadata prad | jsherrill, pulp's add/remove operations will only do associate/dis associations prad | jsherrill, you'll need to call POST /repositories/id/generate_metadata/ to update | repodata prad | after your selections are complete @jsherrill | prad: ahhh good to know, do you know what version of pulp this will take effect in? prad | jsherrill, should probably make it into tomorrows qe build so probably 238 or 239 prad | 237-2 is prospective CR.. so will be after that @jsherrill | prad: ok, i'll open a bug to track that prad | jsherrill, cool here is the pulp bug 738657 prad | jsherrill, and generate_metadata will created an async task in pulp and you get back a | task id jsherrill | prad: thx @jsherrill | prad: ah, k prad | jsherrill, so you can periodically check and show the metadata status
This is in the Pulp CR now. We should implement it.
Added into promotion in katello-0.1.209-1
please provide a CLI scenario how to reproduce the issue. thanks. (so far my tries to add an individual package to the changeset always bring in adding the whole repo content seems)
testing scenario: 1) create a product, add a repo 2) promote the product to next environment 3) sync the product 4) create a changeset, add a package, promote the changeset 5) check if metadata of the repo are updated
my issue is: not possible to add a single package - but all :) but any case - even with this I will check the bug. thanks.
You can add a package but it's repo and product must be promoted first. That's why I let empty repo to be promoted in the scenario above.
# VERIFIED Following the scenario in comment#5 (thanks a lot, Tomas) I confirm: repodata getting regenerated and the system that was registered is getting the packages (from errata as well) through yum successfully installed. I have used the famous zoo repo there :) Checked the scenario under version: --- katello-0.1.228-1.git.5.eabe87d.el6.noarch katello-cli-0.1.54-1.git.0.2670189.el6.noarch subscription-manager-0.99.6-1.el6.x86_64 pulp-0.0.265-1.el6.noarch candlepin-0.5.8-1.el6.noarch