Hide Forgot
Description of problem: 1.. t1.micro has been know to run out of memory during yum updates... I suggest we use a larger hwp for a default 2. I also suggest we allow the customer to choose which hwp they want in /etc/imagefactory/imagefactory.conf :)
I thought this hwp was used for push only, so tiny should be ok, right? Why is it running yum update? I'm probably confused.
adding ce-sprint-next bugs to ce-sprint
Implemented here: https://github.com/aeolusproject/imagefactory/commit/a4fdc5fe5778d5e663fbd6be23e83f6a5493401e I have removed use of t1.micro entirely. The default instance types for EBS snapshots are now the same as S3 snapshots. That is, m1.small for 32 bit and m1.large for 64 bit. Pull request submitted as well. Switching to ON_QA
Update - Please use this commit as the basis for any isolated testing: https://github.com/aeolusproject/imagefactory/commit/cbdcb8dd912f685588cf629f33fe75e69ca88116
bugs in verified or on_qa moving off tracker
Verified for i386 (m1.small) and x86_64 (m1.large) on RHEL62 with this packages : # rpm -qa|grep 'aeolus\|imagefactory-\|oz-\|iwhd' rubygem-imagefactory-console-0.5.0-4.20110824113238gitd9debef.el6.noarch aeolus-conductor-daemons-0.9.0-0.20120111153517gite55da85.el6.noarch aeolus-conductor-doc-0.9.0-0.20120111153517gite55da85.el6.noarch aeolus-configure-2.6.0-0.20120112133633git8701011.el6.noarch imagefactory-jeosconf-ec2-rhel-1.0.0rc2.1-1.el6.noarch rubygem-aeolus-image-0.4.0-0.20120111093551git67fdf6f.el6.noarch rubygem-arel-2.0.10-0.aeolus.el6.noarch rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch oz-0.8.0-0.20111219203204git5775e9d.el6.noarch iwhd-1.2-3.el6.x86_64 imagefactory-jeosconf-ec2-fedora-1.0.0rc2.1-1.el6.noarch rubygem-aeolus-cli-0.4.0-0.20120111093540git5ec8dc7.el6.noarch imagefactory-1.0.0rc2.1-1.el6.noarch aeolus-conductor-0.9.0-0.20120111153517gite55da85.el6.noarch aeolus-all-0.9.0-0.20120111153517gite55da85.el6.noarch
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/RHEA-2012-0588.html