Hide Forgot
Description of problem: Openshift compute ndoes are members of AutoscalingGroup in heat stack, when each member is created it registers itself on bastion node ("deployment_bastion_node_add" SW deployment in templates), then a separate step ("deployment_run_ansible" in node.yaml) configures openshift on all nodes which are already registered. It may happen that deployment_run_ansible is trigerred by some node before all nodes are registered (by deployment_bastion_node_add) which causes that then nodes are added in multiple ansible runs/batches. It doesn't break setup and basically is nothing bad with it but it makes creation or scale up slower. It would be better to wait until deployment_bastion_node_add is done for all nodes and then run deployment_run_ansible only once for all nodes (AutoscalingGroup doesn't allow to do this easily though). Version-Release number of selected component (if applicable): openshift-on-openstak 0.9.5 How reproducible: it's random but can be reproduced when deploying with any higher number of nodes (e.g. node_count=5)
Addressed by: https://github.com/redhat-openstack/openshift-on-openstack/pull/302
For aos-scalability-34 testing the patch above was applied.
Hi, the patch for this issue is not a one-liner, I'm concerned about regression it might introduce. This issue is only optimization (deployment will work without this patch too, it will just be slower which matters only for larger deployments), do you really want to include this now instead of in the next release?