Node count of deployment remains 0 when new node tagging interface is used

[Dan Trainor]

When the new UI interface for node tagging is used, the process fails to update ControllerCount, ComputeCount, CephCount etc parameters required in the environment plan.

Using the node tagging interface, one can tag nodes of a certain type; however, the environment plan does not get updated. If nodes are untagged and then assigned using the "Assign Nodes" interface on the main page, then the Count numbers for the environment are updated.

This may be related to https://bugs.launchpad.net/tripleo/+bug/1642342 , possible regression used in node tagging process.

[Dan Trainor (dtrainor)]

Clicking on the "Assign Nodes" button and then clicking "Assign/Unassign Select Nodes" button populates the needed value of ControlCount, ComputeCount etc.

[Jiri Tomasek (jtomasek)]

This is expected behavior - whole point of splitting nodes tagging and assignment. In nodes table you tag nodes to specific flavor and in deployment plan page you set the count of nodes you want to deploy (and set correct flavor in Role detail if it is not set correctly by default).

The nodes count does not match the number of tagged nodes. Tagging nodes just sets the preference that for deployment nodes tagged for a specific role will be prioritized for deployment of that specific role.

e.g. there are 8 nodes available in total, tag 3 of them as compute, in compute role you set nodes count to 5 -> 3 tagged + 2 untagged nodes will be used for compute role deployment.

Original 'Assign nodes' functionality is being removed by this patch: https://review.openstack.org/454736