-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloud doesn't get bootstrapped #71
Comments
Are you using chef at all in your clouds.rb? |
ya, sure, my clouds.rb looks like this: |
PP should bootstrap chef by manually installing it via gems. You do seem to be getting an error with gem not being found. What version of PP are you using. I noted a problem which auser fixed with regards to the path to the gem binary a couple of releases ago. |
i use this one "poolparty-1.6.3"...do i have to run any other command before "cloud start". |
Actually I'm using one a little older on my own branch and don't have any problems. Can you log into EC2 box with cloud-ssh and check if the chef gem was installed. If you are using an Ubuntu 9.10 AMI then you have to set the user to ubuntu but i don't see you specifiying a base AMI to use. gem list |
hm strange, yes, i can log in by "cloud ssh" and get this gem list by "gem list":
|
ok so PP has really screwed up because it hasn't managed to install the rubygems package manager. You could try do the following whilst logged into your machine. sudo apt-get install rubygems Then go back to your home machine and run cloud-start again. |
ok, i tried out your advice: root@domU-##-##-39-09-B5-A3:
And after cloud-start same error: sent 5435 bytes received 2706 bytes 2326.00 bytes/sec |
After "cloud start":
etc/chef/...
sent 123066 bytes received 1642 bytes 16627.73 bytes/sec
total size is 118041 speedup is 0.95
Warning: Permanently added 'ec2-###-##-##-##.compute-1.amazonaws.com,111.22.33.44' (RSA) to the list of known hosts.
bash: gem: command not found
No packages found matching chef.
bash: gem: command not found
bash: chef-solo: command not found
The text was updated successfully, but these errors were encountered: