Puppet file copy

117 views
Skip to first unread message

Bai Shen

unread,
Aug 31, 2012, 10:18:31 AM8/31/12
to puppet...@googlegroups.com
I'm trying to install solr using puppet.  I have a module installing tomcat.  Now I'm trying to make another module that installs the solr files.  However, it's not copying the file.  Any ideas what I'm doing wrong?

init.pp:
class solr {
        file { '/opt/apache-tomcat/conf/Catalina/localhost':
                source => 'puppet://modules/solr/solr.xml',
                owner => 'tomcat',
                group => 'tomcat',
                mode => '311',
                notify => Service['apache-tomcat'],
                require => Package['apache-tomcat'],
        }
}

Ramin K

unread,
Aug 31, 2012, 1:03:52 PM8/31/12
to puppet...@googlegroups.com
You're missing ensure => present,

Ramin

Dick Davies

unread,
Aug 31, 2012, 1:04:16 PM8/31/12
to puppet...@googlegroups.com
isn't /opt/apache-tomcat/conf/Catalina/localhost a directory?
You should still get output saying that on a puppet agent run though.
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

Josh Cooper

unread,
Aug 31, 2012, 2:23:10 PM8/31/12
to puppet...@googlegroups.com
On Fri, Aug 31, 2012 at 10:03 AM, Ramin K <ramin...@badapple.net> wrote:
> On 8/31/2012 7:18 AM, Bai Shen wrote:

>> class solr {
>> file { '/opt/apache-tomcat/conf/Catalina/localhost':
>> source => 'puppet://modules/solr/solr.xml',

That should be puppet:///modules/solr/solr.xml

The way to think about puppet URI's is that the server host and port
have been omitted, so there are two slashes for puppet://, and the URI
path always has a leading slash, /modules/solr/solr.xml.

See http://docs.puppetlabs.com/guides/file_serving.html

--
Josh Cooper
Developer, Puppet Labs

Bai Shen

unread,
Sep 4, 2012, 11:21:34 AM9/4/12
to puppet...@googlegroups.com
Along with everything else that was pointed out, it turned out that I was using a node with the same name as my module, and therefore it was not being called.

Reply all
Reply to author
Forward
0 new messages