OSP versions 10 and below uses 192.0.2.0/24 network, so EC2MetadataIp should be set to 192.0.2.1 instead of 192.168.24.1 in network_islocation.yaml i.e
Otherwise I am getting below errors in compute node, as no route exists in compute node for reaching 169.254.169.254 target.
Aug 23 04:22:52 compute-0 os-collect-config: HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /latest/meta-data/ (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7fd15c04bc10>, 'Connection to 169.254.169.254 timed out. (connect timeout=10.0)'))
Aug 23 04:23:32 compute-0 os-collect-config: HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /latest/meta-data/ (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7fd15c02fd90>, 'Connection to 169.254.169.254 timed out. (connect timeout=10.0)'))
[heat-admin@compute-0 ~]$ ip r
default via 10.19.97.254 dev em3 proto dhcp metric 100
10.19.96.0/23 dev em3 proto kernel scope link src 10.19.96.54 metric 100
172.17.1.0/24 dev vlan20 proto kernel scope link src 172.17.1.18
172.17.2.0/24 dev vlan50 proto kernel scope link src 172.17.2.14
172.17.3.0/24 dev vlan30 proto kernel scope link src 172.17.3.13
192.0.2.0/24 dev em2 proto kernel scope link src 192.0.2.17
OSP versions 10 and below uses 192.0.2.0/24 network, so EC2MetadataIp should be set to 192.0.2.1 instead of 192.168.24.1 in network_islocation.yaml i.e
https://github.com/redhat-openstack/infrared/blob/master/plugins/tripleo-overcloud/vars/deployment/files/virt/network/network-environment.yaml.j2
{% if install.version|openstack_release > 10 %} DnsServers: ['192.168.24.1'] EC2MetadataIp: 192.168.24.1 {% else %} DnsServers: ['192.0.2.1'] EC2MetadataIp: 192.0.2.1 {% endif %} {% if install.version|openstack_release > 10 %} ControlPlaneDefaultRoute: 192.168.24.1 {% else %} ControlPlaneDefaultRoute: 192.0.2.1 {% endif %}
Otherwise I am getting below errors in compute node, as no route exists in compute node for reaching 169.254.169.254 target.
Aug 23 04:22:52 compute-0 os-collect-config: HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /latest/meta-data/ (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7fd15c04bc10>, 'Connection to 169.254.169.254 timed out. (connect timeout=10.0)')) Aug 23 04:23:32 compute-0 os-collect-config: HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /latest/meta-data/ (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7fd15c02fd90>, 'Connection to 169.254.169.254 timed out. (connect timeout=10.0)'))
[heat-admin@compute-0 ~]$ ip r default via 10.19.97.254 dev em3 proto dhcp metric 100 10.19.96.0/23 dev em3 proto kernel scope link src 10.19.96.54 metric 100 172.17.1.0/24 dev vlan20 proto kernel scope link src 172.17.1.18 172.17.2.0/24 dev vlan50 proto kernel scope link src 172.17.2.14 172.17.3.0/24 dev vlan30 proto kernel scope link src 172.17.3.13 192.0.2.0/24 dev em2 proto kernel scope link src 192.0.2.17