Sean,
I've not been able to replicate this issue at all. It worked
successfully for me.
Could you try the following steps/provide some info to help us diagnose
if there is a general issue.
First just ensure everything is fresh:
1. `yum update -y`
2. Delete your old build and log directories, or use a fresh directory.
Run BoxGrinder again with --trace to see if it still fails (just the
basic build is enough).
If it *does* fail again, can you please provide the following info:
1. `gem list -d boxgrinder`
2. `rpm -q rubygem-boxgrinder-build rubygem-boxgrinder-core`
3. How did you get to root? By su, su -, sudo -i?
4. Upload log/boxgrinder.log to gist or fpaste.
Many thanks!
Marc
On 13/12/2011 12:34, Marc Savy wrote:
Hi Sean,
I'm taking a look at this issue and shall see if I can discover what is
going on. I'll get back to you soon :).
Marc
On 12/12/2011 18:39, sean darcy wrote:
Thanks for the suggestion, but no luck. It failed with permissions
issues. Odd since I'm running as root on the boxgrinder EC2 appliance.
Also, it seems to be grabbing the F15 kernels.
cat f16.appl
name: f16
os:
name: fedora
version: 16
boxgrinder-build f16.appl -p ec2 -d ebs
I, [2011-12-12T12:39:34.170950 #19829] INFO -- : Validating appliance
definition from f16.appl file...
I, [2011-12-12T12:39:34.173858 #19829] INFO -- : Appliance definition
is valid.
I, [2011-12-12T12:39:34.219834 #19829] INFO -- : Building 'f16'
appliance for i686 architecture.
I, [2011-12-12T12:39:34.226844 #19829] INFO -- : Resolving packages
added to f16 appliance definition file...
I, [2011-12-12T12:39:41.109246 #19829] INFO -- : All additional
packages for f16 appliance successfully resolved.
I, [2011-12-12T12:39:41.109595 #19829] INFO -- : Building f16
appliance...
supermin helper [00000ms] whitelist = (not specified), host_cpu = i686,
kernel = (null), initrd = (null), appliance = (null)
supermin helper [00001ms] inputs[0] = /usr/lib/guestfs/supermin.d
checking modpath /lib/modules/2.6.38.8-32.fc15.i686.PAE is a directory
picked vmlinuz-2.6.38.8-32.fc15.i686.PAE because modpath
/lib/modules/2.6.38.8-32.fc15.i686.PAE exists
checking modpath /lib/modules/2.6.41.4-1.fc15.i686.PAE is a directory
picked vmlinuz-2.6.41.4-1.fc15.i686.PAE because modpath
/lib/modules/2.6.41.4-1.fc15.i686.PAE exists
supermin helper [00024ms] finished creating kernel
supermin helper [00025ms] visiting /usr/lib/guestfs/supermin.d
supermin helper [00476ms] visiting /usr/lib/guestfs/supermin.d/base.img
supermin helper [00987ms] visiting /usr/lib/guestfs/supermin.d/daemon.img
supermin helper [01007ms] visiting /usr/lib/guestfs/supermin.d/hostfiles
supermin helper [06003ms] visiting /usr/lib/guestfs/supermin.d/init.img
supermin helper [12993ms] finished creating appliance
I, [2011-12-12T13:29:30.645307 #19829] INFO -- : Executing post
operations after build...
I, [2011-12-12T13:33:31.819301 #19829] INFO -- : Base image for f16
appliance was built successfully.
F, [2011-12-12T13:33:32.802477 #19829] FATAL -- : Errno::EPERM:
Operation not permitted -
/root/build/appliances/i686/fedora/16/fedora-16-i386-ec2/1.0/fedora-plugin/tmp/imgcreate-62qmYe/install_root/proc/sys
/usr/lib/ruby/1.8/fileutils.rb:1231:in `chown'
/usr/lib/ruby/1.8/fileutils.rb:1231:in `chown'
/usr/lib/ruby/1.8/fileutils.rb:967:in `chown_R'
/usr/lib/ruby/1.8/fileutils.rb:1331:in `traverse'
/usr/lib/ruby/1.8/fileutils.rb:965:in `chown_R'
/usr/lib/ruby/1.8/fileutils.rb:964:in `each'
/usr/lib/ruby/1.8/fileutils.rb:964:in `chown_R'
/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.9.8/lib/boxgrinder-build/appliance.rb:144:in
`execute_plugin'
/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.9.8/lib/boxgrinder-build/appliance.rb:105:in
`execute_plugin_chain'
/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.9.8/lib/boxgrinder-build/appliance.rb:105:in
`each'
/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.9.8/lib/boxgrinder-build/appliance.rb:105:in
`execute_plugin_chain'
/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.9.8/lib/boxgrinder-build/appliance.rb:120:in
`create'
/usr/lib/ruby/gems/1.8/gems/boxgrinder-build-0.9.8/bin/boxgrinder-build:189
/usr/bin/boxgrinder-build:19:in `load'
/usr/bin/boxgrinder-build:19
Thanks,
sean
On 12/12/2011 11:17 AM, Marek Goldmann wrote:
Yes, we should make the page more clear about what process was used
to get the official ones vs. what you can do with BoxGrinder.
Sean, everything on that page is up to date. You just need to create
your own appliance definition. Here you have a sample for Fedora 16
JEOS (save it as f16.appl):
name: f16
os:
name: fedora
version: 16
More details here:
http://boxgrinder.org/tutorials/appliance-definition/
Then build it by executing boxgrinder-build f16.appl -p ec2 -d ebs.
If you have troubles, please tell me.
--Marek
On 12 gru 2011, at 17:03, sean darcy wrote:
Thanks for the responses. I would suggest that
https://fedoraproject.org/wiki/Cloud_SIG/EC2_Creation be either
corrected or taken down.
Is there another, more recent, step-by-step description of how to build
a fedora EC2 ebs-backed ami? For instance, are there F16 appl files
available?
sean
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
