Node with status "Ready" doesn't reboot after stop deployment

[Anastasia Palkina]

"build_id": "2014-09-17_04-49-39",
"ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346",
"build_number": "9",
"auth_required": true,
"api": "1.0",
"nailgun_sha": "51231834c61920a5dea8ce402ad027b2505d632d",
"production": "docker",
"fuelmain_sha": "8ef433e939425eabd1034c0b70e90bdf888b69fd",
"astute_sha": "f5fbd89d1e0e1f22ef9ab2af26da5ffbfbf24b13",
"feature_groups": ["mirantis"],
"release": "5.1",
"release_versions": {"2014.1.1-5.1": {"VERSION": {"build_id": "2014-09-17_04-49-39", "ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346", "build_number": "9", "api": "1.0", "nailgun_sha": "51231834c61920a5dea8ce402ad027b2505d632d", "production": "docker", "fuelmain_sha": "8ef433e939425eabd1034c0b70e90bdf888b69fd", "astute_sha": "f5fbd89d1e0e1f22ef9ab2af26da5ffbfbf24b13", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "d9b16846e54f76c8ebe7764d2b5b8231d6b25079"}}},
"fuellib_sha": "d9b16846e54f76c8ebe7764d2b5b8231d6b25079"

1. Create new environment (Ubuntu, HA mode)
2. Choose VLAN Neutron
3. Choose Ceph for images and Rados
4. Add 3 controllers, 3 computes, 4 cinder, 2 ceph
5. Move Storage network to other interface and bond 2 interfaces
6. Start deployment
7. Wait until first controller become 'ready'
8. Stop deployment
9. Node with status 'ready' (node-5) doesn't reboot (see screen)

No node-5 in task:
2014-09-17 13:33:03 DEBUG

[437] 'stop_deploy_task' service method called with data: {"args"=>{"engine"=>{"url"=>"http://10.20.0.2:80/cobbler_api", "username"=>"cobbler", "password"=>"EdEfXhny", "master_ip"=>"10.20.0.2"}, "task_uuid"=>"b7975ec3-add9-4c1b-bae6-97ea9a564b4f", "stop_task_uuid"=>"dce9825b-21f8-4ba5-8b85-e7add640c22c", "nodes"=>[{"admin_ip"=>"10.20.0.3", "uid"=>"1", "roles"=>["compute"], "slave_name"=>"node-1"}, {"admin_ip"=>"10.20.0.4", "uid"=>"2", "roles"=>["compute"], "slave_name"=>"node-2"}, {"admin_ip"=>"10.20.0.5", "uid"=>"3", "roles"=>["cinder"], "slave_name"=>"node-3"}, {"admin_ip"=>"10.20.0.8", "uid"=>"6", "roles"=>["cinder"], "slave_name"=>"node-6"}, {"admin_ip"=>"10.20.0.9", "uid"=>"7", "roles"=>["compute"], "slave_name"=>"node-7"}, {"admin_ip"=>"10.20.0.13", "uid"=>"11", "roles"=>["ceph-osd"], "slave_name"=>"node-11"}, {"admin_ip"=>"10.20.0.11", "uid"=>"9", "roles"=>["controller"], "slave_name"=>"node-9"}, {"admin_ip"=>"10.20.0.6", "uid"=>"4", "roles"=>["cinder"], "slave_name"=>"node-4"}, {"admin_ip"=>"10.20.0.12", "uid"=>"10", "roles"=>["cinder"], "slave_name"=>"node-10"}, {"admin_ip"=>"10.20.0.10", "uid"=>"8", "roles"=>["controller"], "slave_name"=>"node-8"}, {"admin_ip"=>"10.20.0.14", "uid"=>"12", "roles"=>["ceph-osd"], "slave_name"=>"node-12"}]}, "respond_to"=>"stop_deployment_resp", "method"=>"stop_deploy_task", "api_version"=>"1.0"}

[Egor Kotko (ykotko)]

One more reproduced on system tests:
http://jenkins-product.srt.mirantis.net:8080/view/5.1_swarm/job/5.1_fuelmain.system_test.ubuntu.thread_2/7/testReport/%28root%29/deploy_flat_stop_on_deploying/deploy_flat_stop_on_deploying/

[Nikolay Markov (nmarkov)]

As far as I know, this is not a bug, this is by design. We don't reset nodes in 'ready' status and in case of they present we don't unlock environment settings. This means, if you need to make some changes then, go and click 'Reset'. But also, you can just click "Deploy changes" again and continue deployment of remaining nodes without processing 'ready' ones again.

[Mike Scherbakov (mihgen)]

According to comment from Nick, marking as Incomplete. Anastasia, please provide your response on his comment. If you still think it is a bug, we will have to discuss it and finally decide whether we need to change this behavior or continue to have what we have now.

[Anastasia Palkina (apalkina)]

I want to research this situation after release.