Bug 1448549

Summary:	Time between submit one errata via webUI and the installation start on the content host
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Performance	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.8	CC:	inecas
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-05 18:20:13 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:

Description Waldirio M Pinheiro 2017-05-05 17:40:21 UTC

Description of problem:
Long time to start the execution after submit via webIU the errata application

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

How reproducible:
100%

Steps to Reproduce:


Environment

Satellite 6.2.8

Clients
RHEL 7.2

3 Content Hosts
 - node01.domain
 - node02.domain
 - node03.domain
 

Ok, tasks submited to 3 content hosts via host collection to install Erratas *average of 150* and at the end we are able to collect the info below from each task.

	node01
		- Start at: 2017-05-05 11:26:58 -0300 
		- Ended at: 2017-05-05 11:48:22 -0300 
		
	node02
		- Start at: 2017-05-05 11:26:59 -0300 
		- Ended at: 2017-05-05 11:51:30 -0300 
		
	node03
		-  Start at: 2017-05-05 11:27:00 -0300 
		-  Ended at: 2017-05-05 11:49:27 -0300 
		

Now on each content host I collect the information about the package installation via *yum history info*

	node01
		- Begin time     : Fri May  5 10:43:01 2017
		- End time       :            10:48:13 2017 (5 minutes)
		
	node02
		- Begin time     : Fri May  5 10:46:17 2017
		- End time       :            10:51:10 2017 (293 seconds)
		
	node03
		- Begin time     : Fri May  5 10:42:57 2017
		- End time       :            10:49:14 2017 (6 minutes)



So the question is, could we improve the time between submit the task and the same start on the client ?

	node01
		- Submited *2017-05-05 11:26:58 -0300*, started on the content host *Fri May  5 10:43:01 2017* =~ 16 min to start in the content host
	node02
		- Submited *2017-05-05 11:26:59 -0300*, started on the content host *Fri May  5 10:46:17 2017* =~ 19 min to start in the content host
	node03
		- Submited *2017-05-05 11:27:00 -0300*, started on the content host *Fri May  5 10:42:57 2017* =~ 15 min to start in the content host

I'll update my Satellite to 6.2.9 and rerun the same test.

PS: My fear is, when customer increase this number of content host, what will be the time to start the process on each one ? like 500 Content Hosts, 1k Content Hosts at the same time. Not sure if QA team have this number.

Actual results:


Expected results:


Additional info:

Comment 1 Waldirio M Pinheiro 2017-05-05 17:46:26 UTC

Ivan,

To be more effective, the # of packages

// node01
---
ID     | Login user               | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
    10 | System <unset>           | 2017-05-05 10:43 | I, U           |  146 EE
---

// node02
---
ID     | Login user               | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
     6 | System <unset>           | 2017-05-05 10:46 | I, U           |  201 EE
---

// node03
---
ID     | Login user               | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
     6 | System <unset>           | 2017-05-05 10:42 | I, U           |  215 EE
---

Comment 2 Waldirio M Pinheiro 2017-05-05 17:59:41 UTC

Hi

Yet on Sat 6.2.8 when installing just one errata on node01.domain I can see

// On Satellite side *tasks*
 Start at: 2017-05-05 14:42:00 -0300 
 Ended at: 2017-05-05 14:42:11 -0300 

// On content host side *yum history info*
Begin time     : Fri May  5 13:42:11 2017
End time       :            13:42:13 2017 (2 seconds)

Then with one package we can see like ~10 seconds to start and 2 to conclude.


Best Regards
Waldirio M Pinheiro | Senior Software Maintenance Engineer

Comment 3 Waldirio M Pinheiro 2017-05-05 18:20:13 UTC


*** This bug has been marked as a duplicate of bug 1290867 ***