Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1348572 - [RFE] Add installer support for max_speed on the yum-importer plugin
Summary: [RFE] Add installer support for max_speed on the yum-importer plugin
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.1.8
Hardware: x86_64
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Ondřej Pražák
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1120837 (view as bug list)
Depends On:
Blocks: sat-nextgen
TreeView+ depends on / blocked
 
Reported: 2016-06-21 13:25 UTC by Calvin Hartwell
Modified: 2021-12-10 14:40 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16253 0 Normal Resolved Add installer support for max_speed on the yum-importer plugin 2021-01-10 15:21:14 UTC
Pulp Redmine 2629 0 Normal CLOSED - WORKSFORME max_speed param does not work in yum_importer.json 2017-03-30 15:03:56 UTC
Red Hat Knowledge Base (Solution) 448713 0 None None None 2017-06-29 02:55:32 UTC
Red Hat Knowledge Base (Solution) 1224523 0 None None None 2017-05-30 13:18:10 UTC

Description Calvin Hartwell 2016-06-21 13:25:12 UTC 
Description of problem:

Customer has a requirement for using pulp max_speed option on the yum-importer plugin but it is not an option in the katello answers file or on the command line. Can we please add this as a supported option? 

Please see this case for docs bug: https://bugzilla.redhat.com/show_bug.cgi?id=1348570

To set, modify /etc/pulp/server/plugins.conf.d/yum_importer.json

and set: 

"max_speed": X 

where x is an integer of bytes per second (this needs to be confirmed by pulp developers as pulp manual and source code differ). 

Version-Release number of selected component (if applicable):

6.1.X 
6.2.X

How reproducible:

Easy to reproduce. 

Steps to Reproduce:
1. Run the katello/capsule installer and install product
2. Modify pulp config for max_speed option
3. Upgrade or modify product options through installer
4. Custom config for max_speed is removed. 

Actual results:

Customer cannot set max_speed without it being removed by installer. 

Expected results:

Customer should be able to set max_speed and keep the config consistent after upgrades/updates etc. 

Additional info:
Comment 7 Stephen Benjamin 2016-08-23 17:26:42 UTC 
Created redmine issue http://projects.theforeman.org/issues/16253 from this bug
Comment 9 pulp-infra@redhat.com 2017-03-13 20:01:49 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 10 pulp-infra@redhat.com 2017-03-13 20:01:52 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 11 Satellite Program 2017-03-14 04:18:38 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16253 has been resolved.
Comment 12 pulp-infra@redhat.com 2017-03-29 17:33:16 UTC 
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 13 pulp-infra@redhat.com 2017-03-30 15:03:57 UTC 
The Pulp upstream bug status is at CLOSED - WORKSFORME. Updating the external tracker on this bug.
Comment 14 Sean O'Keeffe 2017-05-30 13:18:10 UTC 
*** Bug 1120837 has been marked as a duplicate of this bug. ***
Comment 15 Ondřej Pražák 2017-08-23 08:21:41 UTC 
Verified.

6.3.0 snap 12
Comment 16 Ondřej Pražák 2017-08-23 13:12:30 UTC 
Verification steps:

1) satellite-installer --scenario satellite
2) grep max_speed /etc/pulp/server/plugins.conf.d/yum_importer.json
3) satellite-installer --katello-pulp-max-speed 1GB
4) repeat step 2), max speed will not be null
Comment 17 Satellite Program 2018-02-21 16:54:17 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> 
> For information on the advisory, and where to find the updated files, follow the link below.
> 
> If the solution does not work for you, open a new bug report.
> 
> https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.