Bug 841328 - EC2 upload style imagebuild fails to set x86_64 AMI architecture
EC2 upload style imagebuild fails to set x86_64 AMI architecture
Product: Fedora
Classification: Fedora
Component: imagefactory (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Ian McLeod
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-07-18 13:20 EDT by Etsuji Nakai
Modified: 2013-08-01 13:08 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 13:08:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch to add -a option to euca-register (810 bytes, patch)
2012-07-18 13:20 EDT, Etsuji Nakai
no flags Details | Diff

  None (edit)
Description Etsuji Nakai 2012-07-18 13:20:01 EDT
Created attachment 598952 [details]
Patch to add -a option to euca-register

Description of problem:

When using the upload style image build for Amazon EC2 (setting "ec2_build_style": "upload" in /etc/imagefactory/imagefactory.conf), the AMI architecure is always set to i386 even for x86_64 Fedora images.

Version-Release number of selected component (if applicable):

# rpm -qa | grep imagefactory

Additional info:

This is caused by missing to specify "-a <arch>" option to euca-register command in /usr/lib/python2.7/site-packages/imgfac/builders/Fedora_ec2_Builder.py. The attached is a patch to resolve it.
Comment 1 Ian McLeod 2012-07-18 13:57:58 EDT

The image architecture is set at the time the image is bundled.  I am confused as to how it would ever be necessary or sensible to override it at the time an image is registered.

The euca-register usage message suggests that it will default to i386 if no arch is specified.  This is incorrect.  At least in the version that we are using on RHEL6, if no arch is specified the code simply passes "None" to the register API command, which seems to simply inherit the architecture already set in the bundle.

Have you actually had the Factory produce an unbootable or otherwise unusable x86_64 bit image when using "upload" style builds?  I have repeatedly uploaded 64 bit builds (including all of the JEOS builds for Fedora) without issue.

Is it possible that this is a change in behaviour in the euca tools?
Comment 2 Ian McLeod 2012-07-18 14:10:23 EDT
Answering my own question, yes, it is a change in the euca-register behaviour.  The version in F17 (and possibly earlier versions) now actually does default to i386 when nothing is specified.

I'll fix this up.
Comment 3 Fedora End Of Life 2013-07-04 03:41:12 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2013-08-01 13:08:40 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.