Closed patcon closed 12 years ago
And here's the important stuff from the end (cucumber tests and all):
ruby-1.9.2-p180/tool/mkconfig.rb
ruby-1.9.2-p180/tool/node_name.rb
ruby-1.9.2-p180/tool/parse.rb
ruby-1.9.2-p180/tool/rbinstall.rb
ruby-1.9.2-p180/tool/rmdirs
ruby-1.9.2-p180/tool/rubytest.rb
ruby-1.9.2-p180/tool/runruby.rb
ruby-1.9.2-p180/tool/strip-rdoc.rb
ruby-1.9.2-p180/tool/test/
ruby-1.9.2-p180/tool/test/test_jisx0208.rb
ruby-1.9.2-p180/tool/transcode-tblgen.rb
ruby-1.9.2-p180/tool/vtlh.rb
ruby-1.9.2-p180/tool/ytab.sed
ruby-1.9.2-p180/transcode.c
ruby-1.9.2-p180/transcode_data.h
ruby-1.9.2-p180/transdb.h
ruby-1.9.2-p180/util.c
ruby-1.9.2-p180/variable.c
ruby-1.9.2-p180/version.c
ruby-1.9.2-p180/version.h
ruby-1.9.2-p180/vm.c
ruby-1.9.2-p180/vm.inc
ruby-1.9.2-p180/vm_core.h
ruby-1.9.2-p180/vm_dump.c
ruby-1.9.2-p180/vm_eval.c
ruby-1.9.2-p180/vm_exec.c
ruby-1.9.2-p180/vm_exec.h
ruby-1.9.2-p180/vm_insnhelper.c
ruby-1.9.2-p180/vm_insnhelper.h
ruby-1.9.2-p180/vm_method.c
ruby-1.9.2-p180/vm_opts.h
ruby-1.9.2-p180/vmtc.inc
ruby-1.9.2-p180/vsnprintf.c
ruby-1.9.2-p180/win32/
ruby-1.9.2-p180/win32/configure.bat
ruby-1.9.2-p180/win32/dir.h
ruby-1.9.2-p180/win32/enc-setup.mak
ruby-1.9.2-p180/win32/ifchange.bat
ruby-1.9.2-p180/win32/Makefile.sub
ruby-1.9.2-p180/win32/mkexports.rb
ruby-1.9.2-p180/win32/README.win32
ruby-1.9.2-p180/win32/resource.rb
ruby-1.9.2-p180/win32/rm.bat
ruby-1.9.2-p180/win32/rmdirs.bat
ruby-1.9.2-p180/win32/setup.mak
ruby-1.9.2-p180/win32/win32.c
ruby-1.9.2-p180/win32/winmain.c
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/tmp/ruby-1.9.2-p180':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details
make: *** No targets specified and no makefile found. Stop.
Installing chef and puppet
postinstall.sh: line 35: /usr/local/bin/gem: No such file or directory
FATAL: Could not install chef
ERROR: exit code 1
/Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/ssh.rb:183:in `execute': Exitcode was not what we expected (RuntimeError)
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/session.rb:360:in `build'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/ssh.rb:22:in `call'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/ssh.rb:22:in `when_ssh_login_works'
from /Library/Ruby/Gems/1.8/gems/net-ssh-2.1.4/lib/net/ssh.rb:190:in `start'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/ssh.rb:21:in `when_ssh_login_works'
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/timeout.rb:53:in `timeout'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/ssh.rb:14:in `when_ssh_login_works'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/session.rb:348:in `build'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/session.rb:891:in `transaction'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/session.rb:346:in `build'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/session.rb:341:in `each'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/session.rb:341:in `build'
from /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/command.rb:46:in `build'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/task.rb:22:in `send'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/invocation.rb:109:in `send'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/invocation.rb:109:in `invoke'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor.rb:205:in `basebox'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/task.rb:22:in `send'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
from /Library/Ruby/Gems/1.8/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
from /Library/Ruby/Gems/1.8/gems/vagrant-0.8.6/bin/vagrant:21
from /usr/bin/vagrant:19:in `load'
from /usr/bin/vagrant:19
Patrick-Connollys-MacBook-Pro:vagrant homebase$ vagrant basebox validate centos57_64
Feature: vagrant box validation
As a valid vagrant box
I need to comply to a set of rules
Scenario: Checking login # /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:5
. When I ssh to "127.0.0.1" with the following credentials: # veewee-0.2.0/validation/features/steps/ssh_steps.rb:56
| username | password | port |
| vagrant | vagrant | 7222 |
And I run "whoami" # veewee-0.2.0/validation/features/steps/ssh_steps.rb:98
done!
vagrant
Then I should see "vagrant" in the output # veewee-0.2.0/validation/features/steps/ssh_steps.rb:167
Scenario: Checking sudo # /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:12
. When I ssh to "127.0.0.1" with the following credentials: # veewee-0.2.0/validation/features/steps/ssh_steps.rb:56
| username | password | port |
| vagrant | vagrant | 7222 |
And I run "sudo whoami" # veewee-0.2.0/validation/features/steps/ssh_steps.rb:98
done!
root
Then I should see "root" in the output # veewee-0.2.0/validation/features/steps/ssh_steps.rb:167
Scenario: Checking ruby # /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:19
. When I ssh to "127.0.0.1" with the following credentials: # veewee-0.2.0/validation/features/steps/ssh_steps.rb:56
| username | password | port |
| vagrant | vagrant | 7222 |
And I run ". /etc/profile ;ruby --version 2> /dev/null 1> /dev/null; echo $?" # veewee-0.2.0/validation/features/steps/ssh_steps.rb:98
done!
127
Then I should see "0" in the output # veewee-0.2.0/validation/features/steps/ssh_steps.rb:167
expected: /0/
got: "127\r\n" (using =~)
Diff:
@@ -1,2 +1,2 @@
-/0/
+127
(RSpec::Expectations::ExpectationNotMetError)
Scenario: Checking gem # /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:26
. When I ssh to "127.0.0.1" with the following credentials: # veewee-0.2.0/validation/features/steps/ssh_steps.rb:56
| username | password | port |
| vagrant | vagrant | 7222 |
And I run ". /etc/profile; gem --version 2> /dev/null 1> /dev/null ; echo $?" # veewee-0.2.0/validation/features/steps/ssh_steps.rb:98
done!
127
Then I should see "0" in the output # veewee-0.2.0/validation/features/steps/ssh_steps.rb:167
expected: /0/
got: "127\r\n" (using =~)
Diff:
@@ -1,2 +1,2 @@
-/0/
+127
(RSpec::Expectations::ExpectationNotMetError)
Scenario: Checking chef # /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:33
. When I ssh to "127.0.0.1" with the following credentials: # veewee-0.2.0/validation/features/steps/ssh_steps.rb:56
| username | password | port |
| vagrant | vagrant | 7222 |
And I run ". /etc/profile ;chef-client --version 2> /dev/null 1>/dev/null; echo $?" # veewee-0.2.0/validation/features/steps/ssh_steps.rb:98
done!
127
Then I should see "0" in the output # veewee-0.2.0/validation/features/steps/ssh_steps.rb:167
expected: /0/
got: "127\r\n" (using =~)
Diff:
@@ -1,2 +1,2 @@
-/0/
+127
(RSpec::Expectations::ExpectationNotMetError)
Scenario: Checking puppet # /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:40
. When I ssh to "127.0.0.1" with the following credentials: # veewee-0.2.0/validation/features/steps/ssh_steps.rb:56
| username | password | port |
| vagrant | vagrant | 7222 |
And I run ". /etc/profile ; puppet --version 2> /dev/null 1>/dev/null; echo $?" # veewee-0.2.0/validation/features/steps/ssh_steps.rb:98
done!
127
Then I should see "0" in the output # veewee-0.2.0/validation/features/steps/ssh_steps.rb:167
expected: /0/
got: "127\r\n" (using =~)
Diff:
@@ -1,2 +1,2 @@
-/0/
+127
(RSpec::Expectations::ExpectationNotMetError)
Scenario: Checking shared folders # /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:47
. When I ssh to "127.0.0.1" with the following credentials: # veewee-0.2.0/validation/features/steps/ssh_steps.rb:56
| username | password | keyfile | port |
| vagrant | vagrant | vagrant-private.key | 7222 |
And I run "mount|grep veewee-validation" # veewee-0.2.0/validation/features/steps/ssh_steps.rb:98
done!
Then I should see "veewee-validation" in the output # veewee-0.2.0/validation/features/steps/ssh_steps.rb:167
expected: /veewee-validation/
got: nil (using =~) (RSpec::Expectations::ExpectationNotMetError)
Failing Scenarios:
cucumber /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:19 # Scenario: Checking ruby
cucumber /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:26 # Scenario: Checking gem
cucumber /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:33 # Scenario: Checking chef
cucumber /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:40 # Scenario: Checking puppet
cucumber /Library/Ruby/Gems/1.8/gems/veewee-0.2.0/lib/veewee/../../validation/vagrant.feature:47 # Scenario: Checking shared folders
7 scenarios (5 failed, 2 passed)
21 steps (5 failed, 16 passed)
0m3.427s
It looks like early on in the run, yum cannot find the kernel headers, and other packages needed for this to work.
I've created the updated templates for Centos 5.7 - they are not currently included in version 0.20, but have bene included in 0.3.0.alpha1 and up (install at your own risk).
You can "backport" the template by downloading/cloning the master
branch and placing the templates in $WHEREVER/veewee-0.2.0/templates/
Maybe hold on for this - I've found a couple of bugs in the template, fixing now.
Same here , this issue has been address by accepting the pull request.
Have done essentially no work to convert so far, but just copied the CentOS-5.6-x86_64-netboot template over and changed the mirror and iso settings. But still, thought this might help :)
Here's the output from the ssh session from postinstall.sh: