Project

Profile

Help

Backport #9610

closed

backport to 2.8: Enable rate_limit option during container sync from remote registry

Added by ipanova@redhat.com 6 months ago. Updated 6 months ago.

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

100%

Estimated time:
Triaged:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 111
Quarter:


Related issues

Copied from Container Support - Story #9607: Enable rate_limit option during container sync from remote registryCLOSED - CURRENTRELEASEipanova@redhat.com

Actions
Copied to Container Support - Backport #9611: backport to 2.5: Enable rate_limit option during container sync from remote registryCLOSED - WONTFIXipanova@redhat.com

Actions
Actions #1

Updated by ipanova@redhat.com 6 months ago

  • Copied from Story #9607: Enable rate_limit option during container sync from remote registry added
Actions #2

Updated by ipanova@redhat.com 6 months ago

  • Copied to Backport #9611: backport to 2.5: Enable rate_limit option during container sync from remote registry added
Actions #3

Updated by ipanova@redhat.com 6 months ago

  • Sprint/Milestone set to 2.8.3
Actions #4

Updated by ipanova@redhat.com 6 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ipanova@redhat.com
  • Sprint set to Sprint 111
Actions #5

Updated by pulpbot 6 months ago

  • Status changed from ASSIGNED to POST

Added by ipanova@redhat.com 6 months ago

Revision ba56007c

Fixed rate_limit option on the remote.

backports #9607 closes #9610

(cherry picked from commit 39b3000150960c554d2124ab3654e3e7b4c54352)

Actions #6

Updated by ipanova@redhat.com 6 months ago

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

Updated by pulpbot 6 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF