** 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
** 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
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
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
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
** 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
** 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
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
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
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
**
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
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
@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
** 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
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
** 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.
--
** 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
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
** 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
** 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
** 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
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
** 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
** 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
@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
** 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
** 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
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).
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
** 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.
** 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
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-E58B1525
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
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
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,
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.
** 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
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
38 matches
Mail list logo
