Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionCalvin 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:
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 17Satellite 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