cloud start causes NoMethorError?

[Emil Tin]

hi,
when i try to run 'cloud start' i get this error:

/Users/emiltin/.gem/ruby/1.8/gems/poolparty-0.2.84/bin/../lib/
poolparty/helpers/../../../bin/../lib/poolparty/modules/
cloud_resourcer.rb:42:in `setup_dev': undefined method `ip' for
nil:NilClass (NoMethodError)
from /Users/emiltin/.gem/ruby/1.8/gems/poolparty-0.2.84/bin/../lib/
poolparty/helpers/../../../bin/cloud-start:13:in
`temp_PoolParty::Cloud::Cloud_#<PoolParty::Pool::Pool:0x17ceb14>'
from /Users/emiltin/.gem/ruby/1.8/gems/poolparty-0.2.84/bin/../lib/
poolparty/helpers/../../../bin/../lib/poolparty/core/object.rb:78:in
`send'
from /Users/emiltin/.gem/ruby/1.8/gems/poolparty-0.2.84/bin/../lib/
poolparty/helpers/../../../bin/../lib/poolparty/core/object.rb:78:in
`run_in_context'
from /Users/emiltin/.gem/ruby/1.8/gems/poolparty-0.2.84/bin/../lib/
poolparty/helpers/../../../bin/../lib/poolparty/poolparty/cloud.rb:
17:in `with_cloud'
from /Users/emiltin/.gem/ruby/1.8/gems/poolparty-0.2.84/bin/../lib/
poolparty/helpers/../../../bin/cloud-start:12
from /Users/emiltin/.gem/ruby/1.8/gems/poolparty-0.2.84/bin/../lib/
poolparty/helpers/../../../bin/cloud-start:11:in `each'
from /Users/emiltin/.gem/ruby/1.8/gems/poolparty-0.2.84/bin/../lib/
poolparty/helpers/../../../bin/cloud-start:11




the error occures inside this method:

def setup_dev
unless ::File.exists?("#{full_keypair_basename_path}.pub")
cmd = "scp #{ssh_array.join(" ")} #{Base.user}@#
{master.ip}:.ssh/authorized_keys #{full_keypair_basename_path}.pub"
vputs "Running #{cmd}"
Kernel.system(cmd)
end
end


i've tried cutting down my clouds.pool file to almost nothing, but it
doesn't make a difference.

i've added my AWS keys to the .bash_profile.

i also ran cloud add_keypair, which didn't return any output or error.
i'm not sure what it was supposed to do?


i just installed the poolparty gem, as well as the poolparty plugins
for apache2, mysql and rails. but running 'cloud -V' or 'pool -V' both
returns nil, which seems weird. but it seems i'm running 0.2.84
looking at the paths in the error message.


any ideas?