Hi,
In the foreman apache module, I get an error when trying to apply the
"::config" part of it.
The section that causes problem is:
file{ "${apache::params::configdir}/${apache::params::conffile}":
mode=> '0644',
notify => Exec['reload-apache'],
require => Class['apache::i
$sourcepath = $operatingsystem ? {
AIX => "/etc/puppet/sudo/files/sudoers",
default => "puppet:///SLESSUDO/sudoers",
}
file {"$sourcepath":
you set sourcepath as the targeted path of the file, this won't work
and I assume it is also not
sorry, I assu,e SLES_SUDO is not your servername, so in this case it should
be:
puppet:///SLES_SUDO/..
On Fri, Mar 5, 2010 at 5:29 PM, Ohad Levy wrote:
>
>
> On Fri, Mar 5, 2010 at 5:13 PM, Haris Farooque wrote:
>
>> yes, I tried in the same way, here is my manifest;
>>
>> err: Could not run P
On Fri, Mar 5, 2010 at 5:13 PM, Haris Farooque wrote:
> yes, I tried in the same way, here is my manifest;
>
> err: Could not run Puppet configuration client: Parameter path failed: File
> paths must be fully qualified, not 'puppet:/SLES_SUDO/sudoers' at */
> etc/puppet/manifests/*:
>
> it should
yes, I tried in the same way, here is my manifest;
filesever.conf:
--
[SLESSUDO]
path /etc/puppet/modules/sudo/files/
allow *.mydomain.com
-
$sourcepath = $operatingsystem ? {
AIX => "/etc/puppet/sudo/files/sud
*err: Could not run Puppet configuration client: Parameter path
failed: File paths must be fully qualified, not
'puppet:/myFileSrc**/' at /etc/puppet/manifests/:158
*whats wrong here? *
can you show us your manifest in question?
cheers epte
--
You received this message because you are sub
Haris Farooque wrote:
*err: Could not run Puppet configuration client: Parameter path failed:
File paths must be fully qualified, not 'puppet:/myFileSrc**/'
at /etc/puppet/manifests/:158
The correct format is "puppet:///myFileSrc/". Or more general,
"puppet:", but if you don't specify
an
I was using Puppet 0.24.8 and now upgrade the puppet server and client
both to 0.25.4 (on 1 machine i.e. server and client), but i am facing
some problems. While testing, some of the configs which were/are running
fine on older version generates error here;
for instance,
i have defined the Fi
