Comment 12 for bug 665667

I had a look at Pets's patch, and it looks good, and would certainly
do the trick. Then, I did what I should have done last week, and wrote
a pipelined version that doesn't touch the disk with a temp file. Have
a look at revision 327 here;
http://bazaar.launchpad.net/~eucalyptus-maintainers/euca2ools/euca2ools-main/annotate/head:/euca2ools/euca2ools/__init__.py

Ideally, I'd get the aes128 stuff worked into the pipeline like the
ec2-ami-tools, but this (I think) is the right direction. I've applied
the changes to euca-bundle-image as well as euca-bundle-vol

David

On Thu, Dec 16, 2010 at 5:02 AM, Marek Goldmann
<email address hidden> wrote:
> Garrett, I tested Fedora 13 version - works great! Thank you!
>
> --
> You received this bug notification because you are a member of
> Eucalyptus Maintainers, which is the registrant for euca2ools.
> https://bugs.launchpad.net/bugs/665667
>
> Title:
>  couldn't launch an AMI bundled and uploaded using euca2ools
>
> Status in Euca2ools:
>  New
>
> Bug description:
>  I try to replace ec2-ami-tools with euca2ools package for BoxGrinder Build. If I switch back to ec2-ami-tools - everything works.
>
> Here is my bug report, see comments: https://jira.jboss.org/browse/BGBUILD-55
>
> I used euca2ools-1.3.1-1.fc13.noarch version.
>
>
>