Hello,
Just an update to this issue.
I make it work by adding a DNAT iptables rule on the WNs, redirecting
connection destined to 169.254.169.254 to :8773.
I thought this is taken care of by openstack automatically, maybe not?
Or am I on the wrong track?
Thanks,
Xin
On 8/13/2012 6:03 PM, Xin
Hello,
How can I check the value of $my_ip?
I notice that in the arp table on the instance, the entry for ip
169.254.169.254 has a wrong mac address, which I don't see existent on
both the controller
node and the worker node. After I change the entry for ip
169.254.169.254 to map to the real
On 08/10/2012 12:17 PM, Vishvananda Ishaya wrote:
$> curl -v http://169.254.169.254:8775/
* About to connect() to 169.254.169.254 port 8775 (#0)
* Trying 169.254.169.254... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host
Any idea wher
On Aug 9, 2012, at 7:31 PM, Xin Zhao wrote:
> Hello,
>
> In my essex install on RHEL6, there is a problem with the metadata service.
> The metadata service works for instances running on the controller node, where
> the nova-api(metadata service) is running. But for the other worker nodes,
> th
I would start to check out iptables and routes that are being setup (in
vms and outside).
If you are running a flat (no dhcp) network that usually makes it a lot
harder also.
On 8/9/12 7:31 PM, "Xin Zhao" wrote:
>Hello,
>
>In my essex install on RHEL6, there is a problem with the metadata
>serv
Hello,
In my essex install on RHEL6, there is a problem with the metadata service.
The metadata service works for instances running on the controller node,
where
the nova-api(metadata service) is running. But for the other worker nodes,
the metadata service is intermittent, ie. the instances so
6 matches
Mail list logo
