On Jul 5, 2:51 pm, imase <igor.ma...@googlemail.com> wrote:
> After I change something and
> deployed again with capistrano, the classes rad in the .txt-file were
> away. But after the next time deploying it they were back again.
... So, what did you change? ;)
> node 'v00404' inherits basenode {
> import "webapps.pp"
>
> include mysql::client
>
> tcserver::instance { 'crowd':
> httpport => '8080',
> service_enable => true,
> }
>
> include crowd
>
> apache::vhost { 'v00404':
> priority => '20',
> port => '80',
> docroot => '/var/www/html',
> template => 'puppet4set/virtualhosts/crowd.conf.erb',
> }
>
> include general
>
> }
Ok, without reading through all of your manifests I'd resort to some
quick and dirty black box testing. Take node 'v00404', comment out
everything and then add in includes one by one until you can eliminate
each of the as having the stray "rad" module. I'd also look over your
site.pp and all the other imports you do (roles/*.pp) and see what
includes that class. "grep -R 'include rad'" perhaps :)
I don't use Capistrano but a quick Google makes me think you're using
it for remote file deployment of manifests to your Puppet master(s)?
Could you have old/broken versions of manifests lying around
somewhere? Puppet catalogs shouldn't change between runs - unless
you're relying on resources/classes being defined/tagged when Puppet
applies things in random order.
-Luke
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
