Bug 903650

Summary: Update jeos AMI's for RHEL-6.4
Product: [Retired] CloudForms Cloud Engine Reporter: Chris Pelland <cpelland>
Component: imagefactoryAssignee: jrd <jrd>
Status: CLOSED ERRATA QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0.0CC: athomas, dajohnso, dmacpher, jlaska, morazi, slinaber
Target Milestone: 1.1.2Keywords: Rebase, Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
This enhancement adds support for Red Hat Enterprise Linux 6.4 Amazon Machine Images (AMI) on EC2 providers for CloudForms Cloud Engine.
Story Points: ---
Clone Of: 881404 Environment:
Last Closed: 2013-02-21 19:08:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 881404    
Bug Blocks: 889341, 903651    

Description Chris Pelland 2013-01-24 13:39:04 UTC
+++ This bug was initially created as a clone of Bug #881404 +++

Description of problem:

Add AMI's for RHEL-6.4 to imagefactory to support deploying EC2 RHEL-6.4 applications

Versions affected:
 * imagefactory-jeosconf-ec2-rhel-1.0.2-1.el6cf.noarch

--- Additional comment from Ian McLeod on 2013-01-23 15:04:56 EST ---

NOTE: 6.4 final AMIs are not yet available.  I have added the ability to build against the BETA AMIs.

This has been brewed as:

imagefactory-jeosconf-ec2-rhel-1.0.2_3_gadcc5de-1

It is my understanding that we can update this config file with the final AMIs when they are available.

Comment 3 Dave Johnson 2013-02-19 15:19:49 UTC
good 2 go with

[root@cloud-qe-14 ~]# rpm -qa | grep imagefac
imagefactory-jeosconf-ec2-fedora-1.0.3-1.el6cf.noarch
imagefactory-jeosconf-ec2-rhel-1.0.3-1.el6cf.noarch
imagefactory-1.0.3-1.el6cf.noarch

Comment 5 errata-xmlrpc 2013-02-21 19:08:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0545.html