Issue #9402: creating an empty publication before syncing with mirror=true could cause clients to refuse to use metadata - RPM Support - Pulp

Actions

Send by e-mail Copy link

Issue #9402

closed

creating an empty publication before syncing with mirror=true could cause clients to refuse to use metadata

Added by jsherril@redhat.com about 3 years ago. Updated about 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

dalley

Sprint/Milestone:

3.16.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Katello

Sprint:

Sprint 105

Quarter:

Description

Given the current workflow with katello:

create a repository and a remote pointing to some upstream repo
create a publication against version zero (timestamp in the repomd.xml file is CURRENT_TIME)
distribute it
configure a client to use the repo, yum repolist will show zero packages (as expected)
Sync the repo with mirror=true
distribute the newly created publication
run yum repolist on the client

The client will refuse to pull down new metadata becuase the new metadata has an older timestamp than the original empty metadata.

A likely solution is to support specifying a repomd.xml timestamp when creating a publication.

Related issues

Actions

Copy link

Updated by dalley about 3 years ago

Related to Story #8856: As a user, I have a convenient UX for mirroring repositories added

Actions

Copy link

Updated by dalley about 3 years ago

Triaged changed from No to Yes

The way we'll probably fix this long-term is by bifurcating "repositories" into repositories which are exact clones of the upstream ones, like Katello library repos, and managed repos.

Clone repos can't be modified or published, and managed repos can't be synced against remotes. See for more details: https://pulp.plan.io/issues/8856

In the meantime we can only really mitigate this issue by (having Katello) not publish, or having a special case which uses a revision of 0 if the repository is going to be empty (no packages), which will resolve the issue in one particular case. Generally speaking if the repo is flipping between mirror and non-mirror, there is not a lot we can do.

Actions

Copy link