Bug 1426401

Summary:	"hammer repository upload-content --path" redundantly non-performant against big repos
Product:	Red Hat Satellite	Reporter:	Satellite Program <pm-sat>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Jitendra Yejare <jyejare>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2.5	CC:	bbuckingham, bkearney, jcallaha, jsherril, jyejare, pmoravec, tstrachota
Target Milestone:	Unspecified	Keywords:	Performance, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1402423	Environment:
Last Closed:	2018-02-21 16:54:17 UTC	Type:	---
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:	1402423
Bug Blocks:

Comment 2 Jitendra Yejare 2018-01-09 06:11:16 UTC

Verified!

@ Satellite 6.3 snap 31

Steps:
1. Upload bulk(500) rpms through hammer.
2. Observe Time taken

Observation:

1. This bug was initially created in 6.2 while it was taking 31.6 minutes to upload 500 rpms. But Now it takes 25mintes to upload 500 rpms which are some of earlier rpms and some are new. So there are signs of good performance than earlier.

2. 

Successfully uploaded file 'bff-foo-21bee-1-1.fc21.x86_64.rpm'.
Successfully uploaded file 'bff-foo-95415-1-1.fc21.x86_64.rpm'.

real	25m6.315s
user	0m17.588s
sys	0m2.141s


2. Also there isn't a publish task 'DistributorPublish' ran in ImportUpload:
Actions::Pulp::Repository::ImportUpload (success) [ 0.69s / 0.18s ]
Actions::Katello::Repository::FilteredIndexContent (success) [ 0.10s / 0.10s ]
Actions::Katello::Repository::ImportUpload (success) [ 0.01s / 0.01s ] 

3. There isn't a failure in rpms upload, all 500 rpms are uploaded.

So changing the state to Verified.

Comment 3 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