I have a few questions. What is the command you try to execute? How did you installed BoxGrinder? What versions you use? Could you please also attach log file located in log/ dir? But please strip the content and leave only last build.
To install boxgrinder-build I just followed the explanation in the installation guide http://community.jboss.org/wiki/BoxGrinderBuildInstallation)
curl http://repo.boxgrinder.org/boxgrinder/boxgrinder.repo > /etc/yum.repos.d/boxgrinder.repo
yum install rubygem-boxgrinder-build
Then I installed fedora plugin for boxgrinder-build :
yum install rubygem-boxgrinder-build-fedora-os-plugin
And I installed plugin for vmware platform :
yum install rubygem-boxgrinder-build-vmware-platform-plugin
The boxgrinder-build installed version is : 0.6.3
I use the following command line to create appliance : boxgrinder-build --trace -V f13-basic.appl
I installed BoxGrinder with yum command.
I execute : boxgrinder-build --trace -V f13-basic.appl
In attachement boxgrinder.log file.
boxgrinder.log.zip 6.4 K
Thanks for info. It looks like it's timing out on some HTTP resource. I added checking for HW acceleration availibility which involves a http call here. But I'm expecting a failure, so I assume it's not related to that. Unfortunately the stacktrace is collapsed.
Are you able to reproduce this bug every time? Where are you running BoxGrinder? Is it EC2? VMware? Your laptop?
I'm running BoxGrinder on SteamCannon appliance.
I'm using VirtualBox to launch SteamCannon appliance.
I'm able to reproduce this bug every time.
Please execute this command and paste the output (but remove the build/ dir before to execute a clean build)
boxgrinder-build -t -W f13-basic.appl
Marek, the commit link you've posted won't properly handle a Timeout::Error. I've added a comment to it with an example.
I's alive !!!
It works using your patch.
Thx a lot Marek.