Comment 5 for bug 565043

Revision history for this message
Kevin Jordan (kevin-kjordan) wrote : Re: [Bug 565043] Re: Walrus unable to decrypt image for NC

Yes, it was bundled with the credentials I got from euca_conf
--get-credentials.

I've set that to 500GB. It was initially 30GB. I've only registered the
debian one available from the extras tab this time. Previously I'd
registered both the Debian and Ubuntu images and both got the same error. I
can use euca-download-bundle and get it that way just fine.

On Sat, Apr 17, 2010 at 3:23 PM, Neil Soman <email address hidden> wrote:

> Don't see anything obviously wrong from the log snippet you posted.
> Complete logs (all 3) will definitely help.
>
> Two questions,
>
> -Was the image bundled with the correct credentials?
>
> -What is the image cache size (admin web interface -> configuration tab)
> and are you sure you are not running out of image cache space? How many
> images have been registered so far?
>
> --
> Walrus unable to decrypt image for NC
> https://bugs.launchpad.net/bugs/565043
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Eucalyptus: New
>
> Bug description:
> I've uploaded a couple of the default images and tried to start instances,
> but it times out and ends up erroring out that it's unable to decrypt the
> image.
>
> Two files are created where it would be decrypting it in the bukkit:
> -rw-r--r-- 1 eucalyptus eucalyptus 10M Apr 16 16:28
> debian.5-0.x86-64.img-KTck4EQ..crypt.gz
> -rw-r--r-- 1 eucalyptus eucalyptus 10M Apr 16 16:28
> debian.5-0.x86-64.img-KTck4EQ..tgz
>
> These stay at 10M though and the md5sum doesn't match any other files for
> either.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/eucalyptus/+bug/565043/+subscribe
>