+++ This bug was initially created as a clone of Bug #1315752 +++ Version-Release number of selected component (if applicable): 6.3.0 snap13 pulp 2.13.3-1 on sat and capsule How reproducible: Always Steps to Reproduce: 1. Create a yum repo with the on_demand download policy 2. Assign the repo to a capsule through repo-content view-lifecycle environment relations 3. Sync the repo 4. Switch the download policy to immediate 5. Sync the repo 6. Wait till capsule sync finishes Actual results: None of the rpms are downloaded Expected results: Rpms get downloaded to disk Additional info: switching from on demand to 'background' and syncing does cause them to be synced in the background.
Original issue was fixed in 6.2 and we have auto test for it (511b531d-1fbe-4d64-ae31-0f9eb6625e7f). When porting the test to 6.3 automation uncovered the issue is still reproducible for 6.3 despite Bug #1315752 had sat-6.3.0 flag set to "+". Please note that the issue is only reproducible on a capsule, satellite correctly downloads rpms after update but capsule doesn't.
In 6.3 we added the concept of a download policy setting for each capsule. This allows you to have a capsule use on_demand for all repos syncing to that capsule. This is now the default setting for new capsules. So if you installed a fresh capsule on a 6.3 satellite and left the download policy to the default value (on demand), the behavior you describe is expected. If you would like to use the old behavior, you can simply visit Infrastructure > Capsules > select your capsule > click edit and change the download policy to "Inherit". this will cause the capsule to use the same download policy as the repository on the satellite for each repository.
Thanks, Justin, I've just tried and it works correctly. I wasn't aware of such change. Closing BZ as it's expected behavior.