I figured it out. On the controller node I had to add a route to the network node for the private IP addresses. When the metadata request is sent, it does not NAT the address because the metadata service needs to know the IP. Once I put that route in place it started to work.

--Brian

On Fri, Aug 14, 2015 at 2:18 AM, Matthias Runge <mrunge@redhat.com> wrote:

On 13/08/15 17:16, brian lee wrote:

Sorry I should have said this in the first email, I am using nova
networking for this setup. The error that I shows when the VM is boot is:
unexpected error ['ConnectionError' object has no arrribute 'response']

this rings a bell for me. I used such a setup in Juno and had to toggle
service_metadata_proxy
in /etc/nova/nova.conf.

As far as I remember, this didn't work for me in Kilo any more, thus I switched to neutron.

Matthias

_______________________________________________
Rdo-list mailing list
Rdo-list@redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list

To unsubscribe: rdo-list-unsubscribe@redhat.com