Hey folks,
I am using puppet for some OpenStack deployments and on a new node things
look pretty good right until after the successful reception of a cert from
the puppet master. I get this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
$concat_basedir not defined. Try running again with pluginsync enabled at
/usr/share/puppet/modules/concat/manifests/setup.pp:25 on node
controller-1.example.com
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Things seem to be as they should in the setup.pp file it refers to. I have
searched for similar issues and cannot seem to find much on this issue. It
happens every time I build a node.
Below is the setup.pp file for your reference.
# Sets up the concat system.
#
# $concatdir is where the fragments live and is set on the fact
concat_basedir.
# Since puppet should always manage files in $concatdir and they should
# not be deleted ever, /tmp is not an option.
#
# $puppetversion should be either 24 or 25 to enable a 24 compatible
# mode, in 24 mode you might see phantom notifies this is a side effect
# of the method we use to clear the fragments directory.
#
# The regular expression below will try to figure out your puppet version
# but this code will only work in 0.24.8 and newer.
#
# It also copies out the concatfragments.sh file to ${concatdir}/bin
class concat::setup {
$id = $::id
$root_group = $id ? {
root => 0,
default => $id
}
if $::concat_basedir {
$concatdir = $::concat_basedir
} else {
fail ("\$concat_basedir not defined. Try running again with pluginsync
enabled")
}
$majorversion = regsubst($::puppetversion,
''^[0-9]+[.]([0-9]+)[.][0-9]+$'', ''\1'')
file{"${concatdir}/bin/concatfragments.sh":
owner => $id,
group => $root_group,
mode => ''0755'',
source => $majorversion ? {
24 => ''puppet:///concat/concatfragments.sh'',
default =>
''puppet:///modules/concat/concatfragments.sh''
};
[ $concatdir, "${concatdir}/bin" ]:
ensure => directory,
owner => $id,
group => $root_group,
mode => ''0750'';
## Old versions of this module used a different path.
''/usr/local/bin/concatfragments.sh'':
ensure => absent;
}
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/HJw_dn5BW_EJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> From: "Shannon McFarland" <shmcfarl@gmail.com> > To: puppet-users@googlegroups.com > Sent: Tuesday, July 31, 2012 9:06:04 AM > Subject: [Puppet Users] $concat_basedir not defined > > Hey folks, > > > I am using puppet for some OpenStack deployments and on a new node > things look pretty good right until after the successful reception > of a cert from the puppet master. I get this error: > > > > err: Could not retrieve catalog from remote server: Error 400 on > SERVER: $concat_basedir not defined. Try running again with pluginsync enabled atpretty much as it says here, try enabling pluginsync in your puppet.conf on the node using pluginsync=true -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
That is the issue. It is already enabled. [main] logdir=/var/log/puppet server=<fqdn_of_your_puppet_master> pluginsync=true On Tuesday, July 31, 2012 10:27:04 AM UTC-6, R.I. Pienaar wrote:> > > > ----- Original Message ----- > > From: "Shannon McFarland" <shmcfarl@gmail.com> > > To: puppet-users@googlegroups.com > > Sent: Tuesday, July 31, 2012 9:06:04 AM > > Subject: [Puppet Users] $concat_basedir not defined > > > > Hey folks, > > > > > > I am using puppet for some OpenStack deployments and on a new node > > things look pretty good right until after the successful reception > > of a cert from the puppet master. I get this error: > > > > > > > > err: Could not retrieve catalog from remote server: Error 400 on > > SERVER: $concat_basedir not defined. Try running again with pluginsync > enabled at > > pretty much as it says here, try enabling pluginsync in your > puppet.conf on the node using pluginsync=true >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/DLVbAUrlT9UJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> From: "Shannon McFarland" <shmcfarl@gmail.com> > To: puppet-users@googlegroups.com > Sent: Tuesday, July 31, 2012 9:30:35 AM > Subject: Re: [Puppet Users] $concat_basedir not defined > > That is the issue. It is already enabled. > > [main] > logdir=/var/log/puppet > server=<fqdn_of_your_puppet_master> > pluginsync=trueBest to show the full output then from "puppet agent --test" -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
localadmin@controller-1:/$ puppet agent --test err: Could not retrieve catalog from remote server: Error 400 on SERVER: $concat_basedir not defined. Try running again with pluginsync enabled at /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node controller-1.example.com warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run localadmin@controller-1:/$ Also, just so you have it: localadmin@controller-1:/$ puppet agent -td debug: Failed to load library ''rubygems'' for feature ''rubygems'' debug: Failed to load library ''selinux'' for feature ''selinux'' debug: Failed to load library ''ldap'' for feature ''ldap'' debug: /File[/home/localadmin/.puppet/ssl/private]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/ssl/private_keys]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/ssl/public_keys]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/var/state/graphs]: Autorequiring File[/home/localadmin/.puppet/var/state] debug: /File[/home/localadmin/.puppet/var/client_yaml]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/var/client_data]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/var/run]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/var/log]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/ssl/certs]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/var/state]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/ssl]: Autorequiring File[/home/localadmin/.puppet] debug: /File[/home/localadmin/.puppet/var/lib]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/var/state/last_run_report.yaml]: Autorequiring File[/home/localadmin/.puppet/var/state] debug: /File[/home/localadmin/.puppet/ssl/certs/controller-1.example.com.pem]: Autorequiring File[/home/localadmin/.puppet/ssl/certs] debug: /File[/home/localadmin/.puppet/ssl/crl.pem]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/var/clientbucket]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/var]: Autorequiring File[/home/localadmin/.puppet] debug: /File[/home/localadmin/.puppet/ssl/certs/ca.pem]: Autorequiring File[/home/localadmin/.puppet/ssl/certs] debug: /File[/home/localadmin/.puppet/var/facts]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/var/state/last_run_summary.yaml]: Autorequiring File[/home/localadmin/.puppet/var/state] debug: /File[/home/localadmin/.puppet/ssl/public_keys/controller-1.example.com.pem]: Autorequiring File[/home/localadmin/.puppet/ssl/public_keys] debug: /File[/home/localadmin/.puppet/ssl/certificate_requests]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/ssl/private_keys/controller-1.example.com.pem]: Autorequiring File[/home/localadmin/.puppet/ssl/private_keys] debug: Finishing transaction 70190598951000 debug: /File[/home/localadmin/.puppet/ssl/certs/ca.pem]: Autorequiring File[/home/localadmin/.puppet/ssl/certs] debug: /File[/home/localadmin/.puppet/ssl/crl.pem]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/ssl/private]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/var/log]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/ssl/private_keys/controller-1.example.com.pem]: Autorequiring File[/home/localadmin/.puppet/ssl/private_keys] debug: /File[/home/localadmin/.puppet/ssl/private_keys]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/ssl/public_keys]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/ssl/public_keys/controller-1.example.com.pem]: Autorequiring File[/home/localadmin/.puppet/ssl/public_keys] debug: /File[/home/localadmin/.puppet/var/facts]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/var/lib]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/ssl/certs]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/ssl/certificate_requests]: Autorequiring File[/home/localadmin/.puppet/ssl] debug: /File[/home/localadmin/.puppet/ssl/certs/controller-1.example.com.pem]: Autorequiring File[/home/localadmin/.puppet/ssl/certs] debug: /File[/home/localadmin/.puppet/var]: Autorequiring File[/home/localadmin/.puppet] debug: /File[/home/localadmin/.puppet/ssl]: Autorequiring File[/home/localadmin/.puppet] debug: /File[/home/localadmin/.puppet/var/run]: Autorequiring File[/home/localadmin/.puppet/var] debug: /File[/home/localadmin/.puppet/var/state]: Autorequiring File[/home/localadmin/.puppet/var] debug: Finishing transaction 70190569310660 debug: Using cached certificate for ca debug: Using cached certificate for controller-1.example.com debug: Finishing transaction 70190568910180 debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for controller-1.example.com debug: Using cached certificate_revocation_list for ca err: Could not retrieve catalog from remote server: Error 400 on SERVER: $concat_basedir not defined. Try running again with pluginsync enabled at /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node controller-1.example.com warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (yaml) debug: report supports formats: b64_zlib_yaml raw yaml; using yaml On Tuesday, July 31, 2012 10:31:59 AM UTC-6, R.I. Pienaar wrote:> > > > ----- Original Message ----- > > From: "Shannon McFarland" <shmcfarl@gmail.com> > > To: puppet-users@googlegroups.com > > Sent: Tuesday, July 31, 2012 9:30:35 AM > > Subject: Re: [Puppet Users] $concat_basedir not defined > > > > That is the issue. It is already enabled. > > > > [main] > > logdir=/var/log/puppet > > server=<fqdn_of_your_puppet_master> > > pluginsync=true > > Best to show the full output then from "puppet agent --test" >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/fYLKa3TElPYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> From: "Shannon McFarland" <shmcfarl@gmail.com> > To: puppet-users@googlegroups.com > Sent: Tuesday, July 31, 2012 9:35:54 AM > Subject: Re: [Puppet Users] $concat_basedir not defined > > > localadmin@controller-1:/$ puppet agent --test > err: Could not retrieve catalog from remote server: Error 400 on > SERVER: $concat_basedir not defined. Try running again with > pluginsync enabled at > /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node > controller-1.example.com > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > localadmin@controller-1:/$Looks like you''re not running it as root, this probably affects what config is being used. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
OK. I am rebuilding the node again to check something. I will manually run it as root but this is not a solution other than this test as we won''t be having our nodes come up running as root accounts. On Tuesday, July 31, 2012 11:07:45 AM UTC-6, R.I. Pienaar wrote:> > > > ----- Original Message ----- > > From: "Shannon McFarland" <shmcfarl@gmail.com> > > To: puppet-users@googlegroups.com > > Sent: Tuesday, July 31, 2012 9:35:54 AM > > Subject: Re: [Puppet Users] $concat_basedir not defined > > > > > > localadmin@controller-1:/$ puppet agent --test > > err: Could not retrieve catalog from remote server: Error 400 on > > SERVER: $concat_basedir not defined. Try running again with > > pluginsync enabled at > > /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node > > controller-1.example.com > > warning: Not using cache on failed catalog > > err: Could not retrieve catalog; skipping run > > localadmin@controller-1:/$ > > Looks like you''re not running it as root, this probably affects > what config is being used. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/QXtZ0oLQApMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Yeah, I ran it with ''sudo'' and it pulled the plugin and kicked off. So, how can I point to the correct configuration without running as root or sudo in my preseed? On Tuesday, July 31, 2012 11:26:11 AM UTC-6, Shannon McFarland wrote:> > OK. I am rebuilding the node again to check something. I will manually > run it as root but this is not a solution other than this test as we won''t > be having our nodes come up running as root accounts. > > On Tuesday, July 31, 2012 11:07:45 AM UTC-6, R.I. Pienaar wrote: >> >> >> >> ----- Original Message ----- >> > From: "Shannon McFarland" <shmcfarl@gmail.com> >> > To: puppet-users@googlegroups.com >> > Sent: Tuesday, July 31, 2012 9:35:54 AM >> > Subject: Re: [Puppet Users] $concat_basedir not defined >> > >> > >> > localadmin@controller-1:/$ puppet agent --test >> > err: Could not retrieve catalog from remote server: Error 400 on >> > SERVER: $concat_basedir not defined. Try running again with >> > pluginsync enabled at >> > /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node >> > controller-1.example.com >> > warning: Not using cache on failed catalog >> > err: Could not retrieve catalog; skipping run >> > localadmin@controller-1:/$ >> >> Looks like you''re not running it as root, this probably affects >> what config is being used. >> >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/9wmGhWSDYZYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> From: "Shannon McFarland" <shmcfarl@gmail.com> > To: puppet-users@googlegroups.com > Sent: Tuesday, July 31, 2012 10:46:37 AM > Subject: Re: [Puppet Users] $concat_basedir not defined > > Yeah, I ran it with ''sudo'' and it pulled the plugin and kicked off. > So, how can I point to the correct configuration without running as > root or sudo in my preseed?then you should edit whatever "puppet agent --configprint config" reports as the right config file for the user else run puppet with a specific --config=/etc/puppet/puppet.conf or similar -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Here is the deal, we are trying to launch the puppet agent --test from the preseed file using this line: d-i preseed/late_command string in-target puppet agent --test --waitforcert 0 || true; I tried using ''puppet agent --config=/etc/puppet/puppet.conf --test --waitforcert 0'' given your suggestion but I don''t think that it is a valid flag for the puppet agent (--config). During the late_command run it gets a cert from the master just fine but then dies: Jul 31 23:13:08 puppet-agent[5244]: Caching certificate for controller-1.example.com Jul 31 23:13:08 in-target: ^[[0;32minfo: Caching certificate for controller-1.example.com^[[0m Jul 31 23:13:09 puppet-agent[5244]: Caching certificate_revocation_list for ca Jul 31 23:13:09 in-target: ^[[0;32minfo: Caching certificate_revocation_list for ca^[[0m Jul 31 23:13:11 puppet-agent[5244]: Could not retrieve catalog from remote server: Error 400 on SERVER: $concat_basedir not defined. Try running again with pluginsync enabled at /usr/share/pup pet/modules/concat/manifests/setup.pp:25 on node controller Jul 31 23:13:11 in-target: ^[[1;35merr: Could not retrieve catalog from remote server: Error 400 on SERVER: $concat_basedir not defined. Try running again with pluginsync enabled at /usr/share /puppet/modules/concat/manifests/setup.pp:25 on node control Jul 31 23:13:11 puppet-agent[5244]: Not using cache on failed catalog Jul 31 23:13:11 in-target: ^[[0;33mwarning: Not using cache on failed catalog^[[0m Jul 31 23:13:11 puppet-agent[5244]: Could not retrieve catalog; skipping run Jul 31 23:13:11 in-target: ^[[1;35merr: Could not retrieve catalog; skipping run^[[0m Does the ''puppet agent'' command support a path to the correct puppet.conf? Shannon On Tuesday, July 31, 2012 1:52:59 PM UTC-6, R.I. Pienaar wrote:> > > > ----- Original Message ----- > > From: "Shannon McFarland" <shmcfarl@gmail.com> > > To: puppet-users@googlegroups.com > > Sent: Tuesday, July 31, 2012 10:46:37 AM > > Subject: Re: [Puppet Users] $concat_basedir not defined > > > > Yeah, I ran it with ''sudo'' and it pulled the plugin and kicked off. > > So, how can I point to the correct configuration without running as > > root or sudo in my preseed? > > then you should edit whatever "puppet agent --configprint config" > reports as the right config file for the user else run puppet with > a specific --config=/etc/puppet/puppet.conf or similar >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/gJtyRr22APcJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> From: "Shannon McFarland" <shmcfarl@gmail.com> > To: puppet-users@googlegroups.com > Sent: Tuesday, July 31, 2012 4:22:31 PM > Subject: Re: [Puppet Users] $concat_basedir not defined > > Here is the deal, we are trying to launch the puppet agent --test > from the preseed file using this line: > d-i preseed/late_command string in-target puppet agent --test > --waitforcert 0 || true; > > > I tried using ''puppet agent --config=/etc/puppet/puppet.conf --test > --waitforcert 0'' given your suggestion but I don''t think that it is > a valid flag for the puppet agent (--config). > > > During the late_command run it gets a cert from the master just fine > but then dies: > > > > Jul 31 23:13:08 puppet-agent[5244]: Caching certificate for > controller-1.example.com > Jul 31 23:13:08 in-target: ^[[0;32minfo: Caching certificate for > controller-1.example.com^[[0m > Jul 31 23:13:09 puppet-agent[5244]: Caching > certificate_revocation_list for ca > Jul 31 23:13:09 in-target: ^[[0;32minfo: Caching > certificate_revocation_list for ca^[[0m > Jul 31 23:13:11 puppet-agent[5244]: Could not retrieve catalog from > remote server: Error 400 on > SERVER: $concat_basedir not defined. Try running again with > pluginsync enabled at /usr/share/pup > pet/modules/concat/manifests/setup.pp:25 on node controller > Jul 31 23:13:11 in-target: ^[[1;35merr: Could not retrieve catalog > from remote server: Error 400 > on SERVER: $concat_basedir not defined. Try running again with > pluginsync enabled at /usr/share > /puppet/modules/concat/manifests/setup.pp:25 on node control > Jul 31 23:13:11 puppet-agent[5244]: Not using cache on failed catalog > Jul 31 23:13:11 in-target: ^[[0;33mwarning: Not using cache on failed > catalog^[[0m > Jul 31 23:13:11 puppet-agent[5244]: Could not retrieve catalog; > skipping run > Jul 31 23:13:11 in-target: ^[[1;35merr: Could not retrieve catalog; > skipping run^[[0m > > > Does the ''puppet agent'' command support a path to the correct > puppet.conf?it does, are you certain it has pluginsync=true in the config file at that time? you can also just do --pluginsync on the command line -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
hi. i fixed it after read the docs: Enabling Pluginsync After setting up the directory structure, we then need to turn on pluginsync in our puppet.conf configuration file on *both the master and the clients:* [main] pluginsync = true On Tuesday, July 31, 2012 11:06:04 PM UTC+7, Shannon McFarland wrote:> > Hey folks, > > I am using puppet for some OpenStack deployments and on a new node things > look pretty good right until after the successful reception of a cert from > the puppet master. I get this error: > > err: Could not retrieve catalog from remote server: Error 400 on SERVER: > $concat_basedir not defined. Try running again with pluginsync enabled at > /usr/share/puppet/modules/concat/manifests/setup.pp:25 on node > controller-1.example.com > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > Things seem to be as they should in the setup.pp file it refers to. I > have searched for similar issues and cannot seem to find much on this > issue. It happens every time I build a node. > > Below is the setup.pp file for your reference. > > # Sets up the concat system. > # > # $concatdir is where the fragments live and is set on the fact > concat_basedir. > # Since puppet should always manage files in $concatdir and they should > # not be deleted ever, /tmp is not an option. > # > # $puppetversion should be either 24 or 25 to enable a 24 compatible > # mode, in 24 mode you might see phantom notifies this is a side effect > # of the method we use to clear the fragments directory. > # > # The regular expression below will try to figure out your puppet version > # but this code will only work in 0.24.8 and newer. > # > # It also copies out the concatfragments.sh file to ${concatdir}/bin > class concat::setup { > $id = $::id > $root_group = $id ? { > root => 0, > default => $id > } > > if $::concat_basedir { > $concatdir = $::concat_basedir > } else { > fail ("\$concat_basedir not defined. Try running again with pluginsync > enabled") > } > > $majorversion = regsubst($::puppetversion, > ''^[0-9]+[.]([0-9]+)[.][0-9]+$'', ''\1'') > > file{"${concatdir}/bin/concatfragments.sh": > owner => $id, > group => $root_group, > mode => ''0755'', > source => $majorversion ? { > 24 => ''puppet:///concat/concatfragments.sh'', > default => ''puppet:///modules/concat/concatfragments.sh'' > }; > > [ $concatdir, "${concatdir}/bin" ]: > ensure => directory, > owner => $id, > group => $root_group, > mode => ''0750''; > > ## Old versions of this module used a different path. > ''/usr/local/bin/concatfragments.sh'': > ensure => absent; > } > } > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ZL-kqVBZNCYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.