Project

Profile

Help

Issue #4345

Review behaviour when publishing empty repositories.

Added by quba42 over 2 years ago. Updated over 1 year ago.

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

Description

The current behaviour when publishing an empty repository (containing no packages) is for the pulp task to succeed without publishing anything.

We may want to review and improve this behaviour. Ideally, publishing an empty repository should create something that apt won't choke on.
Another possible use case is to ensure that pulp to pulp synchronization won't lead to a failed task.

While we are at it we may also want to consider whether there should be some kind of warning or error if an empty repository results from bad user input. The way things are now, if the user attempts to synchronize an upstream repository using for example bogus components, this will result in a successful sync with an empty repository. This may be counter intuitive for the user who has no indication what he did wrong.

Associated revisions

History

#1 Updated by bmbouter about 2 years ago

  • Tags Pulp 2 added

#2 Updated by mdellweg about 2 years ago

  • Triaged changed from No to Yes

#3 Updated by mdellweg almost 2 years ago

  • Status changed from NEW to POST
  • Assignee set to quba42

#4 Updated by ipanova@redhat.com over 1 year ago

  • Status changed from POST to MODIFIED
  • Platform Release set to 2.21.1

#5 Updated by ipanova@redhat.com over 1 year ago

  • Status changed from MODIFIED to 5

#6 Updated by ipanova@redhat.com over 1 year ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF