euca2ools: euca-bundle-vol strips leading zero (0) from user id
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Eucalyptus |
Fix Released
|
Undecided
|
Unassigned | ||
euca2ools (Ubuntu) |
Fix Released
|
Medium
|
Dustin Kirkland |
Bug Description
Binary package hint: euca2ools
Using an AWS account which has a user id starting with a zero (0), I used the euca-bundle-vol to bundle a running Karmic instance, then euca-upload-bundle to upload to S3, then euca-register to try to register the uploaded bundle.
The euca-register command dies with the following error:
AuthFailure: User ('063491364108') is not image creator ('63491364108')
When running the euca-bundle-vol command, I specified the complete user id including the leading zero. The euca-register command only takes an AWS Access Key ID.
It appears that euca-bundle-vol may have stripped off the leading zero (treating it as a number?) when it created the bundle.
I think the error might be coming from the EC2 API when it tries to compare the user id stored in the bundle with the user id indicated by the AWS Access Key ID.
I have no problems bundling, uploading, and registering AMIs with the ec2-ami-tools package.
ProblemType: Bug
Architecture: i386
Date: Tue Nov 10 06:37:18 2009
DistroRelease: Ubuntu 9.10
Ec2AMI: ami-1515f67c
Ec2AMIManifest: ubuntu-
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-5f15f636
Ec2Ramdisk: ari-0915f660
Package: euca2ools 1.0+bzr20091007
PackageArchitec
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: euca2ools
Tags: ec2-images
Uname: Linux 2.6.31-302-ec2 i686
Changed in euca2ools (Ubuntu): | |
status: | New → Confirmed |
Changed in eucalyptus: | |
status: | New → Confirmed |
Changed in eucalyptus: | |
status: | Fix Committed → Fix Released |
Eric, is it just euca-bundle-vol or are you experiencing issues with other euca2ools commands using that 0xxx account ?