euca2ools: euca-bundle-vol strips leading zero (0) from user id

Bug #479823 reported by Eric Hammond
6
This bug affects 1 person
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-images-us/ubuntu-karmic-9.10-i386-server-20091027.1.manifest.xml
Ec2AvailabilityZone: us-east-1a
Ec2InstanceType: m1.small
Ec2Kernel: aki-5f15f636
Ec2Ramdisk: ari-0915f660
Package: euca2ools 1.0+bzr20091007-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: User Name 2.6.31-302.7-ec2
SourcePackage: euca2ools
Tags: ec2-images
Uname: Linux 2.6.31-302-ec2 i686

Revision history for this message
Eric Hammond (esh) wrote :
Erik Kronberg (eakron)
Changed in euca2ools (Ubuntu):
status: New → Confirmed
Changed in eucalyptus:
status: New → Confirmed
Revision history for this message
Thierry Carrez (ttx) wrote :

Eric, is it just euca-bundle-vol or are you experiencing issues with other euca2ools commands using that 0xxx account ?

Changed in euca2ools (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Neil Soman (neilsoman) wrote :

------------------------------------------------------------
revno: 231
committer: Neil
branch nick: euca2ools-1.0
timestamp: Fri 2009-11-13 10:02:43 -0800
message:
  fixes #479823
------------------------------------------------------------

Changed in eucalyptus:
status: Confirmed → Fix Committed
Revision history for this message
Neil Soman (neilsoman) wrote :

This fixes euca-bundle-vol and euca-bundle-image

Revision history for this message
Eric Hammond (esh) wrote :

Thierry: This is the first time I've typed any euca2ools commands, so I'm not sure where else there might be a problem. I don't think may commands would require the user id anyway.

Let me know if there are any specific ones you'd like me to test.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Fixed upstream, merging...

Changed in euca2ools (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Dustin Kirkland (kirkland)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package euca2ools - 1.1~bzr238-0ubuntu1

---------------
euca2ools (1.1~bzr238-0ubuntu1) lucid; urgency=low

  * Merge from upstream bzr revision; should fix:
    - LP: #497495 - parse dir path correctly in euca-delete-bundle
    - LP: #439366 - show kernel and ramdisk in euca-describe-images
    - LP: #495618 - show blk dev mappings in euca-describe-image-attribute
    - LP: #485106 - read credentials from config file
    - LP: #450044 - create tmpfs mounts in euca-bundle-vol
    - LP: #479823 - correctly handle userid in euca-bundle-vol
    - LP: #461301 - fix user data encoding
  * Also, created Ubuntu packaging branch, with a common root to the upstream
    project
 -- Dustin Kirkland <email address hidden> Tue, 05 Jan 2010 23:13:36 -0600

Changed in euca2ools (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Eric Hammond (esh) wrote :

I tried to test the fix, but ran into bug 505482.

Revision history for this message
Mitch Garnaat (mitch-garnaat) wrote :

Surprisingly, this never made it upstream. I just committed a fix upstream in r330.

Changed in eucalyptus:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.