metadata missing when CLC and CC on different hosts and VM instance is private
Bug #792329 reported by
Francesco Caruso
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Eucalyptus |
New
|
Undecided
|
chris grzegorczyk | ||
Bug Description
Hi Folks,
Looks like when the CLC and CC are on different hosts the metadata is only accessible by instances with a public address.
(if the VNET_CLOUDIP points to the CLC host)
When I launch images with a private IP the metadata call returns an empty value.
This works well if CLC and CC are on the same machine.
Please advise
--Francesco
| Changed in eucalyptus: | |
| assignee: | nobody → chris grzegorczyk (chris-grze) |
Revision history for this message
| Francesco Caruso (caruso) wrote | #1 |
Revision history for this message
| Andy Grimm (agrimm) wrote | #2 |
To post a comment you must log in.
I did some testing and looks like the CLC is not returning the data because the HTTP request in the CC is NATed to the CLC host and hence the metadata repo does not know the IP of the real originator. I wonder if having an HTTP proxy server in the CC and removing the NAT for VNET IPs will fix the problem...
What puzzles me is, has this ever worked in any multi-cluster deployment before?
--Fr