Red Hat Bugzilla – Bug 1266241
Last 5% of fusor-installer feels like it takes almost as long as 0 - 95%
Last modified: 2016-09-23 14:50:21 EDT
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):
Let's look into different task weights to give this a better feel.
This probably goes back to katello-installer/foreman-installer behavior and I 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.
This Bug is dependant on an upstream foreman-kafo issue:
The kafo installer (which katello-installer adds on to, and fusor-installer adds on to that) calculates progress by simply calculating #-printed-puppet-lines / #-expected-puppet-lines. There is currently no mechanism to specify that one puppet line is much longer than others.
We may have trimmed some time off of the seeding process as it appears it was unnecessarily running an extra rake db:seed and rake db:migrate which both take a fair amount of time. In combination with the foreman-installer changes coming hopefully we can get a taskbar that better represents progress as well.