Sorry, I haven't worked with Eucalyptus since so don't know if this
issue was ever resolved. Unless the designed changed somewhat, however,
I would have expected it to be a problem for everyone using separate CC
CLC with private addressing and managed mode, as the metadata service
keys off
Scott Moser wrote on 2010-05-20:
(MANAGED modes). In order for the meta-data service to work, the VM
needs to be assigned a public IP, and it looks like this operation is
failing (indicated by the fact that the public/private IPs being
reported are both from the private IP subnet).
Indeed, I've never had it work with separate CC CLC for an instance
without a public IP (see my comment #28 in bug 566792).
--
Instance without public ip fails reading metadata with separate CC CLC
https://bugs.launchpad.net/bugs/580184
You received this bug notification because you are a
Public bug reported:
With separate CC and CLC, when an instance without a public address (in
MANAGED[_NOVLAN] mode) attempts to contact the metadata service to get
its ssh key, the CC reroutes the request to the CLC and masquerades the
requestor's address. So the CLC appears to get the metadata
