During deployment of 5 node cluster (3 controllers and 2 computes) with contrail plugin (https://github.com/stackforge/fuel-plugin-contrail) failure of one of the compute nodes switches all nodes into Error state forcing redeployment of entire environment instead of just failed node.
Steps to reproduce:
1) install the plugin
2) create new environment
3) add 3 controllers and two compute nodes
4) configure interfaces for all hosts intentionally misconfiguring one of the compute nodes
5) deploy changes
Current behavior:
Although controllers got deployed successfully prior to deployment of misconfigured compute node, failure of this node is switching all nodes in the cluster (also those marked as "Ready") into error state forcing user to redeploy everything from scratch.
Expected behavior:
misconfigured compute node is switched into error state, controllers are still marked as "Ready" and don't require redeployment
During deployment of 5 node cluster (3 controllers and 2 computes) with contrail plugin (https:/ /github. com/stackforge/ fuel-plugin- contrail) failure of one of the compute nodes switches all nodes into Error state forcing redeployment of entire environment instead of just failed node.
VERSION: version: "2014.2.2-6.1" 19_13-02- 31" dd8cfd7e60c3f66 50f18013a37" fuelclient_ sha: "4fc55db0265bbf 39c369df398b9dc 7d6469ba13b" 13706d543a5b9f5 57f5414beae" 00ebf08ce87f486 7df36aa9fab" 0f00847cc309c24 f0b62de718d" f56019c8ce21aa8 bb81fee0c2f"
feature_groups:
- mirantis
production: "docker"
release: "6.1"
openstack_
api: "1.0"
build_number: "525"
build_id: "2015-06-
nailgun_sha: "dbd54158812033
python-
astute_sha: "1ea8017fe88894
fuel-library_sha: "2e7a08ad9792c7
fuel-ostf_sha: "8fefcf7c464937
fuelmain_sha: "a3998372183468
Steps to reproduce:
1) install the plugin
2) create new environment
3) add 3 controllers and two compute nodes
4) configure interfaces for all hosts intentionally misconfiguring one of the compute nodes
5) deploy changes
Current behavior:
Although controllers got deployed successfully prior to deployment of misconfigured compute node, failure of this node is switching all nodes in the cluster (also those marked as "Ready") into error state forcing user to redeploy everything from scratch.
Expected behavior:
misconfigured compute node is switched into error state, controllers are still marked as "Ready" and don't require redeployment