IP mismatch from terraform output to VM actual addresses

[bwgartner]

The output (after terraform apply) echos the "ips", yet if you look at the VMs you will notice they are a +1 increment on the last octet. So then the output of

terraform output -json | jq -r '.ips.value[][]'

will not match the deployed VMs so the mk-ssh-config.sh and subsequent cluster setup commands will not work.

Good news is that manually making the IP changes in those commands/outputs seems to allows connectivity and completion

[yacinelazaar]

I second this.
Here are the assigned IPs during provisioning (some are dangling):

 Expiry Time          MAC address        Protocol  IP address                Hostname        Client ID or DUID
-------------------------------------------------------------------------------------------------------------------
 2020-05-18 20:44:28  52:54:00:52:b0:b3  ipv4      10.16.0.211/24            -               ff:00:52:b0:b3:00:01:00:01:26:55:94:03:52:54:00:52:b
0:b3
 2020-05-18 20:44:56  52:54:00:52:b0:b3  ipv4      10.16.0.212/24            kubic-1         ff:00:52:b0:b3:00:01:00:01:26:55:94:1f:52:54:00:52:b
0:b3
 2020-05-18 20:44:28  52:54:00:56:b8:86  ipv4      10.16.0.155/24            -               ff:00:56:b8:86:00:01:00:01:26:55:94:02:52:54:00:56:b
8:86
 2020-05-18 20:44:56  52:54:00:56:b8:86  ipv4      10.16.0.156/24            kubic-0         ff:00:56:b8:86:00:01:00:01:26:55:94:21:52:54:00:56:b
8:86
 2020-05-18 20:44:28  52:54:00:62:6a:6c  ipv4      10.16.0.89/24             -               ff:00:62:6a:6c:00:01:00:01:26:55:94:03:52:54:00:62:6
a:6c
 2020-05-18 20:44:56  52:54:00:62:6a:6c  ipv4      10.16.0.90/24             kubic-2         ff:00:62:6a:6c:00:01:00:01:26:55:94:21:52:54:00:62:6
a:6c

[emilianolangella]

I have the same issue.