tripleo

  1. Bug #1742237
  2. Comment #6

Comment 6 for bug 1742237

Revision history for this message
emanoel (emanoelxavier) wrote :

The value I currently have for EC2MetadaIP is the undercloud API IP. From the overcloud VM:
curl 192.168.24.1:8000
{"versions": [{"status": "CURRENT", "id": "v1.0", "links": [{"href": "http://192.168.24.1:8000/v1/", "rel": curl 192.168.24.1:8080
<html><h1>Not Found</h1><p>The resource could not be found.</p></html>[root@overcloud ~]

There is a route to that IP from the overcloud VM, and the behavior above is the expected one according to http://tripleo.org/install/advanced_deployment/deployed_server.html#testing-connectivity. The configuration I am currently using is based on http://tripleo.org/install/advanced_deployment/deployed_server.html#testing-connectivity. Should the value of the EC2MetadataIp be something else?