progress bar immediately jumped to 42%

[Mike Scherbakov]

Build #461
I've ran fuel-createrepo in ordet to get all repos on master node first, then started deployment of Ubuntu env. Progress bar immediately jumped to 42%, while I'd expect it to be more gradual.

[Vladimir Sharshov (vsharshov)]

Closed as invalid because of plan to reimplement this: https://blueprints.launchpad.net/fuel/+spec/progress-bar-based-on-tasks

[Vladimir Sharshov (vsharshov)]

I suggest move it to 8.0, because this bug covered by https://blueprints.launchpad.net/fuel/+spec/progress-bar-based-on-tasks.

Also discovering log i could not confirm immediately jump to 42%:

2015-05-24T19:28:03 debug: [684] Data received by ProvisiningProxyReporter to report it up: {"nodes"=>[{"uid"=>"1", "progress"=>4, "status"=>"provisioning"}, {"uid"=>"2", "progress"=>4, "status"=>"provisioning"}, {"uid"=>"3", "progress"=>4, "status"=>"provisioning"}, {"uid"=>"4", "progress"=>4, "status"=>"provisioning"}, {"uid"=>"5", "progress"=>4, "status"=>"provisioning"}, {"uid"=>"6", "progress"=>4, "status"=>"provisioning"}]}

2015-05-24T19:31:40 debug: [684] Data received by ProvisiningProxyReporter to report it up: {"nodes"=>[{"uid"=>"1", "progress"=>10, "status"=>"provisioning"}, {"uid"=>"2", "progress"=>10, "status"=>"provisioning"}, {"uid"=>"3", "progress"=>10, "status"=>"provisioning"}, {"uid"=>"4", "progress"=>10, "status"=>"provisioning"}, {"uid"=>"5", "progress"=>10, "status"=>"provisioning"}, {"uid"=>"6", "progress"=>10, "status"=>"provisioning"}]}

2015-05-24T19:35:56 debug: [684] Data received by ProvisiningProxyReporter to report it up: {"nodes"=>[{"uid"=>"1", "progress"=>16, "status"=>"provisioning"}, {"uid"=>"2", "progress"=>16, "status"=>"provisioning"}, {"uid"=>"3", "progress"=>16, "status"=>"provisioning"}, {"uid"=>"4", "progress"=>16, "status"=>"provisioning"}, {"uid"=>"5", "progress"=>16, "status"=>"provisioning"}, {"uid"=>"6", "progress"=>16, "status"=>"provisioning"}]}

2015-05-24T19:40:06 debug: [684] Data received by ProvisiningProxyReporter to report it up: {"nodes"=>[{"uid"=>"1", "progress"=>100, "status"=>"provisioning"}, {"uid"=>"2", "progress"=>99, "status"=>"provisioning"}, {"uid"=>"3", "progress"=>99, "status"=>"provisioning"}, {"uid"=>"4", "progress"=>99, "status"=>"provisioning"}, {"uid"=>"5", "progress"=>99, "status"=>"provisioning"}, {"uid"=>"6", "progress"=>99, "status"=>"provisioning"}]}

[Alexander Kislitsky (akislitsky)]

We passed SCF in 8.0. Moving the bug to 9.0.

[Vladimir Sharshov (vsharshov)]

It is still actual because provisioning operation still separate action and big operation which progress detected using log.