Project

Profile

Help

Story #8658

closed

As a user I want to purge individual orphan or list of orphans

Added by ipanova@redhat.com over 1 year ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
GalaxyNG
Sprint:
Quarter:

Description

http POST :24817/pulp/api/v3/orphans/ content_hrefs:= []

Enable a POST call to the orphans endpoint that would accept a list of content_hrefs to purge.

  1. A task will be triggered and will call into orphan_cleanup(). Instead of looking for all of the orphaned content across pulp , it would just instead work with the list if hrefs provided( in case the list of content_hrefs was provided).
  2. The timestamp_of_interest on the content will be honored and if there was specified a Content unit that is not an orphan - it will be ignored.
  3. Only content that has version_memberships__isnull=True will be purged.
Actions #1

Updated by ipanova@redhat.com over 1 year ago

  • Description updated (diff)
Actions #2

Updated by ipanova@redhat.com over 1 year ago

  • Description updated (diff)
Actions #3

Updated by ipanova@redhat.com over 1 year ago

  • Tracker changed from Issue to Story
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)
Actions #4

Updated by daviddavis over 1 year ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

Grooming per our pulpcore team meeting today.

Actions #5

Updated by bmbouter over 1 year ago

Maybe a silly question, but why wouldn't a user want all orphans removed?

Actions #6

Updated by ipanova@redhat.com over 1 year ago

bmbouter wrote:

Maybe a silly question, but why wouldn't a user want all orphans removed?

In case a user has installed more than one plugin and he wants to remove one specific rpm package( for example), all other content types, including the ones from the other plugins would be cleaned up as well. This outcome might be undesirable.

Actions #7

Updated by ipanova@redhat.com over 1 year ago

  • Tags GalaxyNG added
Actions #8

Updated by bmbouter over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bmbouter
Actions #9

Updated by ipanova@redhat.com over 1 year ago

  • Sprint/Milestone set to Content/disk space management
Actions #10

Updated by pulpbot over 1 year ago

  • Status changed from ASSIGNED to POST
Actions #11

Updated by ipanova@redhat.com over 1 year ago

  • Sprint/Milestone changed from Content/disk space management to 3.14.0

Added by bmbouter over 1 year ago

Revision 8ad6aca9

Adds /pulp/api/v3/orphans/cleanup/

This adds a new endpoint /pulp/api/v3/orphans/cleanup/. When called with POST and no parameters it is equivalent to calling DELETE /pulp/api/v3/orphans/. Additionally the optional parameter content_hrefs can be specified and must contain a list of content hrefs. When content_hrefs is specified, only those content units will be considered to be removed by orphan cleanup.

closes #8658

Actions #12

Updated by bmbouter over 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #13

Updated by pulpbot over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF