Deploy issue

[Bob]

I have an app that i have deployed onto a slicehost slice using
moonshine.

I recently setup a new slice and im trying to move my app over. I have
changed the deploy.rb to match the new slice. setup my moonshine.yml
accordingly. but for some reason i cant get the deploy to take. I have
noticed that i do not get rails, mysql, or any gems installed when
doing cap deploy:setup or cap deploy.

i have noticed a few errors like missing gem etc.. that i have fixed
by manual install. but the most recent i cannot figure out
Parameter require failed: No title provided and title '"package"' is
not a valid resource reference

any help would be great.

Thanks

B

[dreamcat four]

Hi,
I have seen this too. It happens when shadow_puppet calls puppet with
the gems recipie. For some reason, puppet is reporting that it doesn't
recognise the package keyword (within the gems recipie).

here:
shadow_puppet/examples.rb

recipe :some_gems

def some_gems
package 'rails', :ensure => :updated, :provider => :gem
package 'railsmachine', :ensure => '1.0.5', :provider => :gem,
:require => package('capistrano')
package 'capistrano', :ensure => :updated, :provider => :gem
end

Uncaught exception
Puppet::Error

Parameter require failed: No title provided and title '"package"' is
not a valid resource reference

/Users/id/.gem/ruby/1.8/gems/puppet-0.25.0/lib/puppet/resource/reference.rb:30:in
`initialize'


This happens with...
puppet-0.25.0
puppet-0.25.x (git branch)

They fixed a very similar-looking error recently in 2.5.x branch:
http://groups.google.com/group/puppet-users/browse_thread/thread/5ce7e3346f20fefd
http://projects.reductivelabs.com/issues/2686

Commit:
http://github.com/reductivelabs/puppet/commit/bca3b70437666a8b840af032cab20fc1ea4f18a2

Roll back to an older version of puppet, perahps 0.24.8, and Active
Recort 2.3.2 ?

Puppet team seem to prefer to be contacted on IRC,
irc://irc.freenode.net/puppet

Otherwise can open a ticket,
http://projects.reductivelabs.com/issues/create

[Jesse Newland]

Hey Everyone -

This appears to be an issue that's specific to Moonshine/ShadowPuppet
and Puppet 0.25. I'm working on getting this fixed. For now, the fix
is to remove Puppet 0.25 and install 0.24.8:

sudo gem install puppet
sudo gem install puppet -v 0.24.8

Sorry about this bug. We're working on it!

Regards -

Jesse Newland
---
je...@railsmachine.com
404.216.1093