Incorrect status of progress bar on Ubuntu

Does it affect master?

Please move bug to 'Invalid' state in 5.1 if it not reproducible there.

Does it always freeze? Does it freeze at 0% for whole duration of deployment, or only during provisioning? Does it affect CentOS?

Does not reproduced on the iso #106

Reproduced again on iso #107

Discovery logs and compare with success installation:

Correct (Astute):

[407] Casting message to fuel: {"method"=>"deploy_resp", "args"=>{"task_uuid"=>"eb13f757-7c91-4869-bd78-410e7f481750", "nodes"=>[{"uid"=>"2", "progress"=>34, "status"=>"deploying", "role"=>"compute"}]}}
[407] Casting message to fuel: {"method"=>"deploy_resp", "args"=>{"task_uuid"=>"eb13f757-7c91-4869-bd78-410e7f481750", "status"=>"ready", "progress"=>100}}

Incorrect (Astute):

422] Casting message to fuel: {"method"=>"deploy_resp", "args"=>{"task_uuid"=>"1f2906a7-0fff-423e-91b6-6686b54cb1a8", "nodes"=>[{"uid"=>"2", "progress"=>34, "status"=>"deploying", "role"=>"compute"}]}}
[422] Casting message to fuel: {"method"=>"deploy_resp", "args"=>{"task_uuid"=>"1f2906a7-0fff-423e-91b6-6686b54cb1a8", "status"=>"ready", "progress"=>100}}

Result: no differents.

Correct (Nailgun):

2014-07-10 08:56:03.961 INFO [7fc90c241700] (receiver) RPC method deploy_resp received: {"status": "ready", "progress": 100, "task_uuid": "eb13f757-7c91-4869-bd78-410e7f481750"}
/usr/lib64/python2.6/site-packages/sqlalchemy/sql/expression.py:1927: SAWarning: The IN-predicate on "nodes.id" was invoked with an empty sequence. This results in a contradiction, which nonetheless can be expensive to evaluate. Consider alternative strategies for improved performance.
  return self._in_impl(operators.in_op, operators.notin_op, other)
2014-07-10 08:56:04.005 DEBUG [7fc90c241700] (receiver) Controller is found, node_id=1, getting it's IP addresses
2014-07-10 08:56:04.039 INFO [7fc90c241700] (notification) Notification: topic: done message: Deployment of environment 'test' is done. Access the OpenStack dashboard (Horizon) at http://172.16.0.2/ or via internal network at http://10.20.0.3/
2014-07-10 08:56:04.039 DEBUG [7fc90c241700] (helpers) Updating task: eb13f757-7c91-4869-bd78-410e7f481750
2014-07-10 08:56:04.052 INFO [7fc90c241700] (helpers) Task eb13f757-7c91-4869-bd78-410e7f481750 (deployment) status is set to ready
2014-07-10 08:56:04.053 INFO [7fc90c241700] (helpers) Task eb13f757-7c91-4869-bd78-410e7f481750 (deployment) progress is set to 100
2014-07-10 08:56:04.053 INFO [7fc90c241700] (helpers) Task eb13f757-7c91-4869-bd78-410e7f481750 (deployment) message is set to Deployment of environment 'test' is done. Access the OpenStack dashboard (Horizon) at http://172.16.0.2/ or via internal network at http://10.20.0.3/
2014-07-10 08:56:04.073 DEBUG [7fc90c241700] (helpers) Updating cluster status: eb13f757-7c91-4869-bd78-410e7f481750 cluster_id: 1 status: ready
2014-07-10 08:56:04.101 DEBUG [7fc90c241700] (helpers) Updating parent task: 00f16f66-0825-480c-a362-80dd3cbe93a2.
2014-07-10 08:56:04.137 DEBUG [7fc90c241700] (helpers) Updating cluster (test (id=1, mode=multinode)) status: from deployment to operational

Incorrect (Nailgun):

2014-07-07 13:17:13.990 INFO [7f376e415700] (receiver) RPC method deploy_resp received: {"status": "ready", "progress": 100, "task_uuid": "1f2906a7-0fff-423e-91b6-6686b54cb1a8"}
/usr/lib64/python2.6/site-packages/sqlalchemy/sql/expression.py:1927: SAWarning: The IN-predicate on "nodes.id" was invoked with an empty sequence. This results in a contradiction, which nonetheless ca...

You are right - after F5 refreshing the page progress became in normal state. It is UI bug that is why it is marked with [ui] tag.

I can confirm this bug in 5.1 {"build_id": "2014-07-10_02-01-14", "ostf_sha": "f6f7cee46a85ca3e758f629c2df8b370e9de494a", "build_number": "308", "auth_required": false, "api": "1.0", "nailgun_sha": "745cf21a85a238a62d339e517258eb475fb0603e", "production": "docker", "fuelmain_sha": "11552f9b70f60ae4be4a4f6a68fa0291298c4e00", "astute_sha": "c0ffd4fa1b1ea16931f174a7f4efeac701ec23e6", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "c7c47fb692846dd1fb2e50661c6e95e0545b09ab"}

I can have hung progress bar for particular nodes while deployment is finished. If I hit reload - status is updated.

Down to Medium since workaround is available. Still leaving targeted for 5.0.1: it's a highly visible bug and we should try our best to fix it.

It seems the browser was not able to parse http response correctly: see "No Content" string before valid HTTP response

Fix proposed to branch: master
Review: https://review.openstack.org/106348

Fix proposed to branch: stable/5.0
Review: https://review.openstack.org/106351

Reviewed: https://review.openstack.org/106348
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=663e56128d935df4e614e731d6b80f8bcfbfd7ff
Submitter: Jenkins
Branch: master

commit 663e56128d935df4e614e731d6b80f8bcfbfd7ff
Author: Vitaly Kramskikh <email address hidden>
Date: Fri Jul 11 15:59:02 2014 +0400

    Fix random stop of polling of deployment status

    Change-Id: Ice4b5dbea047889ee59ef3fa8d51b1e00967504a
    Closes-Bug: 1338573

Reviewed: https://review.openstack.org/106351
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=9dfb38d393f57b043f8f0aa726ee4ed467ab3ace
Submitter: Jenkins
Branch: stable/5.0

commit 9dfb38d393f57b043f8f0aa726ee4ed467ab3ace
Author: Vitaly Kramskikh <email address hidden>
Date: Fri Jul 11 15:59:02 2014 +0400

    Fix random stop of polling of deployment status

    Change-Id: Ice4b5dbea047889ee59ef3fa8d51b1e00967504a
    Closes-Bug: 1338573