You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The subnet filtering work perfectly if subnet name looks like sub-pvt-mgmt-a
Problems starting when subnet looks like mgmt mgmt-services-a res-persist-mgmt us-west-2 as ansible won't be able to filter exact name mgmt mgmt-services-a.
…` + `az` (e.g. `test mysvc-us-west-2a myextrastring`). Also make only a single call to get subnets, improving speed. Fixes#62
Add `UserKnownHostsFile=/dev/null` to EXAMPLE/ansible.cfg (prevents host key check failures).
…` + `az` (e.g. `test mysvc-us-west-2a myextrastring`). Also make only a single call to get subnets, improving speed. Fixes#62 (#63)
Add `UserKnownHostsFile=/dev/null` to EXAMPLE/ansible.cfg (prevents host key check failures).
The subnet filtering work perfectly if subnet name looks like
sub-pvt-mgmt-a
Problems starting when subnet looks like
mgmt mgmt-services-a res-persist-mgmt us-west-2
as ansible won't be able to filter exact namemgmt mgmt-services-a
.clusterverse/cluster_hosts/tasks/get_cluster_hosts_target.yml
Line 47 in d544eb7
Possible solution is to alter to
"tag:Name": "{{ cluster_vars[buildenv].vpc_subnet_name_prefix }}{{item}}*"
- add*
in the end.The text was updated successfully, but these errors were encountered: