Terra | 1 Apr 02:18 2010
Picon

[Puppet Users] Re: How to manipulate contents of directory without affecting parent directory

Hello Brian,

On Mar 31, 3:24 pm, Brian Wingenroth <wingenr... <at> jhu.edu> wrote:
> On 3/31/10 5:37 PM, Terra wrote:
>
>
>
> > Greetings,
>
> > I'm having a bit of a problem where file{} doesn't support globbing...
>
> > Say I have the following directory tree:
> > /foo  (mode: 0751)
> > /foo/bar1
> > /foo/baz1
> > /foo/random1
> > ...
> > /foo/randomN
>
> > All subdirectories under '/foo' can be arbitrary names...
>
> > How I would like to be able to express this, which won't work...
> > file { "/foo/*":  mode =>  700; }
>
> > What comes close is:
> > file { "/foo": mode =>  700, recurse =>  "true", recurselimit =>  1; }
>
> > The problem with that, is '/foo' is also set to mode 700, when it
> > should remain mode 751...
>
(Continue reading)

Michael DeHaan | 1 Apr 03:09 2010

Re: [Puppet Users] Could not find dependency



On Wed, Mar 31, 2010 at 6:30 PM, Darvin Denmian <darvin.denmian <at> gmail.com> wrote:
Hello,

I have the following define:

define adduser ($shell, $group, $fullname, $ingroups = "none", $home = "none") {
  user { "$name":
     ensure => present,
     comment => "$fullname",
     gid => "$group",
     groups => "$ingroups",
     membership => minimum,
     shell => "$shell",
     home => "$home",
     require => Group[$group]
  }
}

and the following "call" for this define:

adduser {
  "teste" :
  shell => "/bin/bash", group => "teste",fullname => "teste
Workgroup",ingroups => "admin"
}

and ..... the following error:

err: Could not run Puppet configuration client: Could not find
dependency Group[teste] for User[teste] at
/etc/puppet/modules/sysadmin/manifests/init.pp:13

Can somebody help me with this error?

Thanks !


Dependencies for groups are implicit when they are listed with a user, so what you have for $ingroups (I could be wrong here), should cover you and you won't need the require.

However, where's the group, right?

You will not be able to reference an explicit dependency unless somewhere in your configuration you are declaring the Group.   In the above example, you don't have the Group declared, so most likely it is not present, hence the problem.

I may be lacking some additional context, but from what you've shared, that looks like the problem to me.

--Michael

=

--
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael DeHaan | 1 Apr 03:13 2010

Re: [Puppet Users] Re: How to manipulate contents of directory without affecting parent directory


I was hoping that there was a way for Puppet to remember the
subdirectories and only chmod on new subdirectories that are not mode
700...

or if that is too complicated to support internally, then something
simple like:
If file{} had globbing ability, then
[pseudo]  file { "/foo/*": ... }
for item in /foo/*
 if item is not a directory: then continue
 if item mode != 700: then chmod 700 item


Thus the server doesn't know what files the client has, so it can't presently do that -- it couldn't build the resource graph.

Exec in your usage may feel like the thermonuclear option, but you're using it in a fairly limited way... be sure it's executed with a require in the right
place in the dependency chain and it's not too unreasonable IMHO, as it's not a resource intensive command. 

It's there to fill in the gaps for things that are hard to model. 


 

--
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Smain Kahlouch | 1 Apr 07:42 2010
Picon

Re: [Puppet Users] Mongrel : Can't download files

-------- Message initial --------
De: Michael DeHaan <michael <at> puppetlabs.com>
Reply-to: puppet-users <at> googlegroups.com
À: puppet-users <at> googlegroups.com
Cc: James Turnbull <james <at> lovedthanlost.net>
Sujet: Re: [Puppet Users] Mongrel : Can't download files
Date: Wed, 31 Mar 2010 10:17:24 -0400

On Wed, Mar 31, 2010 at 6:05 AM, smain kahlouch <smainklh <at> gmail.com>
wrote:
        Hi,

        i'm following the steps of the documentation but the links are
        not working.
        I can't download the files :

        http://projects.reductivelabs.com/projects/puppet/wiki/Using_Mongrel_On_Debian

        Thanks for your help,
        Grifith

This looks like this might have happened as part of the redmine
conversion, as the attachment still references a URL in Trac.
It could also be a problem with the rewrite rules having changed since
the site migration.

(James, do you know anything about attachment migration?)

I've seen some other docs that had attachments migrated, though I'm not
sure why this one is an outlier.

--Michael

        -- 
        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 <at> googlegroups.com.
        To unsubscribe from this group, send email to puppet-users
        +unsubscribe <at> 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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users
+unsubscribe <at> googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi Michael,

Is there another way to get these files?

Thanks,
Grifith

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

James Turnbull | 1 Apr 08:22 2010
Picon

[Puppet Users] ANNOUNCE: Puppet 0.25.5 - Release Candidate 1 available!

Welcome back to the Puppet release cycle - brought to you by the newly 
minted Puppet Labs.

The 0.25.5 release is a maintenance release in the
0.25.x branch. It contains a number of bug fixes but also some 
performance enhancements including speed-ups to Puppet's graphing.

The release candidate is available at:

http://puppetlabs.com/downloads/puppet/puppet-0.25.5rc1.tar.gz

Please note that all final releases of Puppet are signed with the
Reductive Labs key (we'll issue a new, improved Puppet Labs key after 
the Rowlf release).

See the Verifying Puppet Download section at 
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please test this release candidate and report feedback via the
Puppet Labs Redmine site:

http://projects.puppetlabs.com

Please select an affected version of 0.25.5rc1.

RELEASE NOTES

The default location for Puppet's dynamic files, the $vardir option, has 
changed from /var/puppet to /var/lib/puppet. This is already the default 
for the Fedora EPEL and Debian/Ubuntu packages and brings Puppet into 
FHS compliance.

You can now specify checksum => none in the file type to disable file 
check-summing.

CHANGELOG

57ae381  Modify SuSE spec file for 0.25.x and correct shebang lines for 
puppetd/puppetmasterd
d90ec79  Fixes #3460 - Makes Puppet FHS compliant by moving /var/puppet 
to /var/lib/puppet
ae0b0bf  Fix for #3101 (bug in MRI 1.8.7)
9db066b  Fixes #3419. OS X 10.6 Ruby doesn't set supplementary groups
306d082  Revert the guts of #2890
4eea77a  Fail gracefully on packages that don't have the HOMEPAGE 
variable set (e.g. dev-lang/php).
f5b8494  Fixed #3443 - Typo in mount type
b0ef2c6  Fixes #3135 - darwin doesn't support 'mount -o remount'
7018cf5  Adding :catalog_terminus setting
978ab8a  fixing obsolete comment in puppetd
6d13d0d  Adding support for only using cached catalogs
bc28715  Refactoring Configurer to enable the next feature
ba43d7b  Fix for #3366 - --tags '' treated as boolean 'true'
5ab5e8a  Supressing warnings (not really failures) in test/unit
e4df0b0  Fix test using wrong Puppet util filesetting group
eeb3d74  Mock user in SUIDManager tests
9ea27db  Removing resources generate tests
218e3e9  Removing old test for service/debian provider
1556938  Replace test/unit file write test with spec
2defc00  Fix for #3424 and tests to prove it.
44798b9  Fixed changelog Rake task
5d10f65  Fix #3155 - prevent error when using two matching regex in cascade
fbedb99  Fixing #3148 Settings#without_noop when run with no noop setting
389c77b  Another trivial follow-up fix for #2604: invalid path to zaml.rb
56b5753  Fix inefficient SimpleGraph#matching_edge
4b2b9eb  Fix #3229 - use original value in case/selector regex matching
19863c0  Fix #2929 - Allow checksum to be "none"
fd76142  Fixed puppetlast typo
3b4e782  Follow up for #2604, debug msg left behind.
e44430b  Fix for #2604 Pure Ruby yaml generation
74cd55f  Fixes #3113 - When importing a manifest puppet needs to chill
7ec50a7  Fixes #3387 - Handle path elements with ticks and spaces
d561a98  Fix for #3412 install.rb should not put "." first in the tmp_dirs
751df45  Fix #3186 - require function set relationship only on the last 
class
a1d216c  Fixed the return types were valid, and removed the copy paste 
error with the exception logic
d532e6d  Fixing #3185 Rakefile is loading puppet.rb twice
5aa596c  Fix #3150 - require function doesn't like ::class syntax
3457b87  Added time module to tagmail report
71653a7  Fixed #3162 - tidy does not remove empty files when "size => 0" 
is set
efd0f76  Fixed #3128 - Updated man pages and moved puppet.conf.8 to 
puppet.conf.5
ad4f94a  Add version number to puppetlast display.
0533cea  Forgot fakedata called in spec
6416f91  Fixing #2669 puppetmasterd integration has leaky state
8a3a205  Fix for #2327, check the return types from augeas and fail 
where appropriate
2ae7516  2047: Add a not_include into match
55f6239  Minor unit test fixes
b7b7a1c  vim: Improve function matching when functions contain ')'
b3c363c  vim: puppetDefArguments is contained by puppetDefine
f9e05a8  Fix for #3094 (libdir should take ":" delimited path)
b473264  Fix #1842 Net::HTTP#enable_post_connection_check doesn't work 
anymore
9419c2b  Fix for #3035 (redhat services use init for source)
10becce  Fix for #3077 (unit tests broken in 0.25.1-->0.25.4)
49a7185  Fix for #3085 (user_role_add pulls from same source as useradd)
1f086c2  Fix for #3114 (ruby's arbitrary limit on process groups too low)

Regards

James Turnbull

-- 
Author of:
* Pro Linux System Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Daniel Pittman | 1 Apr 09:38 2010
Picon

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Charles Johnson <gm.johns276 <at> gmail.com> writes:
> On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman <daniel <at> rimspace.net> wrote:
>
>> [...]
>> 
>> Your client logs *still* show that there is no MOTD stuff being touched at
>> all; try this on the client that should manage MOTD and see what is output:
>> 
>>    puppetd --test --debug 2>&1 | grep -i motd
>> 
>> I suspect the answer will be "nothing is output".
>> 
>> If you post those results, and the content of your MOTD class (or a pointer
>> to your entire set of manifests) we should be better able to help narrow
>> this down...
>> 
>
> I do appreciate your help.
>  
> OK, right, nothing is output on the client from puppetd --test --debug 2>&1 | grep -i
> motd
>
> /etc/puppet/manifests/site.pp contains this at the top line:  import "modules"
> /etc/puppet/manifests/modules.pp contains this line at the top: import "motd"
> /etc/puppet/modules/motd/manifests/init.pp looks like this

Darn.  I don't know. :(  It all looks right to me.  At this point I would be
reduced to guessing, or tracing through the code.  Sorry.

        Daniel

-- 
✣ Daniel Pittman            ✉ daniel <at> rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

smain kahlouch | 1 Apr 09:50 2010
Picon

Re: [Puppet Users] Mongrel : Can't download files



2010/4/1 Smain Kahlouch <smainklh <at> gmail.com>
-------- Message initial --------
De: Michael DeHaan <michael <at> puppetlabs.com>
Reply-to: puppet-users <at> googlegroups.com
À: puppet-users <at> googlegroups.com
Cc: James Turnbull <james <at> lovedthanlost.net>
Sujet: Re: [Puppet Users] Mongrel : Can't download files
Date: Wed, 31 Mar 2010 10:17:24 -0400



On Wed, Mar 31, 2010 at 6:05 AM, smain kahlouch <smainklh <at> gmail.com>
wrote:
       Hi,

       i'm following the steps of the documentation but the links are
       not working.
       I can't download the files :

       http://projects.reductivelabs.com/projects/puppet/wiki/Using_Mongrel_On_Debian

       Thanks for your help,
       Grifith


This looks like this might have happened as part of the redmine
conversion, as the attachment still references a URL in Trac.
It could also be a problem with the rewrite rules having changed since
the site migration.

(James, do you know anything about attachment migration?)

I've seen some other docs that had attachments migrated, though I'm not
sure why this one is an outlier.

--Michael




       --
       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 <at> googlegroups.com.
       To unsubscribe from this group, send email to puppet-users
       +unsubscribe <at> 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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users
+unsubscribe <at> googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi Michael,

Is there another way to get these files?

Thanks,
Grifith

It seems that many files disapeared. I was looking the puppet dashboard features and i noticed the same problem for the pictures.

http://www.puppetlabs.com/2009/12/14/a-tour-of-puppet-dashboard-0-1-0/

Regards,
Grifith

--
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
John Lyman | 1 Apr 14:16 2010
Picon

[Puppet Users] Re: How to manipulate contents of directory without affecting parent directory

> file { "/foo/*":  mode => 700; }
>
> What comes close is:
> file { "/foo": mode => 700, recurse => "true", recurselimit => 1; }

I'm not sure if this will work (I've never tried to ignore the top
level directory), but you can try:

file { "/foo": mode => 700, recurse => "true", recurselimit => 1,
ignore => "/foo"; }

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson | 1 Apr 16:27 2010
Picon

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Daniel, I resolved the issue. One of my classes had duplicate 'ensure => ' lines. This was OK with 0.24.8, but 0.25.4 silently fails. I posted a RESOLVED about my discovery.


I appreciate your help.

Cheers--

Charles

On Thu, Apr 1, 2010 at 2:38 AM, Daniel Pittman <daniel <at> rimspace.net> wrote:
Charles Johnson <gm.johns276 <at> gmail.com> writes:
> On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman <daniel <at> rimspace.net> wrote:
>
>> [...]
>>
>> Your client logs *still* show that there is no MOTD stuff being touched at
>> all; try this on the client that should manage MOTD and see what is output:
>>
>>    puppetd --test --debug 2>&1 | grep -i motd
>>
>> I suspect the answer will be "nothing is output".
>>
>> If you post those results, and the content of your MOTD class (or a pointer
>> to your entire set of manifests) we should be better able to help narrow
>> this down...
>>
>
> I do appreciate your help.
>  
> OK, right, nothing is output on the client from puppetd --test --debug 2>&1 | grep -i
> motd
>
> /etc/puppet/manifests/site.pp contains this at the top line:  import "modules"
> /etc/puppet/manifests/modules.pp contains this line at the top: import "motd"
> /etc/puppet/modules/motd/manifests/init.pp looks like this

Darn.  I don't know. :(  It all looks right to me.  At this point I would be
reduced to guessing, or tracing through the code.  Sorry.

       Daniel

--
✣ Daniel Pittman            ✉ daniel <at> rimspace.net            ☎ +61 401 155 707
              ♽ made with 100 percent post-consumer electrons

--
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> 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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Serge Dewailly | 1 Apr 11:13 2010
Picon

[Puppet Users] Puppet environment + fileserver

Hi All,

I'm trying to use different environment for my servers management. I'am 
able to use different classes, modules... for each environment but I 
can't find how to specify fileserver configuration for each environement.

Here is a piece of my configuration :

puppet.conf
[main]
         logdir=/var/log/puppet
         vardir=/var/lib/puppet
         ssldir=/var/lib/puppet/ssl
         rundir=/var/run/puppet
         factpath=$vardir/lib/facter
         pluginsync=true
         autosign=true
         certname = pup05401.grpldc.com
         environments = production,testing
         environment=production

[production]
        manifest=/etc/puppet/production/manifests/site.pp
        manifestdir=/etc/puppet/production/manifests
        modulepath=/etc/puppet/production/modules
        templatedir=/etc/puppet/production/templates
        fileserverconfig=/etc/puppet/production/fileserver.conf

[testing]
         manifest=/etc/puppet/testing/manifests/site.pp
         manifestdir=/etc/puppet/testing/manifests
         modulepath=/etc/puppet/testing/modules
         templatedir=/etc/puppet/testing/templates
         fileserverconfig=/etc/puppet/testing/fileserver.conf

testing/fileserver.conf
[files]
   path /etc/puppet/testing/files
   allow *.mydomain.com

When using this configuration, I get unauthorized access to files. 
Reason is puppetmaster can't find file server configuration :

debug: No file server configuration file; autocreating modules mount 
with default permissions

Is it possible to manage a fileserverconfig for each environment ?

Thanks for your help.
Serge

--

-- 
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.


Gmane