Project

Profile

Help

Story #4668

As a user i can instruct a sync to abort early, when diskspace is tight

Added by mdellweg almost 2 years ago. Updated almost 2 years ago.

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

0%

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

Description

It would be nice, if the sync mechanism, after reading the metadata could anticipate the (possibly) needed diskspace, compare that to the available and take appropriate action before starting to download the content units.

Another option might be to add a "fake_sync" or "dry_run_sync" that reports, whether disk space is sufficient.

History

#1 Updated by bmbouter almost 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

#2 Updated by bmbouter almost 2 years ago

If this is for Pulp3 please reopen.

#3 Updated by bmbouter almost 2 years ago

  • Tags Pulp 2 added

#4 Updated by mdellweg almost 2 years ago

  • Tags Pulp 3 added
  • Tags deleted (Pulp 2)

#5 Updated by mdellweg almost 2 years ago

I cannot reopen this.

#6 Updated by daviddavis almost 2 years ago

  • Sprint/Milestone set to 3.0.0

#7 Updated by bmbouter almost 2 years ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF