Project

Profile

Help

Issue #855

Newest unit not published for each branch

Added by jortel@redhat.com over 6 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version - OSTree:
Platform Release:
Target Release - OSTree:
1.0.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

When a repository contains multiple units for a branch, it needs to publish the newest unit. The problem is that the publisher is using the wrong sort keyword in the criteria for the 'created' field.

Steps to reproduce:

1. Compose an ostree.
2. Create an ostree repository and sync with the remote.
3. Compose a newer tree.
4. Sync with pulp repository.
5. Ensure the newest unit is published.

History

#1 Updated by jortel@redhat.com over 6 years ago

  • Status changed from NEW to POST

#2 Updated by jortel@redhat.com over 6 years ago

  • Status changed from POST to ASSIGNED

The _id on content units is a plain UUID instead of ObjectID. Adding a created property to OSTree units. This is a stopgap until the unit model can be fixed. Moving back to ASSIGNED.

#3 Updated by jortel@redhat.com over 6 years ago

  • Status changed from ASSIGNED to POST

#4 Updated by jortel@redhat.com over 6 years ago

  • Status changed from POST to MODIFIED

#5 Updated by dkliban@redhat.com over 6 years ago

  • Target Release - OSTree set to master

#6 Updated by dkliban@redhat.com over 6 years ago

  • Status changed from MODIFIED to 5

#7 Updated by rbarlow almost 6 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
  • Target Release - OSTree changed from master to 1.0.0

#8 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF