Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #1847

closed

last_unit_added is not added in mongo repo collection records

Added by ipanova@redhat.com over 8 years ago. Updated over 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
bizhang
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.8.0
Platform Release:
2.11.2
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 13
Quarter:

Description

If some units got removed from the repo, the last_unit_removed will be updated in the mongo data, but if a unit was added 'last_unit_added' will be still missing

> db.repos.find()
{ "_id" : ObjectId("5710f3da45ef48069a4dd985"), "_ns" : "repos", "content_unit_counts" : { "rpm" : 2 }, "last_unit_removed" : ISODate("2016-04-15T14:09:12.992Z"), "notes" : { "_repo-type" : "rpm-repo" }, "repo_id" : "repo", "scratchpad" : {  } }

Related issues

Has duplicate Pulp - Issue #2499: 'Last Unit Added' attribute not updatedCLOSED - DUPLICATEActions
Actions
Copy link
 #1

Updated by ipanova@redhat.com over 8 years ago

  • Project changed from RPM Support to Pulp
  • Version set to 2.8.0
Actions
Copy link
 #2

Updated by ipanova@redhat.com over 8 years ago

  • Blocks Story #1724: Publish should be a no-op if no units and no settings have changed since the last successful publish added
Actions
Copy link
 #3

Updated by bmbouter over 8 years ago

Did last_unit_added exist before?

If you have a datetime and want to find if a unit was created or updated since then you could query on the RepositoryContentUnit model updated field[0]:

RepositoryContentUnit.objects.filter(repo_id=repo_id, updated_gt=the_timestamp)

You could use count() to determine how many there were without actually pulling the documents into memory.

[0]: https://github.com/pulp/pulp/blob/1503f2772aee59d30621b58582ea997feb28fb41/server/pulp/server/db/model/__init__.py#L199-L208

Actions
Copy link
 #4

Updated by mhrivnak over 8 years ago

  • Triaged changed from No to Yes
Actions
Copy link
 #5

Updated by ipanova@redhat.com over 8 years ago

With bmbouter suggestion i managed to find the other way of implementation, so this issue is not a blocker for #1724 anymore

Actions
Copy link
 #6

Updated by ipanova@redhat.com over 8 years ago

  • Blocks deleted (Story #1724: Publish should be a no-op if no units and no settings have changed since the last successful publish)
Actions
Copy link
 #7

Updated by ttereshc about 8 years ago

  • Has duplicate Issue #2499: 'Last Unit Added' attribute not updated added
Actions
Copy link
 #8

Updated by bizhang about 8 years ago

  • Sprint/Milestone set to 31
  • Severity changed from 2. Medium to 3. High
Actions
Copy link
 #9

Updated by bizhang almost 8 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bizhang
Actions
Copy link
 #10

Updated by bizhang almost 8 years ago

  • Status changed from ASSIGNED to POST

Added by bizhang almost 8 years ago

Revision 0a1c14ee | View on GitHub

Update last_unit_added when unit is imported to repo.

closes #1847 https://pulp.plan.io/issues/1847

Added by bizhang almost 8 years ago

Revision 0a1c14ee | View on GitHub

Update last_unit_added when unit is imported to repo.

closes #1847 https://pulp.plan.io/issues/1847

Actions
Copy link
 #12

Updated by bizhang almost 8 years ago

  • Status changed from POST to MODIFIED
Actions
Copy link
 #13

Updated by semyers almost 8 years ago

  • Platform Release set to 2.11.2
Actions
Copy link
 #14

Updated by semyers almost 8 years ago

  • Status changed from MODIFIED to 5
Actions
Copy link
 #15

Updated by semyers almost 8 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
Copy link
 #16

Updated by bmbouter almost 7 years ago

  • Sprint set to Sprint 13
Actions
Copy link
 #17

Updated by bmbouter almost 7 years ago

  • Sprint/Milestone deleted (31)
Actions
Copy link
 #18

Updated by bmbouter over 5 years ago

  • Tags Pulp 2 added
Actions
Send by e-mail Copy link

Also available in: Atom PDF