Project

Profile

Help

Test #4442

Test different code paths

Added by kersom 8 months ago. Updated 6 months ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Version:
Platform Release:
Tags:
Sprint:

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.

Associated revisions

Revision ed8ba2de View on GitHub
Added by kersom 8 months 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.

https://pulp.plan.io/issues/4442
closes: #4442

Revision ed8ba2de View on GitHub
Added by kersom 8 months 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.

https://pulp.plan.io/issues/4442
closes: #4442

History

#1 Updated by kersom 8 months ago

  • Description updated (diff)

#2 Updated by kersom 8 months ago

  • Assignee set to kersom

#3 Updated by kersom 8 months ago

  • Status changed from NEW to MODIFIED

#4 Updated by kersom 7 months ago

  • Status changed from MODIFIED to CLOSED - COMPLETE

#5 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF