Project

Profile

Help

Story #8673

Auto-publishing should be more fault-tolerant

Added by sskracic@redhat.com 12 days ago. Updated 12 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

I admit the title is a bit vague.

During auto-publishing sync of a very large repository (rhel-7-server-rpms), the rq process got killed by oom-killer sometime in the middle of the publishing step. So the new repository version (1) got created, but accompanying publication did not.

On the subsequent sync runs, the repository did not get published, as no new content was available to sync, hence a new repository version was not created, which in turn should trigger publication and distribution update.

Of course, the repo can still be published and distributed using the non-autopublishing REST API, but I wonder whether the behavior was intended.

Please register to edit this issue

Also available in: Atom PDF