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). > > > > That is interesting. Does that mean the meta-data service would not > > work for instance started with "--addressing private"? > > I happen to from experience that it does work for addressing private. My > guess is that Eucalyptus especially takes care of the case where > '--addressing private' was used.
Scott, were the CC & CLC the same host when it worked for you? I don't see how it could ever work with "--addressing-private" if they're separate, and Daniel's comment seems to confirm. Since it doesn't inject the key using the non-MANAGED way when in MANAGED mode, it seems we need add a fix for private IP instances. It seems this specific bug may be around the fact that a host with a public IP isn't getting it nat'd properly by the CC. But the issue of a private-only IP instance not being able to get metadata may be separate (see bug 580184). -- metadata service returns empty data with 200 OK https://bugs.launchpad.net/bugs/566792 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
