Bug 1348572

Summary:	[RFE] Add installer support for max_speed on the yum-importer plugin
Product:	Red Hat Satellite	Reporter:	Calvin Hartwell <chartwel>
Component:	Installation	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED ERRATA	QA Contact:	Ondřej Pražák <oprazak>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.1.8	CC:	bbuckingham, bmbouter, brubisch, chrobert, daviddavis, dkliban, ggainey, ipanova, mhrivnak, omaciel, oprazak, pcreech, pdwyer, rchan, rjerrido, stbenjam, ttereshc
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
URL:	http://projects.theforeman.org/issues/16253
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:54:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	672946

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