Issue #855: Newest unit not published for each branch - OSTree Support - Pulp

Actions

Send by e-mail Copy link

Issue #855

closed

Newest unit not published for each branch

Added by jortel@redhat.com about 9 years ago. Updated about 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

jortel@redhat.com

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:

Sprint Candidate:

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.

Actions

Copy link

Updated by jortel@redhat.com about 9 years ago

Status changed from NEW to POST

https://github.com/pulp/pulp_ostree/pull/25

Actions

Copy link

Updated by jortel@redhat.com about 9 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.

Actions

Copy link