Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #2187

closed

rsync as predistributor logic is wrong

Added by dkliban@redhat.com over 7 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
dkliban@redhat.com
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.10.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Docker web distributor publishes without regard for predistributor publish history when publishing for the very first time. Here is a snippet from the test plan for this feature:

# remove all content from remote server
rm -rf /root/dir/on/remote/*
# remove all locally published docker content
rm -rf /var/lib/pulp/published/docker

# create docker repo to sync v2 content
pulp-admin docker repo create --feed http://127.0.0.1:5000 --upstream-name ubuntu --repo-id mydocker-repo --auto-publish false

# sync the v2 content
pulp-admin docker repo sync run --repo-id mydocker-repo
# validate that an auto publish did not occur (on local pulp install, not remote)

# add rsync distributor
http --verify no --auth admin:admin POST https://localhost/pulp/api/v2/repositories/mydocker-repo/distributors/ < docker_rsync_distributor_config.json

# publish using web distributor with rsync distributor defined as the predistributor
http --verify no --auth admin:admin POST https://localhost/pulp/api/v2/repositories/mydocker-repo/actions/publish/ < publish_docker_with_predistributor.json

# verify that the publish is skipped in the task details because the rsync predistributor has not published yet

The publish is not skipped. Though no units are actually published because the publisher does check the publish history of predistributor.

Actions
Send by e-mail Copy link

Also available in: Atom PDF