Fuel Nodes tab shows 100% "Installing ubuntu" progress for all nodes, but actual Ubuntu installation is still in progress.

[Aleksandr Didenko]

{"release": "3.2.1", "nailgun_sha": "61c4aafd97de7eb52b7a5f710d9cfcf8d50c52ec", "ostf_sha": "c70535553616d3c2f8b0bccced54361c06f76f97", "astute_sha": "df6ddea3abc93fbe1cab9b4534d4d5e9508c95d6", "fuellib_sha": "2899a334f022435c2593bde7ddd5511bf8456e07"}

Installation details
Nodes: 3 (1 controller + 1 cinder + 1 compute)
Mode: simple
OS: ubuntu on KVM
Network: neutron+vlan
Storage: cinder+lvm

During environment deployment in the Fuel UI (Fuel Nodes tab) "Installing ubuntu" progress bars for all nodes reach 100% before OS installations are actually completed.

[Vladimir Sharshov (vsharshov)]

It is expected behavior because Ubuntu installation contain many log files but at now moment we analyze only one which contain data about progress on the largest time interval. Unfortunately, this file does not cover the entire installation process.

We use some technical magic to bring the progress bar to the real state as best as possible, but because we not control all logs we could not show progress bar with 100% precision.

Please give information how much time has passed since the show 100% to 100% real?

[Aleksandr Didenko (adidenko)]

On a kvm test lab it could take up to 20-40 minutes.

[Vladimir Sharshov (vsharshov)]

Alexander Didenko, i am correctly understand what progress of installation showed 100% 20-40 minutes early when really got 100%? Or whole progress take 20-40 minutes?

[Aleksandr Didenko (adidenko)]

It "showed 100% 20-40 minutes early when really got 100%". Let me check this again on the latest 4.0 iso and provide more actual info.

[Aleksandr Didenko (adidenko)]

ISO: {"release": "4.0", "nailgun_sha": "e377abc3ce2abf75ac4d40206cc4d2964581ffef", "ostf_sha": "bb0802637abc40d2caa734756544033951739f09", "astute_sha": "7b77437a5d87dd5d06b45d152df80a681ffa25eb", "fuellib_sha": "912a1c77d0506115452bb455b476d74b927f1153"}

Ubuntu installation progress bars are pretty accurate now, tested on a bare metal deployment (HA, 4 nodes).

[Nikolay Markov (nmarkov)]

Alexander, is this already fixed? If so, please close the bug ('Fix commited' status).