[Puppet Users] Re: Using puppet to import database on client side

[Al @ Lab42]

Seems like the command /usr/bin/mysql -uroot -proot papa < filedump.sql  
returns an error when executed.
Try to run it directly to understand why and note that you have to eecute it 
only once and not at every Puppet runs, that is achieved with 
refreshonly => true,
or
unless => "a command that checks if the exec has been done and returns 
true",

Al

-- 
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/-/d3cUqUNnMVQJ.
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.

Re: [Puppet Users] How to use notify to invoke something prior to a change

[Nan Liu]

On Thu, Jul 14, 2011 at 8:55 AM, PBWebGuy  wrote:
> I have a Chicken and Egg scenario here and trying to come up with a
> way to solve it.
>
> I have a mount definition that manages mount points.  The problem
> arises when the mount point changes after it is in use.  Case in
> point, we have mount points for the mysql data and logs directories.
> If we change the configuration of the mount (i.e. options) then Puppet
> will unmount and remount the directory automatically.  MySQL will not
> be to happy with that.
>
> So, what I want to do is to optionally pass the service name to the
> define and to shut it down, but ONLY if the mount command detects a
> change and mysql is running.
>
> The problem I have is that if the mount command notifies shutdown,
> then the shutdown happens to late and I only what to shutdown if mount
> detects a change.  It would be great if there was a "pre-notify"
> option to force an exec to run beforehand.
>
> I tried putting a Notify and Require from the mount to the stop
> service exec but that causes a circular reference and just the require
> in the mount does not trigger the stop service exec because of the
> refreshonly=>true which is necessary so that it doesn't always run.
>
> Any thoughts?
>
> Thanks, John
>
> Here's what I have:
>
>      exec { "stop service for remount $name":
>         onlyif      => ["test -f /etc/init.d/$service", "service
> $service status"],
>         command     => "service $service stop",
>         refreshonly => true,
>         notify      => Exec["restart service for remount $name"],
>      }
>
>      # Mount the file system
>      mount { $name:
>         name    => $mount_point,
>         ensure  => mounted,
>         options => $options,
>         atboot  => $atboot,
>         fstype  => $fstype,
>         device  => $device,
>         dump    => 0,
>         pass    => 0,
>         require => Exec["stop service for remount $name"],
>         # notify  => Exec["stop service for remount $name"],
>      }
>
>      exec { "restart service for remount $name":
>         command     => "service $service start",
>         refreshonly => true,
>         require     => Mount[$name],
>      }

No good way at the moment since the type and provider doesn't allow
resource to trigger actions between detection of resource state and
updates to the resource. This would be an interesting feature request
if there isn't one yet. At the moment, you can abuse puppet resource
with noop to check if there will be changes to the resource (puppet
resource does not support arrays, maybe we need -e to support
arbitrary puppet manifests string):

Exec { "shutdown service":
  command     => "service $service stop",
  onlyif => "puppet resource --noop mount name=$mount_point ... | grep notice"
}

Thanks,

Nan
-- 
==
Join us in PDX for PuppetConf: http://bit.ly/puppetconfsig

-- 
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.

[Puppet Users] yum.puppetlabs.com re-do

[Michael Stahnke]

 I'd like to reorganize yum.puppetlabs.com.

As it is, it's a little cluttered, and it's unclear what each folder
and such are for.

Here's what I'd like to do:

yum.puppetlabs.com/

 /el
   /4
   /5
   /6
 /fedora
  /14
  /15
 /sles
  /11

Under each of those we'll have

products -- stuff we actually create as puppet labs

dependencies -- stuff that we use in order to maximize our usage of
Puppet Labs products

 then i386, x86_64 and SRPMS under each of those


I'd like to have  puppetlabs-release rpm as well, that will let you
install this.



All RPMS will be signed by the Puppet Labs signing key.



This work will take place next week.


Mike

-- 
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.

Re: [Puppet Users] facts_terminus = rest

[Ohad Levy]

On 2011 7 15 22:22, "Glenn Bailey"  wrote:
>
> I scrapped the idea and just gonna go with using activemq and
> connecting to the DB directly. I think this may scale better in the
> long run anyway ;-)
>
Not to hijack the thread, but multiple puppetmasters facts, rest etc is
supported for a long time with foreman.

Ohad
> On Thu, Jul 14, 2011 at 10:09 PM, Scott Smith  wrote:
> > I personally couldn't get it to work (no facts in Dashboard), but only
spent
> > a short amount of time on it.
> >
> > On Thu, Jul 14, 2011 at 1:50 PM, Glenn Bailey <
replic...@dallaslamers.org>
> > wrote:
> >>
> >> Anyone using this? I'm trying to setup a separate inventory server for
> >> multiple puppet masters to report back. For testing purposes I have in
> >> my auth.conf:
> >>
> >> path /facts
> >> auth any
> >> method find, search
> >> allow *
> >>
> >> Then on the "slave" puppet masters I have in the puppet.conf [master]
> >> section:
> >>
> >> facts_terminus = rest
> >> inventory_server = SERVER.DOMAIN.BLAH
> >> inventory_port = 8140
> >>
> >> Then when I run I puppet agent --test, I simply get the following:
> >>
> >> err: Could not retrieve catalog from remote server: Error 400 on
> >> SERVER: certificate verify failed
> >>
> >> Throwing the puppet master into debug mode and I see the exact same
> >> error w/o anything else. I can't seem to find any documentation on
> >> this sans the standard:
> >>
> >> http://docs.puppetlabs.com/guides/inventory_service.html
> >>
> >> I saw a previous mention about a possible bug on the mailing list here:
> >>
> >>
> >>
http://groups.google.com/group/puppet-users/browse_thread/thread/682402305dc01ea9
> >>
> >> But never saw anything else .. :-( Does the "master fact" server need
> >> to be a certificate authority as well?
> >>
> >> --
> >> I've seen things you people wouldn't believe. Attack ships on fire off
> >> the shoulder of Orion. I watched C-beams glitter in the dark near the
> >> Tannhauser gate. All those moments will be lost in time... like tears
> >> in rain... Time to die.
> >>
> >> --
> >> 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.
> >>
> >
> > --
> > 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.
> >
>
>
>
> --
> I've seen things you people wouldn't believe. Attack ships on fire off
> the shoulder of Orion. I watched C-beams glitter in the dark near the
> Tannhauser gate. All those moments will be lost in time... like tears
> in rain... Time to die.
>
> --
> 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.
>

-- 
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.

Re: [Puppet Users] facts_terminus = rest

[Glenn Bailey]

I scrapped the idea and just gonna go with using activemq and
connecting to the DB directly. I think this may scale better in the
long run anyway ;-)

On Thu, Jul 14, 2011 at 10:09 PM, Scott Smith  wrote:
> I personally couldn't get it to work (no facts in Dashboard), but only spent
> a short amount of time on it.
>
> On Thu, Jul 14, 2011 at 1:50 PM, Glenn Bailey 
> wrote:
>>
>> Anyone using this? I'm trying to setup a separate inventory server for
>> multiple puppet masters to report back. For testing purposes I have in
>> my auth.conf:
>>
>> path /facts
>> auth any
>> method find, search
>> allow *
>>
>> Then on the "slave" puppet masters I have in the puppet.conf [master]
>> section:
>>
>> facts_terminus = rest
>> inventory_server = SERVER.DOMAIN.BLAH
>> inventory_port = 8140
>>
>> Then when I run I puppet agent --test, I simply get the following:
>>
>> err: Could not retrieve catalog from remote server: Error 400 on
>> SERVER: certificate verify failed
>>
>> Throwing the puppet master into debug mode and I see the exact same
>> error w/o anything else. I can't seem to find any documentation on
>> this sans the standard:
>>
>> http://docs.puppetlabs.com/guides/inventory_service.html
>>
>> I saw a previous mention about a possible bug on the mailing list here:
>>
>>
>> http://groups.google.com/group/puppet-users/browse_thread/thread/682402305dc01ea9
>>
>> But never saw anything else .. :-( Does the "master fact" server need
>> to be a certificate authority as well?
>>
>> --
>> I've seen things you people wouldn't believe. Attack ships on fire off
>> the shoulder of Orion. I watched C-beams glitter in the dark near the
>> Tannhauser gate. All those moments will be lost in time... like tears
>> in rain... Time to die.
>>
>> --
>> 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.
>>
>
> --
> 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.
>



-- 
I've seen things you people wouldn't believe. Attack ships on fire off
the shoulder of Orion. I watched C-beams glitter in the dark near the
Tannhauser gate. All those moments will be lost in time... like tears
in rain... Time to die.

-- 
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.

[Puppet Users] Re: Using puppet to import database on client side

[newguy]

I tried the path /usr/bin but it showed the following error:

change from notrun to 0 failed: /usr/bin/mysql -uroot -proot papa <
filedump.sql returned 1 instead of one of [0] at /etc/puppet/ping/
modules/vim/manifests/init.pp:29
exec {"Get db":
command => "/usr/bin/mysql -uroot -proot papa <
dumpfile.sql",
require => exec["Retrieve dump"],
}
Thanks for your efforts
On Jul 15, 10:41 am, Nan Liu  wrote:
> On Fri, Jul 15, 2011 at 10:37 AM, newguy  wrote:
> > Hey
> > Thanks for the help, I was able to download the dump file successfully
> > but when I try to execute the mysql command I get the following error:
>
> > Could not run Puppet configuration client: 'mysql -uroot -pring
>
> > parasol < download.php?i=hV0wsTfa' is both unqualifed and specified no
>
> > search path at /etc/puppet/environments/abcd/modules/vim/manifests/
> > init.pp:25
>
> > here is my exec where am trying to run mysql command:
>
> > exec {"Get db":
> >                command => "mysql -uroot -proot papa < dumpfile.sql",
> >                require => exec["Retrieve dump"],
> >        }
>
> You need to provide the full path to mysql such as /usr/bin/mysql, or
> supply the path.
>
> Nan

-- 
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.

[Puppet Users] Re: Using puppet to import database on client side

[newguy]

Yes I did that and got the following error:
change from notrun to 0 failed: /usr/bin/mysql -uroot -pring parasol
<
download.php?i=hV0wsTfa returned 1 instead of one of [0] at /etc/
puppet/environments/ss/modules/vim/manifests/init.pp:29
This is my exec:
exec {"Get db":
command => "/usr/bin/mysql -uroot -pring parasol <
download.php?
i=hwwws22s",
require => exec["Retrieve dump"],
}
Please help

On Jul 15, 10:41 am, Nan Liu  wrote:
> On Fri, Jul 15, 2011 at 10:37 AM, newguy  wrote:
> > Hey
> > Thanks for the help, I was able to download the dump file successfully
> > but when I try to execute the mysql command I get the following error:
>
> > Could not run Puppet configuration client: 'mysql -uroot -pring
>
> > parasol < download.php?i=hV0wsTfa' is both unqualifed and specified no
>
> > search path at /etc/puppet/environments/abcd/modules/vim/manifests/
> > init.pp:25
>
> > here is my exec where am trying to run mysql command:
>
> > exec {"Get db":
> >                command => "mysql -uroot -proot papa < dumpfile.sql",
> >                require => exec["Retrieve dump"],
> >        }
>
> You need to provide the full path to mysql such as /usr/bin/mysql, or
> supply the path.
>
> Nan

-- 
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.

[Puppet Users] Re: Using puppet to import database on client side

[newguy]

Yes I did that and got the following error:
change from notrun to 0 failed: /usr/bin/mysql -uroot -pring parasol <
download.php?i=hV0wsTfa returned 1 instead of one of [0] at /etc/
puppet/environments/ss/modules/vim/manifests/init.pp:29

This is my exec:

exec {"Get db":
command => "/usr/bin/mysql -uroot -pring parasol < download.php?
i=hV0wsTfa",
require => exec["Retrieve dump"],
}


Please help


On Jul 15, 10:41 am, Nan Liu  wrote:
> On Fri, Jul 15, 2011 at 10:37 AM,newguy wrote:
> > Hey
> > Thanks for the help, I was able to download the dump file successfully
> > but when I try to execute the mysql command I get the following error:
>
> > Could not run Puppet configuration client: 'mysql -uroot -pring
>
> > parasol < download.php?i=hV0wsTfa' is both unqualifed and specified no
>
> > search path at /etc/puppet/environments/abcd/modules/vim/manifests/
> > init.pp:25
>
> > here is my exec where am trying to run mysql command:
>
> > exec {"Get db":
> >                command => "mysql -uroot -proot papa < dumpfile.sql",
> >                require => exec["Retrieve dump"],
> >        }
>
> You need to provide the full path to mysql such as /usr/bin/mysql, or
> supply the path.
>
> Nan

-- 
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.

Re: [Puppet Users] Re: Custom fact scoping problem

[Ken Barber]

IMHO I don't think I want nested facts to work :-). The evaluation
order alone is trouble some ... ie. the inner fact wouldn't get added
until the enclosed fact is evaluated ... doesn't sound like something
you would want in ordinary circumstances :-). Remember sometimes fact
information is gather on a per-fact basis and doing nesting would
break this for your inner fact.

I think using the confine is fine :-).

ken.

On Fri, Jul 15, 2011 at 7:02 PM, Greg Etling  wrote:
> I have it working, but I'm curious if this might be a bug with nested
> Facter.add statements?
> I simply un-nested them and used a 'confine' statement to make things work.
> New facts posted below:
> Facter.add("is_ldap_server") do
>   setcode do
>     if  FileTest.exists?("/usr/sbin/slapd")
>       %x{echo yes}.chomp
>     else
>       %x{echo no}.chomp
>     end
>   end
> end
> Facter.add("ldap_rid") do
>   confine :is_ldap_server => :yes
>   setcode do
>     case Facter::network_eth0
>     when "192.168.96.0"
>       Facter::ipaddress[/[0-9]+$/].chomp
>     when "192.168.97.0"
>       ( 500 + Facter::ipaddress_eth0[/[0-9]+$/].chomp.to_i )
>     end
>   end
> end
>
> --
> 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/-/ob5dE8e2afMJ.
> 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.
>



-- 
"Join us for PuppetConf, September 22nd and 23rd in Portland, OR:
http://bit.ly/puppetconfsig";

-- 
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.

[Puppet Users] Re: Custom fact scoping problem

[Greg Etling]

I have it working, but I'm curious if this might be a bug with nested 
Facter.add statements?

I simply un-nested them and used a 'confine' statement to make things work. 
New facts posted below:
Facter.add("is_ldap_server") do
  setcode do
if  FileTest.exists?("/usr/sbin/slapd")
  %x{echo yes}.chomp
else
  %x{echo no}.chomp
end
  end
end

Facter.add("ldap_rid") do
  confine :is_ldap_server => :yes
  setcode do
case Facter::network_eth0
when "192.168.96.0"
  Facter::ipaddress[/[0-9]+$/].chomp
when "192.168.97.0"
  ( 500 + Facter::ipaddress_eth0[/[0-9]+$/].chomp.to_i )
end
  end
end

-- 
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/-/ob5dE8e2afMJ.
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.

[Puppet Users] Re: Custom fact scoping problem

[Greg Etling]

Well, whatever problem I'm seeing is due to the nested Facter.add 
statements...when I pulled the ldap_rid one out and ran it separately, it 
worked.

-- 
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/-/rVoETeJ5MqwJ.
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.

Re: [Puppet Users] new variable scoping in templates

[Greg Etling]

Nan, that's exactly what I thought. I posted another thread with more 
details on the issue I'm seeing though, so I won't go into my issues here.

On Friday, July 15, 2011 1:42:23 PM UTC-4, Nan Liu wrote:
>
> Facts are top scope, so simply ::factname such as
> scope.lookupvar('::operatingsystem')
>
>
>

-- 
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/-/TbRoQNKsY00J.
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.

Re: [Puppet Users] new variable scoping in templates

[Nan Liu]

Facts are top scope, so simply ::factname such as
scope.lookupvar('::operatingsystem')

On Fri, Jul 15, 2011 at 8:26 AM, Greg Etling  wrote:
> Justin,
> What would the syntax be along those lines when looking up custom facts?
>
> --
> 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/-/BB3TAoW6PVEJ.
> 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.
>



-- 
==
Join us in PDX for PuppetConf: http://bit.ly/puppetconfsig

-- 
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.

Re: [Puppet Users] Re: Using puppet to import database on client side

[Nan Liu]

On Fri, Jul 15, 2011 at 10:37 AM, newguy  wrote:
> Hey
> Thanks for the help, I was able to download the dump file successfully
> but when I try to execute the mysql command I get the following error:
>
> Could not run Puppet configuration client: 'mysql -uroot -pring
>
> parasol < download.php?i=hV0wsTfa' is both unqualifed and specified no
>
> search path at /etc/puppet/environments/abcd/modules/vim/manifests/
> init.pp:25
>
>
>
> here is my exec where am trying to run mysql command:
>
> exec {"Get db":
>                command => "mysql -uroot -proot papa < dumpfile.sql",
>                require => exec["Retrieve dump"],
>        }

You need to provide the full path to mysql such as /usr/bin/mysql, or
supply the path.

Nan

-- 
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.

[Puppet Users] Re: Using puppet to import database on client side

[newguy]

Hey
Thanks for the help, I was able to download the dump file successfully
but when I try to execute the mysql command I get the following error:

Could not run Puppet configuration client: 'mysql -uroot -pring

parasol < download.php?i=hV0wsTfa' is both unqualifed and specified no

search path at /etc/puppet/environments/abcd/modules/vim/manifests/
init.pp:25



here is my exec where am trying to run mysql command:

exec {"Get db":
command => "mysql -uroot -proot papa < dumpfile.sql",
require => exec["Retrieve dump"],
}
Thanks for your efforts


On Jul 15, 10:03 am, newguy  wrote:
> Yes Marek, it does make sense and thanks for this help, lemme try what
> Al @ Lab42 has suggested first as I have been told to do things by
> Puppet. In case I fail then I will look in to your suggestion.
>
> Thanks anyways
>
> On Jul 14, 11:43 pm, "Marek Dohojda"  wrote:
>
>
>
>
>
>
>
> > Personally I don't think using puppet for this would not be the best
> > solution.  However here is what I would do.  Write a shell script to do what
> > you need, and than use puppet's EXEC statement to launch this command as
> > needed.
>
> > You could also use custom Fact for this.
>
> > For instance have you custom script do the export, while within puppet class
> > you have an "if" that looks if a particular fact is true.  if it is set to
> > true than launch that exec command to do copy and import on your other host.
>
> > Does that make sense?
>
> > -Original Message-
> > From:newguy
> > Sent: Thursday, July 14, 2011 10:10 PM
> > To: Puppet Users
> > Subject: [Puppet Users] Re: Using puppet to import database on client side
>
> > Guys somebody please help
>
> > On Jul 14, 5:32 pm,newguy wrote:
> > > Hi guys
> > > I have database dump available on pastebin/exzxzxz
>
> > > I want the puppet server to download the dump from pastebin and store
> > > it at a fixed location(suppose /home/dump) and then open mysql on the
> > > client side(mysql is installed on the client)  and run the import
> > > command so that the downloaded dump is used to make a database on the
> > > client .
>
> > > Please help guys.
>
> > > Both client and server are Ubuntu 10.04.
>
> > > Thanks
>
> > --
> > 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 
> > athttp://groups.google.com/group/puppet-users?hl=en.

-- 
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.

Re: [Puppet Users] Re: Seemingly random failures after 2.7.1 upgrade

[Gustavo Soares]

done!

http://projects.puppetlabs.com/issues/8433

Gus

On Fri, Jul 15, 2011 at 7:59 AM, Peter Meier  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> > same problem for me.. I've notice the problem on modules using
> > autoloading...
> >
> > I think I will stick to version 2.6.9...
>
> can you at least file a detailed bug report? Thanks! Otherwise the
> situation can't be really improved...
>
> ~pete
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk4gHX4ACgkQbwltcAfKi3/GXQCgpZMNyTEiV1USVG1qpxgCh3mE
> +S8AoJnCLIYreiOg3bXr1zf4u56eZivk
> =NF0L
> -END PGP SIGNATURE-
>
> --
> 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.
>
>

-- 
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.

[Puppet Users] Re: Using puppet to import database on client side

[newguy]

Yes Marek, it does make sense and thanks for this help, lemme try what
Al @ Lab42 has suggested first as I have been told to do things by
Puppet. In case I fail then I will look in to your suggestion.

Thanks anyways

On Jul 14, 11:43 pm, "Marek Dohojda"  wrote:
> Personally I don't think using puppet for this would not be the best
> solution.  However here is what I would do.  Write a shell script to do what
> you need, and than use puppet's EXEC statement to launch this command as
> needed.
>
> You could also use custom Fact for this.
>
> For instance have you custom script do the export, while within puppet class
> you have an "if" that looks if a particular fact is true.  if it is set to
> true than launch that exec command to do copy and import on your other host.
>
> Does that make sense?
>
>
>
>
>
>
>
> -Original Message-
> From:newguy
> Sent: Thursday, July 14, 2011 10:10 PM
> To: Puppet Users
> Subject: [Puppet Users] Re: Using puppet to import database on client side
>
> Guys somebody please help
>
> On Jul 14, 5:32 pm,newguy wrote:
> > Hi guys
> > I have database dump available on pastebin/exzxzxz
>
> > I want the puppet server to download the dump from pastebin and store
> > it at a fixed location(suppose /home/dump) and then open mysql on the
> > client side(mysql is installed on the client)  and run the import
> > command so that the downloaded dump is used to make a database on the
> > client .
>
> > Please help guys.
>
> > Both client and server are Ubuntu 10.04.
>
> > Thanks
>
> --
> 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 
> athttp://groups.google.com/group/puppet-users?hl=en.

-- 
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.

[Puppet Users] Custom fact scoping problem

[Greg Etling]

OK, I think this is probably something that is entirely my fault, but I 
cannot access a facter fact that I need. It evaluates only on certain 
clients, and is dependent upon the creation and value of another fact. 
Client and server are puppet 2.6.6 and facter 1.5.9.

Custom fact defined in common module:
/etc/puppetdev/modules/common/lib/facter/openldap.rb
Facter.add("is_ldap_server") do
  setcode do
if  FileTest.exists?("/usr/sbin/slapd")
  Facter.add("ldap_rid") do
setcode do
  case Facter::network_eth0
  when "192.168.96.0"
Facter::ipaddress[/[0-9]+$/].chomp
  when "192.168.97.0"
( 500 + Facter::ipaddress_eth0[/[0-9]+$/].chomp.to_i )
  end
end
  end
  %x{echo yes}.chomp
else
  %x{echo no}.chomp
end
  end
end

This fact does evaluate on the client in question:
ldap_rid => 529

However, whatever way I use to try to find it in my template fails...can 
someone please help?
Attempted syntaxes:
<%= @ldap_rid %>
<% @ldap_rid %>
<%= ldap_rid %>
<% ldap_rid %>
<%= scope.lookupvar("ldap_rid") %>
<%= scope.lookupvar("::ldap_rid") %>
...probably others as well. I'm probably just scoping it wrong, but every 
time it comes up as blank or 'undef'.

Thanks.

-- 
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/-/INd3uN7go6sJ.
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.

Re: [Puppet Users] Problem to start puppet

[Craig White]

try commenting out the line genconfig in puppet.conf

Craig

On Jul 14, 2011, at 5:05 PM, Anton wrote:

> Hello
> Im following this guide
> http://aaronwalrath.wordpress.com/2010/09/03/installing-and-configuring-puppet-on-centos-linux/
> (running centos 5.6). But when i try  puppetmasterd --verbose --no-
> daemonize on the supposed server machine it only prints (like cat) /
> etc/puppet/puppet.conf. in the terminal and nothing more.
> 

-- 
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.

Re: [Puppet Users] new variable scoping in templates

[Greg Etling]

Justin,

What would the syntax be along those lines when looking up custom facts?

-- 
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/-/BB3TAoW6PVEJ.
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.

Re: [Puppet Users] new variable scoping in templates

[Justin Lambert]

I've been using:

scope.lookupvar('puppet::params::certdnsnames')

On Thu, Jul 14, 2011 at 8:45 PM, lurdan  wrote:

> hi,
>
> What's the best way to refer variables which pass as defined resource
> parameter
> from template erbs?
>
> I've been made many modules which has resource definitions containing
> file templating.
> After I upgrade my puppet version to 2.7.0rc (debian experimental),
> I'm getting many
> warnings "Dynamic lookup is deprecated.  Support will be removed in
> Puppet 2.8.".
>
> I can surpress this warnings with rewriting from:
> <%= some_arg %>
> to:
> <%= scope.to_hash.fetch('some_arg') %>, but this should be bad way
> because
> it seems ugly and meaningless.
> (It's not an explicit scope declaration, simply variable-syntax
> longed...)
>
> regards,
> --
> KURASHIKI Satoru
>
> --
> 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.
>
>

-- 
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.

[Puppet Users] Re: Run this only once!!

[vella1tj]

the errors are:

err: //Package[Bindscript20100601.dmg]/ensure: change from absent to
present failed: Execution of '/usr/bin/hdiutil mount -plist -nobrowse -
readonly -noidme -mountrandom /tmp /Users/vella1tj/Desktop/
Bindscript2010601.dmg' returned 1: hdiutil: mount failed - Resource
temporarily unavailable

notice: //Exec[blahblah]: Dependency package[Bindscript20100601.dmg]
has 1 failures
warning: //Exec[blahblah]: Skipping because of failed dependencies

On Jul 15, 10:23 am, vella1tj  wrote:
> After I ran that manifest, with this only
>
> #Package to install
> package { 'Bindscript20100601.dmg':
>    provider    => pkgdmg,
>    ensure      => installed,
>    source      => '/etc/puppet/bindscript/files/
> Bindscript20100601.dmg',
>
> I am now receiving these errors and on the second error,
> Bindscript.dmg disappears as if it's deleting itself. I've created the
> dmg in disk utility in Mac osx.
>
> On Jul 12, 4:19 pm, vella1tj  wrote:
>
>
>
>
>
>
>
> > Hi, I am trying run a package once and when it completes I want my
> > manifest to create a touch file and from that file being placed there
> > it will not run again. I have this so far, but have been running into
> > syntax problems/invalid parameters.
>
> > #Package to install
> >  package { 'Bindscript20100601.dmg':
> >    provider    => pkgdmg,
> >    ensure      => installed,
> >    source      => 'temp/location/rightnow/Bindscript20100601.dmg',
> >    notify      => [Exec['blahblah']],
> >    onlyif      => "test -e /var/db/.bindscript",}
>
> >   exec {'blahblah':
> >    command     =>'touch /var/db/.bindscript',
> >    path        =>['/usr/bin']
>
> > }
>
> > If you need more information please ask.

-- 
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.

[Puppet Users] Re: Run this only once!!

[vella1tj]

After I ran that manifest, with this only

#Package to install
package { 'Bindscript20100601.dmg':
   provider=> pkgdmg,
   ensure  => installed,
   source  => '/etc/puppet/bindscript/files/
Bindscript20100601.dmg',


I am now receiving these errors and on the second error,
Bindscript.dmg disappears as if it's deleting itself. I've created the
dmg in disk utility in Mac osx.


On Jul 12, 4:19 pm, vella1tj  wrote:
> Hi, I am trying run a package once and when it completes I want my
> manifest to create a touch file and from that file being placed there
> it will not run again. I have this so far, but have been running into
> syntax problems/invalid parameters.
>
> #Package to install
>  package { 'Bindscript20100601.dmg':
>    provider    => pkgdmg,
>    ensure      => installed,
>    source      => 'temp/location/rightnow/Bindscript20100601.dmg',
>    notify      => [Exec['blahblah']],
>    onlyif      => "test -e /var/db/.bindscript",}
>
>   exec {'blahblah':
>    command     =>'touch /var/db/.bindscript',
>    path        =>['/usr/bin']
>
> }
>
> If you need more information please ask.

-- 
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.

Re: buglet (with rpms from tmz) Re: [Puppet Users] Re: [Puppet-dev] ANNOUNCE: Puppet 2.6.9rc1 is available

[Chris May]

Did anyone ever post a bug, or find a solution for this? I've just upgraded 
some of our Solaris boxes (using OpenCSW) to 2.6.9 and I'm seeing the same 
behaviour. 

-- 
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/-/SDvh1RzW8pgJ.
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.

Re: [Puppet Users] Re: puppet custom fuction run as user pupprt?

[R.I.Pienaar]

- Original Message -
> 
> 
> On Jul 14, 11:57 am, PBWebGuy  wrote:
> > You bring up a good point and I wanted to ask this question
> > anyways.
> > To the best of my knowledge, functions run on the master and facts
> > run
> > on the node.  If that is the case, it perplexes me that functions
> > get
> > sync'd to the node in the /var/lib/puppet/lib... directory.  That
> > is
> > unless functions can then be used in a fact which is something that
> > I
> > have yet to test.  Do you have any clarification?
> 
> 
> If you want an authoritative answer, then the question might be
> better
> posed on the dev list.
> 
> I speculate, however, that functions in modules are synced to nodes
> as a harmless side effect of the overall plugin sync mechanism.  Since
> they *are* synced to nodes, it should be possible to use them (their
> Ruby implementations, that is) in custom facts.  But again, the kinds
> of things you want a Puppet function for tend to be quite different
> from the kinds of things you want a fact for, so the likelihood that
> such a capability would be useful seems small.

they are also usable in running manifests using puppet apply on nodes.

-- 
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.

[Puppet Users] Re: puppet custom fuction run as user pupprt?

[jcbollinger]

On Jul 14, 11:57 am, PBWebGuy  wrote:
> You bring up a good point and I wanted to ask this question anyways.
> To the best of my knowledge, functions run on the master and facts run
> on the node.  If that is the case, it perplexes me that functions get
> sync'd to the node in the /var/lib/puppet/lib... directory.  That is
> unless functions can then be used in a fact which is something that I
> have yet to test.  Do you have any clarification?


If you want an authoritative answer, then the question might be better
posed on the dev list.

I speculate, however, that functions in modules are synced to nodes as
a harmless side effect of the overall plugin sync mechanism.  Since
they *are* synced to nodes, it should be possible to use them (their
Ruby implementations, that is) in custom facts.  But again, the kinds
of things you want a Puppet function for tend to be quite different
from the kinds of things you want a fact for, so the likelihood that
such a capability would be useful seems small.


John

-- 
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.

[Puppet Users] Re: What is the best practice to clean up installed components on a node?

[jcbollinger]

On Jul 14, 6:48 pm, Darrell Fuhriman  wrote:

[...]

> So your scenario wouldn't affect me anyway. But I'm anal-rententive that way. 
> I can't imagine why you *wouldn't* do that if you're going to be running on 
> more than one platform.


It's fine to *wish* for a feature that would make your life easier,
but it is unreasonable to expect such a feature to be implemented when
it carries with it serious technical and practical problems for people
who build their manifests differently than you do.  Puppet needs to do
a good job handling everything its DSL can express, explicitly or
implicitly, which is one reason why its semantics do not include
implicitly adding classes to catalogs, and probably never will.


> I actually wish puppet had a 'confine' parameter for classes like it does for 
> custom facts. It would make it easier to avoid shooting yourself in the foot.
>
>   class foo {
>     confine $kernel => ['Linux', 'Darwin']
>   }


I wouldn't have a problem with that, but you can accomplish the same
thing now with a conditional around the whole class body.


> Anyway, it's a problem, yes, but not an insurmountable one.


It depends on what you mean by 'insurmountable'.  If the DSL suffered
from that problem then yes, users could avoid it by taking care to use
certain coding techniques, but that just treats the symptom.  The
underlying problem is that the DSL would contain additional traps for
unwary and inexperienced users, and it would be capable of expressing
undecidable declarations.  Moreover, adding the feature at this point
would require everybody to audit all their manifests for compatibility
with this behavior change.  People are fallible, so some breakage
*would* occur.


> > Consider also what happens when X, Y, X::disabled, and Y::disabled all
> > exist, and Y::disabled includes X. Suppose that after Puppet's initial
> > pass to choose which classes to include, it sees that neither X nor Y
> > is included, so it adds X::disabled and Y::disabled.  But Y::disabled
> > includes X, so X::disabled shouldn't be included after all!  Or should
> > it?
>
> Well, in that situation the right answer would be that only X is included.


Perhaps, but but what if also X::disbled includes Y?  Then it is
completely undeterminable which classes to include.  Real-life
manifests are unlikely to have such a tight mutually-contradictory
loop, but they might easily have one involving a longer chain.


> How much work that is to implement in the current puppet parser, I have no 
> idea. But that's irrelevant to the question at hand.
>
> Plus, why the hell would anyone want to do that?


Why do you suppose they wouldn't?  It's entirely likely that
foo::disabled classes would often want to include other classes.  For
instance, if foo::disabled ensures Service['foo'] stopped, then it
must also ensure that Package['foo-service'] is installed, which is
accomplished by some other class in a sufficiently DRY manifest set.
Or if it ensures a different state of some configuration file than
does class foo, then it may need to manage the directory in which that
file lives, which again is likely to be in some other class.  Since it
is likely that foo::disabled classes will include other classes, it is
unreasonable to assume that cycles would never occur.


> If you put includes into your !X classes, you've clearly failed to understand 
> the concept and should be taken far away from any keyboards and put into a 
> systems administration re-education camp. I'd go so far as to say that any !X 
> class could not include another class at all. (And obviously !X classes could 
> not be included explicitly anywhere, since that's also fundamentally missing 
> the point.)


I don't think you've thought this all the way through.


> >>  Maybe we have different approaches to how we manage resources, but I 
> >> genuinely can't think of an example of where you would want some hosts to 
> >> be X, some to be !X, and some to be unknown, which is kind of what I think 
> >> you're saying here, because I can't think of anyway that "unmanaged" 
> >> doesn't mean "unknown".
>
> > [...] Dev and test boxes present a wide
> > variety of examples where looser management of some resources may be
> > desired than for production boxes.
>
> *shudder*  Down that path lies madness, if you ask me.  To my mind, either 
> something's managed or it isn't – there is no alternative that doesn't end in 
> tears. But again, these things are easily solved by saying something like:
>
> class !foo {
>   case $environment {
>     default: { #do nothing }
>    production: { # do stuff }
>   }
>
> }
>
> Because then at least you're forced to be explicit about what your management 
> policy is, even if that policy is "we let dev machines do whatever they want 
> to service foo".


Your overall theme seems to be "there are ways to write manifests so
that the problems inherent in the proposed feature won't bite you."  I
generally agree, but I don't find that sufficient 

Re: [Puppet Users] LDAP ENC

[Rob McBroom]

On Jul 14, 2011, at 4:01 PM, Craig White wrote:

> same user/password as I have configured in puppet.conf
> 
> It does happen to work if I comment out the username & password
> 
> It doesn't work even if I use rootbinddn and rootbinddn password

Well, then it’s probably a bug in Puppet or (more likely) Ruby. At thins point, 
I’d probably start looking at or writing some Ruby stuff to test it outside of 
Puppet. Maybe someone else has a better idea.

-- 
Rob McBroom


-- 
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.

Re: [Puppet Users] Definition parameter defaulting to the definition's own $title?

[Matthias Saou]

R.I.Pienaar wrote :

> > Maybe I'm going nuts, but I could have sworn reading about a trick or
> > new feature which allowed to have a definition parameter get a
> > default value of the definition's own $title (instead of having the hack
> > around the limitation with selectors and intermediate variables later on).
> 
> try $name, that should do it, came in somewhere mid 2.6.x series

Yup, that was it!

Section "$name can now be used to set default values in defined
resource types" in the release notes :
https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes

And this is the original feature request :
https://projects.puppetlabs.com/issues/5061

Thanks for the quick pointer :-)

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 14 (Laughlin) - Linux kernel 2.6.35.13-91.fc14.x86_64
Load : 0.33 0.39 0.55

-- 
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.

Re: [Puppet Users] Definition parameter defaulting to the definition's own $title?

[R.I.Pienaar]

- Original Message -
> Hi,
> 
> Maybe I'm going nuts, but I could have sworn reading about a trick or
> new feature which allowed to have a definition parameter get a
> default value of the definition's own $title (instead of having the hack
> around the limitation with selectors and intermediate variables later on).

try $name, that should do it, came in somewhere mid 2.6.x series

-- 
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.

[Puppet Users] Definition parameter defaulting to the definition's own $title?

[Matthias Saou]

Hi,

Maybe I'm going nuts, but I could have sworn reading about a trick or
new feature which allowed to have a definition parameter get a default
value of the definition's own $title (instead of having the hack around
the limitation with selectors and intermediate variables later on).

Basically what I want to have working is this :

-8<-

define foo (
$bar = $namevar
) {
file { '/tmp/foo': content => $title }
file { '/tmp/bar': content => $bar }
}

# Here I want both to contain "foo"
foo { 'foo': }
# Here I want bar to contain "bar"
foo { 'foo': bar => 'bar' }

-8<-

Anything I can use instead of "$bar = $namevar" to get it working?

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 14 (Laughlin) - Linux kernel 2.6.35.13-91.fc14.x86_64
Load : 0.36 0.40 0.85

-- 
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.

Re: [Puppet Users] Re: Seemingly random failures after 2.7.1 upgrade

[Peter Meier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

> same problem for me.. I've notice the problem on modules using
> autoloading...
> 
> I think I will stick to version 2.6.9...

can you at least file a detailed bug report? Thanks! Otherwise the
situation can't be really improved...

~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4gHX4ACgkQbwltcAfKi3/GXQCgpZMNyTEiV1USVG1qpxgCh3mE
+S8AoJnCLIYreiOg3bXr1zf4u56eZivk
=NF0L
-END PGP SIGNATURE-

-- 
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.