In Fuel UI, if "Stop deployment" is selected when all nodes have just been marked as 'Ready', then cluster status becomes "Stopped", but the button "Deploy changes" is inactive.
Looks like some post-deployment actions wasn't performed in this case. Several OSTF tests failed because TestVM image wasn't uploaded.
Steps to reproduce:
- Create a cluster with any configuration (for example: CentOS / IBP, Nova-network/FlatDHCP, Ceph for images, RagosGW for objects);
- Add nodes to the cluster (for example: 1 controller, 1 compute, 1 cinder, 3 ceph);
- Deploy changes;
- Press "Stop deployment" button at the moment when all nodes became "Ready"
Expected result: After pressing "Stop deployment", button "Deploy changes" is available.
Actual result: button "Deploy changes" is not available (see the attached screenshot). To make "Deploy changes" available, a new compute node was added to the cluster, but deploy failed with the following error in puppet for the new compute:
-----------
2015-06-18 10:19:43 NOTICE (/Stage[main]/Ceph::Nova_compute/Exec[Set Ceph RBD secret for Nova]/returns) Error ENOENT: don't have client.compute
2015-06-18 10:19:43 ERR (/Stage[main]/Ceph::Nova_compute/Exec[Set Ceph RBD secret for Nova]/returns) change from notrun to 0 failed: virsh secret-set-value --secret $( virsh secret-define --file /root/secret.xml | egrep -o '[0-9a-fA-F]{8}(-[0-9a-fA-F]{4}){3}-[0-9a-fA-F]{12}') --base64 $(ceph auth get-key client.compute) && rm /root/secret.xml returned 1 instead of one of [0]
-----------
{"build_id": "2015-06-16_13-53-26", "build_number": "522", "release_versions": {"2014.2.2-6.1": {"VERSION": {"build_id": "2015-06-16_13-53-26", "build_number": "522", "api": "1.0", "fuel-library_sha": "3528dddbd0c961290909d5e3e256f55ff75cd2fc", "nailgun_sha": "fa8dec50f3df2626c97f6c38a897cf4e0f80b39d", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "4fc55db0265bbf39c369df398b9dc7d6469ba13b", "astute_sha": "1ea8017fe8889413706d543a5b9f557f5414beae", "fuel-ostf_sha": "8fefcf7c4649370f00847cc309c24f0b62de718d", "release": "6.1", "fuelmain_sha": "42020c36d6dec9fedf61faa68aa3674156d41977"}}}, "auth_required": true, "api": "1.0", "fuel-library_sha": "3528dddbd0c961290909d5e3e256f55ff75cd2fc", "nailgun_sha": "fa8dec50f3df2626c97f6c38a897cf4e0f80b39d", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "4fc55db0265bbf39c369df398b9dc7d6469ba13b", "astute_sha": "1ea8017fe8889413706d543a5b9f557f5414beae", "fuel-ostf_sha": "8fefcf7c4649370f00847cc309c24f0b62de718d", "release": "6.1", "fuelmain_sha": "42020c36d6dec9fedf61faa68aa3674156d41977"}
Workaround: reset cluster.
We could not garantee that deployment will fine after stop deployment. As i remember, we have such bug for 6.1 also, but i could not find link, and also should added this info release-notes for 6.1.
Add release-notes tag.