Bug 1274725

Summary:	Last 5% of fusor-installer feels like it takes almost as long as 0 - 95%
Product:	Red Hat Satellite	Reporter:	Jason Montleon <jmontleo>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	low	Docs Contact:
Priority:	high
Version:	6.1.0	CC:	bkearney, dajohnso, ehelms, jcallaha, jmatthew, jmontleo, mbacovsk, mreid, rohoover
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1266241	Environment:
Last Closed:	2017-08-01 19:57:48 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:	1266241

Description Jason Montleon 2015-10-23 12:59:31 UTC

+++ This bug was initially created as a clone of Bug #1266241 +++

Description of problem:
I don't have timings around this, but the last 5% or so of fusor-installer took much longer than I would have expected, given how long it took to get to 95%. Feels like it took almost as long to do the last 5% as it did to go from 0 - 95%. Is it all one task, or a number of things that are left to do at that point? 

Not sure where the % progress comes from, but it might help ease expectations if the last few things it did accounted for more of the overall progress, since they seem to take longer.

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

Additional info:

--- Additional comment from John Matthews on 2015-10-13 14:21:57 EDT ---

Let's look into different task weights to give this a better feel.

--- Additional comment from Jason Montleon on 2015-10-23 08:42:46 EDT ---

This probably goes back to katello-installer/foreman-installer behavior and it is not specific to fusor-installer. rake tasks like db:migrate, etc, are running at the end of the install and these are what is being waited on for so long.

Comment 2 Martin Bacovsky 2016-04-21 11:51:26 UTC

1/ The process duration is estimated from count of resources in puppet plan. The real number of resources processed may differ based on installer options and puppet version used. 

2/ Also the duration of the steps may differ significantly. As it was said above db migrations, seeds, cache population and others is done at the end of installation and all of them are long running tasks.

3/ Also when the estimate was lower then the real result, which is common, all the extra tasks are executed at 99% to avoid exceeding 100%.

As a solution we can probably address 3/ by multiplying the estimate by some arbitrary ratio to avoid waiting at 99%. Assuming that eventual skip from 95% to 100% is more acceptable for the user. To address 2/ some kind of weighting could be added, but it is unlikely to get in in 6.2 timeframe.

Comment 3 Bryan Kearney 2016-04-21 11:54:07 UTC

Created redmine issue http://projects.theforeman.org/issues/14753 from this bug

Comment 4 Bryan Kearney 2016-05-23 14:09:53 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/12166 has been closed

Comment 6 Bryan Kearney 2017-08-01 19:57:48 UTC

The fix to this bug will be delivered with release 6.3 of Satellite.