Description of problem: Instances are unable to get metadata when booted with --user-data. Key injection also fails. Instances cannot even ping 169.254.169.254
Looking at with Brent Eagles, looks like nova_metadata_ip is not configured by TripleO.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy OSP using DVR
2. Boot instance injecting key, or passing --user-data
Instances fail to get metadata, although they have a route configured for metadata. Also, can't ping 169.254.169.254 even if the route has been configured.
Instance should be able to ping metadata IP, fetch metadata.
This issue had been resolved upstream through a unrelated refactoring/cleanup.
It appears that the change has already been pulled into our current packages.
The change that was made to the heat templates were insufficient. The required changes were made and merged upstream.
Tested metadata on dvr environment.
[root@vm-1 ~]# ip route
default via 220.127.116.11 dev eth0 proto static metric 100
18.104.22.168/24 dev eth0 proto kernel scope link src 22.214.171.124 metric 100
169.254.169.254 via 126.96.36.199 dev eth0 proto dhcp metric 100
[root@vm-1 ~]# curl http://169.254.169.254/
there is connectivity.
tack@undercloud-0 ~]$ rpm -qa| grep openstack-tripleo-heat
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.