Test #4442
closed
Test different code paths
Description
Different code paths are used in Pulp for the cases when artifacts are already present on the filesystem during sync and when they are not downloaded yet.
It probably makes sense to test 2 subsequent syncs of the same repo with immediate policy (doesn't matter which plugin) to be sure that second one is fine.
1. no content from repo A is downloaded
2. sync/publish repo A with download policy immediate
3. sync/publish repo A (or any other repo which has at least one artifact from repo A) again with download policy immediate
No failure in 2 shows that sync went fine when content was not present on the disk and in the DB.
No failure in 3 shows that sync went fine when content was already present on the disk and in the DB.
Added by kersom almost 5 years ago
Added by kersom almost 5 years ago
Add test to verify sync/publish content already in pulp
Add test to verify how pulp handles sync/publish of content already on filesystem and database.
Updated by kersom almost 5 years ago
- Status changed from NEW to MODIFIED
Applied in changeset pulp|ed8ba2ded760455f632161ba9068bd33daa86562.
Updated by kersom over 4 years ago
- Status changed from MODIFIED to CLOSED - COMPLETE
.
Add test to verify sync/publish content already in pulp
Add test to verify how pulp handles sync/publish of content already on filesystem and database.
https://pulp.plan.io/issues/4442 closes: #4442