Project

Profile

Help

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 over 2 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 105
Quarter:

Description

Given the current workflow with katello:

  1. create a repository and a remote pointing to some upstream repo
  2. create a publication against version zero (timestamp in the repomd.xml file is CURRENT_TIME)
  3. distribute it
  4. configure a client to use the repo, yum repolist will show zero packages (as expected)
  5. Sync the repo with mirror=true
  6. distribute the newly created publication
  7. 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

Related to Pulp - Story #8856: As a user, I have a convenient UX for mirroring repositoriesCLOSED - DUPLICATE

Actions
Copied to RPM Support - Backport #9437: Backport #9402 "empty repos should be published with revision 0" to 3.14.zCLOSED - CURRENTRELEASEdalley

Actions

Also available in: Atom PDF