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): RHOP 10 Puddle- 2016-08-24.1 How reproducible: 100% Steps to Reproduce: 1. Deploy OSP using DVR 2. Boot instance injecting key, or passing --user-data 3. Actual results: 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. Expected results: Instance should be able to ping metadata IP, fetch metadata. Additional info:
This issue had been resolved upstream through a unrelated refactoring/cleanup. https://review.openstack.org/#/c/361362/ 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 25.25.25.1 dev eth0 proto static metric 100 25.25.25.0/24 dev eth0 proto kernel scope link src 25.25.25.3 metric 100 169.254.169.254 via 25.25.25.1 dev eth0 proto dhcp metric 100 [root@vm-1 ~]# curl http://169.254.169.254/ 1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01 2009-04-04 there is connectivity. tack@undercloud-0 ~]$ rpm -qa| grep openstack-tripleo-heat openstack-tripleo-heat-templates-5.0.0-0.20160929150845.4cdc4fc.el7ost.noarch
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. https://rhn.redhat.com/errata/RHEA-2016-2948.html