Comment 4 for bug 1383511

Revision history for this message
Vladimir Sharshov (vsharshov) wrote : Re: Controller deployment completion wasn't seen by Fuel/MOS masternode

During Astute logs message about correct status for both controllers send in time.

2014-10-20T22:35:52 debug: [432] Data received by DeploymentProxyReporter to report it up: {"nodes"=>[{"uid"=>"78", "status"=>"ready", "role"=>"controller"}, {"uid"=>"85", "progress"=>56, "status"=>"deploying", "role"=>"controller"}]}
2014-10-20T22:36:00 debug: [432] Data received by DeploymentProxyReporter to report it up: {"nodes"=>[{"uid"=>"85", "status"=>"ready", "role"=>"controller"}]}

Nailgun got this messages also in time:

2014-10-20 22:35:52.269 INFO [7f34f7f14700] (receiver) RPC method deploy_resp received: {"task_uuid": "24d4f50b-9775-42ca-a436-e0cacfa1e107", "nodes": [{"status": "ready", "progress": 100, "role": "controller", "uid": "78"}]}
2014-10-20 22:36:16.692 INFO [7f34f7f14700] (receiver) RPC method deploy_resp received: {"task_uuid": "24d4f50b-9775-42ca-a436-e0cacfa1e107", "nodes": [{"status": "ready", "progress": 100, "role": "controller", "uid": "85"}]}

Looks like UI problem.