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:
Created redmine issue http://projects.theforeman.org/issues/16253 from this bug
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16253 has been resolved.
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - WORKSFORME. Updating the external tracker on this bug.
*** Bug 1120837 has been marked as a duplicate of this bug. ***
Verified. 6.3.0 snap 12
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
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