** Changed in: python-boto (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/525675
Title:
20100222 images fail to boot in UEC (HTTP error 500 retrieving
e
** Changed in: python-boto (Ubuntu Lucid)
Status: Confirmed => Won't Fix
--
20100222 images fail to boot in UEC (HTTP error 500 retrieving ephemeral0
metadata)
https://bugs.launchpad.net/bugs/525675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Upon further inspection, it is definitely a different bug.
I have not actually seen this particular bug resurface. Only similar
symptoms. Thanks.
--
20100222 images fail to boot in UEC (HTTP error 500 retrieving ephemeral0
metadata)
https://bugs.launchpad.net/bugs/525675
You received this bug
@Dustin: make sure it's the same bug. I'd rather think it's a global
issue for the instance to access metadata in that topology, rather than
specifically an issue with the "ephemeral0" key, and that would make it
a new bug. Checking cloud-error.log should help.
--
20100222 images fail to boot in
Erg, I think I'm hitting this again on an Alpha3 eucalyptus
1.6.2-0ubuntu4 installation.
Funny thing is that I did not hit it in topo1 (CLC+WC+CC+SC, NC), but I
did hit it in topo3 (CLC+WC, CC+SC, NC).
I'm still investigating :-/
--
20100222 images fail to boot in UEC (HTTP error 500 retrieving
Indeed. Not sure how that slipped by. Thanks for catching it. See
r1200.
On Mon, Feb 22, 2010 at 8:05 PM, Dustin Kirkland
wrote:
> Chris-
>
> Almost, but not quite ... Looks to me like this commit fixed one
> ephemeral reference, but missed the other... Can you confirm/deny,
> Chris?
>
> bzr
Chris-
Almost, but not quite ... Looks to me like this commit fixed one
ephemeral reference, but missed the other... Can you confirm/deny,
Chris?
bzr diff -r 1185..1185.1.1
=== modified file
'clc/modules/cluster-manager/src/main/java/edu/ucsb/eucalyptus/cloud/cluster/VmInstance.java'
---
clc/
Hi Dustin,
This was fixed in the below revno. Closing the bug against Eucalyptus.
revno: 1185.1.1
committer: decker
branch nick: metadata
timestamp: Tue 2010-02-09 17:27:01 -0800
message:
ephemeral -> ephemer
** Branch linked: lp:ubuntu/eucalyptus
--
20100222 images fail to boot in UEC (HTTP error 500 retrieving ephemeral0
metadata)
https://bugs.launchpad.net/bugs/525675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Dan/upstream Eucalyptus-
I have a minor fix for this bug that I'd like for you to review and
merge into your 1.6.2 branch.
See:
lp:~kirkland/eucalyptus/525675
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Branch linked: lp:~kirkland/eucalyptus/525675
--
20100222
Okay, I rolled a package with Thierry's fix. I bundled and uploaded
today's Lucid's image, ran that Instance, and I was able to successfully
ssh into it.
Note, I did file a couple of new bugs, notably that I had to manually register
the image, rather than using uec-publish*
* Bug #525989
And t
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu3
---
eucalyptus (1.6.2-0ubuntu3) lucid; urgency=low
[ Thierry Carrez ]
*
clc/modules/cluster-manager/src/main/java/edu/ucsb/eucalyptus/cloud/cluster/VmInstance.java:
fix incomplete ephemeral block device mapping pat
For reference, regression introduced by an incomplete fix for bug 513842
--
20100222 images fail to boot in UEC (HTTP error 500 retrieving ephemeral0
metadata)
https://bugs.launchpad.net/bugs/525675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
@Scott: no eri reference for the one without ramdisk, so it's ok.
--
20100222 images fail to boot in UEC (HTTP error 500 retrieving ephemeral0
metadata)
https://bugs.launchpad.net/bugs/525675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I think I nailed it:
in
clc/modules/cluster-manager/src/main/java/edu/ucsb/eucalyptus/cloud/cluster/VmInstance.java
m.put( "block-device-mapping/", "emi\nephemeral0\nroot\nswap" );
m.put( "block-device-mapping/emi", "sda1" );
m.put( "block-device-mapping/ami", "sda1" );
m.put( "bl
On Mon, 22 Feb 2010, Thierry Carrez wrote:
> The image was registered through uec-register-tarball, is there anything
> specific to do to avoid booting with an initramfs ?
>
does euca-describe-images show a eri ?
if so, then uec-register tarbal is buggy,
--
20100222 images fail to boot in UEC
Adding a wishlist priority task against boto; it could fail more
gracefully with a more informative message.
** Also affects: python-boto (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-boto (Ubuntu Lucid)
Status: New => Confirmed
** Changed in: python-boto (Ubu
Right, boto 1.9 implemented recursive metadata retrieval in
get_instance_metadata (in boto/utils.py). That makes it fail if
Eucalyptus exposes a key (ephemeral0) that it doesn't support querying
to (error 500).
** Summary changed:
- 20100222 images fail to boot in UEC (no ephemeral0 metadata)
+ 2
** Attachment added: "Eucalyptus-side error log"
http://launchpadlibrarian.net/39537887/cloud-error.log
--
20100222 images fail to boot in UEC (no ephemeral0 metadata)
https://bugs.launchpad.net/bugs/525675
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
In karmic instance:
boto.utils.get_instance_userdata("2009-02-01") --> returns ''
boto.utils.get_instance_userdata("2009-04-04") --> returns ''
boto.utils.get_instance_metadata("2009-02-01") --> returns a full dict
boto.utils.get_instance_metadata("2009-04-04") --> returns the same full dict
In ka
I'm fairly sure I know what is wrong, or at least suspect something.
cloudinit/DataSourceEc2.py:
class DataSourceEc2(DataSource.DataSource):
api_ver = '2009-04-04'
Where, in ec2init (in karmic):
./ec2init/__init__.py:
class EC2Init:
api_ver = '2008-02-01'
The result of above is that lu
About the metadata service:
The metadata service seems to work well for the karmic cloud image ?
About the boot with initramfs:
The image was registered through uec-register-tarball, is there anything
specific to do to avoid booting with an initramfs ?
--
20100222 images fail to boot in UEC
htt
It would seem that your metadata service is not up for some reason.
However, one thing to note here is that you seem to be trying to boot
with an initramfs, but there is no initramfs in this build.
--
20100222 images fail to boot in UEC
https://bugs.launchpad.net/bugs/525675
You received this bu
Reinstalled my UEC setup to todays archive:
- Karmic image works alright
- Lucid image still fails
So I suppose it's an issue in the image rather than in Eucalyptus.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Confi
24 matches
Mail list logo