[Bug 566792] Re: metadata service returns empty data with 200 OK
** Changed in: eucalyptus Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/566792 Title: metadata service returns empty data with 200 OK To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/566792/+subscriptions -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Branch linked: lp:ubuntu/eucalyptus -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
I'm not seeing this behavior in Maverick, so marking fixed released for that task. ** Changed in: eucalyptus (Ubuntu Maverick) Status: Triaged = Fix Released -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
Sorry if this is the wrong place to post such a message, but I'm experiencing this issue on a production host and it's a significant issue. I have to reboot my machine regularly, and this bug is causing boot to take well over 30 minutes. Is there a workaround I can use until the next stable release? Can someone point me to the proper place to get support for this issue? Thanks in advance -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
aaronbauman, This bug is believed to be fix-released in lucid (lucid-updates). I think its probably best if you open a new bug and describe the issue you're having. Please open the bug with 'ubuntu-bug eucalyptus' on the cluster controller that way related debug information will be collected. Thank you. -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Tags added: lucid maverick patch -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Tags removed: patch -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
Added patch-forwarded-upstream since the upstream project uses launchpad for bugtracking ** Tags added: patch-forwarded-upstream ** Tags removed: patch -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
Hi Can it be that with this packages, the initscripts on the CC and CLC have changed from eucalyptus-cloud (CLC) eucalyptus-CC (CC) to only eucalyptus? Because i installed the CC based on these packages and and restart eucalyptus-cc did nothing, whereas a restart eucalyptus CLEAN=1 worked for me? Greets Thomas -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
Making this a release blocker to avoid regressions in maverick. ** Also affects: cloud-init (Ubuntu Maverick) Importance: Undecided Status: Invalid ** Also affects: eucalyptus (Ubuntu Maverick) Importance: High Assignee: Dave Walker (davewalker) Status: Confirmed ** Changed in: eucalyptus (Ubuntu Maverick) Status: Confirmed = Won't Fix ** Changed in: eucalyptus (Ubuntu Maverick) Milestone: None = ubuntu-10.10-beta ** Changed in: eucalyptus (Ubuntu Maverick) Status: Won't Fix = Triaged -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu30.3 --- eucalyptus (1.6.2-0ubuntu30.3) lucid-proposed; urgency=low * debian/patches/lp566792-metadata-service.patch: Prevent invalid state transitions and fix address handling which mangled in-flight state changes. Cherry pick from upstream 1.6.2 branch (r1230..1232). (LP: #566792) -- Dave Walker (Daviey) davewal...@ubuntu.com Wed, 30 Jun 2010 00:10:43 +0100 ** Changed in: eucalyptus (Ubuntu Lucid) Status: Fix Committed = Fix Released -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
Tests re-run; in 800 instances we got a single metadata failure. After discussing the status with all in a teleconference, we decided to approve the changes so far: * no regressions were detected; * one failure in 800, on a extremely stressed UEC is *way better* than ~5 failures in 100. * we need this fix published for stability. So I am marking this verification-done; Eucalyptus is looking at the error, and will eventually propose an addendum to the patch, which we will integrate in another SRU. ** Tags added: verification-done ** Tags removed: verification-needed ** Changed in: eucalyptus (Ubuntu) Status: Confirmed = Fix Committed ** Changed in: eucalyptus (Ubuntu) Status: Fix Committed = Confirmed -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
@Colin, thanks for that. @C de-Avillez: Can you re-run your tests against the package that is hitting lucid-proposed shortly, and update the verification tag as appropriate. Thanks all! -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Branch linked: lp:ubuntu/lucid-proposed/eucalyptus -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
I have just ran a 400-instance test with the latest patch (from Dave's PPA, 1.6.2-0ubuntu30.3.6). I sent the following to the interested parties: email begins I just finished a 400-instances run. I am extremely glad to state I saw no occurrence of the metadata/public IP issue. Of course, we are talking about a race, but I would say that we have drastically reduced (if not completely resolved) the incidence. I favour we consider this fix done publish it ASAP. email ends -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Changed in: eucalyptus Status: New = Fix Committed -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Branch linked: lp:~davewalker/ubuntu/lucid/eucalyptus/lp566792 -metadata-service -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
I am still running the 2,000 test. Right now I am at about 385 instances started, with 10 failures. Looking at the failures I see: i-442A07C, i-55F5097A, i-405C076B, i-42B708A5, i-3C0F0746, i-4C6D099C, i-4B0D08E4, i-568308F5 -- did not get assigned a public IP. I have uploaded the current view to lp:~hggdh2/+junk/uec-qa, under lucid/r1235. Sorry. -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Branch linked: lp:~davewalker/ubuntu/lucid/eucalyptus/lp566792_fix_metadata_service -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Changed in: eucalyptus (Ubuntu) Assignee: Scott Moser (smoser) = Dave Walker (davewalker) ** Changed in: eucalyptus (Ubuntu Lucid) Assignee: Scott Moser (smoser) = Dave Walker (davewalker) -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Changed in: eucalyptus Assignee: (unassigned) = chris grzegorczyk (chris-grze) -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
Update on status: revision 1230 seems to have corrected the issue of IP addresses not being correctly set. Nevertheless, we still have metadata errors. Chris is looking into it. ** Tags added: patch-refused ** Tags removed: patch -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Tags removed: patch-forwarded-upstream -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Tags added: patch-forwarded-upstream -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
@David, Why are you setting the 'patch-forwarded-upstream' tag on this bug, the patch has *not* been forwarded upstream. in fact, there is no patch or solution for the bug. -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Tags added: patch-forwarded-upstream -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Tags removed: patch-forwarded-upstream -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
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
Re: [Bug 566792] Re: metadata service returns empty data with 200 OK
On Fri, 28 May 2010, Mike Cook wrote: I happen to [know] 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. They were the same, yes. So my comment may well be invalid. -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Changed in: eucalyptus (Ubuntu Lucid) Milestone: None = lucid-updates -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Summary changed: - UEC guests sometimes fail on consuming user data (metadata service isn't ready) + metadata service returns empty data with 200 OK -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
OK. I think I've figured out what is causing this. in 100% of the failed instances that I'm seeing today, the instance has its public ip identical to its private ip. Ie, the following is euca-describe-instances output of a failed instance: INSTANCEi-2F1A0573 emi-E58B1525172.19.1.48 172.19.1.48 running uectest-k0 0 m1.small 2010-05-20T15:34:28.275ZUEC-TEST1 eki-2B241A2B And this is from a successful instance: INSTANCEi-37A30725 emi-E58B152510.55.55.187172.19.1.34 running uectest-k0 0 m1.small 2010-05-20T15:34:06.874ZUEC-TEST1 eki-2B241A2B Note, these instances were not launched with '--addressing private'. $ euca-describe-addreses | sort ADDRESS 10.55.55.100i-4A34090E (eucalyptus) ADDRESS 10.55.55.101available (nobody) ADDRESS 10.55.55.102available (eucalyptus) ... ADDRESS 10.55.55.238nobody ADDRESS 10.55.55.239nobody ADDRESS 10.55.55.240nobody $ euca-describe-addresses | grep nobody | wc -l 24 $ euca-describe-addresses | wc -l 141 It seems there should have been addresses available, euca-describe- availability-zones only shows 32 instances max. # on the cloud-controller cc-host$ cat /etc/eucalyptus/eucalyptus.local.conf VNET_MODE=MANAGED-NOVLAN VNET_SUBNET=172.19.0.0 VNET_NETMASK=256.255.0.0 VNET_DNS=10.55.55.1 VNET_ADDRSPERNET=32 VNET_PUBLICIPS=10.55.55.100-10.55.55.240 VNET_CLOUDIP=10.55.55.2 The testcases (lp:~uec-testing-scripts-dev/uec-testing-scripts/trunk/) basically keep firing off instances 1 by 1 with euca-run-instances as long as 'euca-describe-availability-zones verbose' reports that there is space. Note, instances are ran *without* '--addressing private', but appear to be getting private addressing. -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
I'm attaching iptables-save output on CLC, CC, NC1 and NC2. I really don't think its of that much value due to the previous comment, but it was requested. ** Attachment added: iptables-save output on CLC, CC, NC1, NC2 in failing state http://launchpadlibrarian.net/48821877/failing-iptables.txt -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
Scott, thank you for pursuing this issue. Indeed, the meta-data service keys off of the public IP of the VM, since that is the only source address that is translated when the NCs cannot directly contact the CLC (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). Lets take a look at cc.log for an instance that is failing to get a public IP (look for the RunInstance that corresponds with the instance ID in question, and include a few minutes of log after the RunInstance). We're specifically looking to see if an AssignAddress() operation is ever called for the VM's private IP, or if no AssignAddress() is ever called for that VM. I think this will help us figure out why that VM is not getting a public IP assigned. Thanks again, I think we're close to being able to get to the root cause of this. p.s. I notice that your VNET_NETMASK is set to an invalid value, but the iptables output doesn't reflect this problem; can you confirm that your VNET_NETMASK is actually '255.255.0.0' and not '256.255.0.0' as was reported above? If it is, note that this may have unforeseen consequences. -- 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
Re: [Bug 566792] Re: metadata service returns empty data with 200 OK
Daniel Nurmi wrote: Scott, thank you for pursuing this issue. Indeed, the meta-data service keys off of the public IP of the VM, since that is the only source address that is translated when the NCs cannot directly contact the CLC (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? -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
I'm attaching 2 files. failed-instance-cc.log (i-3812076B) and good- instance-cc.log (i-42A70769) Unfortunately, I dont think they'll be of a whole lot of use, as the 'AssignAddress' calls are not tied to the instance id in the log, so I dont know how to tell which call was for which instance id. In the 'good-instance-cc.log', there was really only one instance, but in the failed version, there are lots of things happening (the test case is running). ** Attachment added: cc.log during failure of i-3812076B http://launchpadlibrarian.net/48830261/failed-instance-cc.log.bz2 -- 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
[Bug 566792] Re: metadata service returns empty data with 200 OK
** Attachment added: cc.log during successful run of i-42A70769 http://launchpadlibrarian.net/48830292/good-instance-cc.log.bz2 -- 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
Re: [Bug 566792] Re: metadata service returns empty data with 200 OK
On Thu, 20 May 2010, Etienne Goyer wrote: (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. -- 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
