Here is the deal, we are trying to launch the puppet agent --test from the preseed file using this line:

On Tuesday, July 31, 2012 2:05:28 PM UTC-7, ZJE wrote:

Is it possible to access <at> resource variables inside a type?

I would like to make some decisions on parameters based on other parameters that may have already been set.

For example,
---
  newparam(:param1) do
    Puppet.debug "Found drivesperarray parameter"
    desc "parameter 1"
    validate do |value|
      if resource[:otherparam] then
        #dosomething
      else
        resource[:param1] = 0
      end
    end
    Puppet.debug "Parameter 1 is: #{ <at> resource[:param1]}"
  end
---

But I keep getting messages like "undefined method `[]' for nil:NilClass"

Anyone have experience with this? I've tried searching around for example without much luck...

Thanks!

Hello,

thanks for the reply, I actually made an error in my declaration. I used two variables which I had just moved out of scope, and so I declared two empty File[] objects - and puppet complained.

When your solution didn't work either it hit me :) .

thanks & greetings!
Axel.



Am Dienstag, 31. Juli 2012 16:10:23 UTC+2 schrieb David Schmitt:

Hi Axel,


   $filesA = ["/tmp/A1", "/tmp/A2", "/tmp/A3" ]
   $filesB = ["/tmp/B1", "/tmp/B2", "/tmp/B3" ]

   file {
     $filesA:
       ensure => present,
       mode => 0644, owner => root;
     $filesB:
       ensure => present,
       mode => 0755, owner => "www-data";
   }

If you're looking for something different you might want to look into
setting recurse=>true. Read the Type Reference for more info.

Best Regards, David

Hello Christopher,

that's a nice explanation. I thought only the contents _under_ .../nfs-mounted/ would be server-side, not the mount-point itself. Well you always learn more. no_root_squash is not an option, I will have a look as how to manage that properly on our server side.

Mainly I just want to have the directory to have the correct permission when it is not currently mounted.


Thanks & greetings,
Axel.

Am Mittwoch, 1. August 2012 00:24:21 UTC+2 schrieb Christopher Wood:

(inline)

On Tue, Jul 31, 2012 at 05:23:00AM -0700, Axel Bock wrote:
>    Hi group,
>
>    I am managing an NFS mount with puppet. And it does not work, and
>    seriously I really don't see how this can work out nicely. First I make
>    sure with a file {} class that the directory I want to mount exists. Cause
>    it is used by the webserver it should belong to the wwwrun/www group on
>    the system. No prob.

This is changing the directory inode on the nfs client.

>    Then I mount the NFS share on the dir. No prob.

Now the inode that your nfs client sees is on the nfs server. It is not the same inode that you just managed with puppet.

(I say inode, but depending on the nfs server it may not be a unix filesystem behind it.)

>    On the 2nd run of puppet though ... Error! The NFS mount point is
>    "changed" over to root:root with 775 permissions (or 777? I don't
>    remember). Puppet of course now wants to set the user:group of the dir ...
>    and naturally fails.

This is dependent on your nfs server settings. You likely have root_squash set by default (see 'man exportfs'), so any activity as the root user on the nfs client is mapped to a "nobody" or "nfsnobody" (uid 65535 or similar) on the nfs server. Check /etc/exports on the nfs server.

>    So is there a way to keep this error from happening?

You can set no_root_squash on the export and run 'exportfs -a' on the nfs server. Then you might have to remount on the client end.

The broader issue is whether you should manage file permissions on the nfs client or the nfs server. I haven't decided myself, but if you do it on the server you won't have to reduce security by running no_root_squash. The mount will also arrive with the correct permissions.

>    Thanks in advance & greetings,
>    Axel.
>
>    --
>    You received this message because you are subscribed to the Google Groups
>    "Puppet Users" group.
>    To view this discussion on the web visit
>    [1]https://groups.google.com/d/msg/puppet-users/-/tw1oa58dRhoJ.
>    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.
>
> References
>
>    Visible links
>    1. https://groups.google.com/d/msg/puppet-users/-/tw1oa58dRhoJ

Hi,

I am new to puppet and have started evaluating various features in last few days. I am not a developer and am mostly going to use the modules available on github or puppet forge.

Currently I have tried all easier modules and they seem to work perfectly without any issues, but now the problem is arising when I am trying to use modules like mysql, tomcat etc...

For mysql I am using the module https://github.com/puppetlabs/puppetlabs-mysql

What I am observing is mysql is gets installed and everything but no db is added, also intermittently the password is not set, it is neither not blank nor does it set the password that I have mentioned. The nodes.pp that I am using is as follows

[root <at> pmast1 manifests]# cat /etc/puppet/manifests/nodes.pp
class baseclass {
class { 'mysql': }
class { 'mysql::server':
#config_hash => { 'root_password' => 'mypass' }
}
mysql::db { 'mydb':
user     => 'myuser',
password => 'mypass',
host     => 'localhost',
grant    => ['all'],
}
}

node 'pclient1.example.com' {
        include baseclass
}

Now as in nodes.pp if I try to set the password it gives me the error below on the puppet client node

[root <at> pclient1 ~]# puppetd --test
notice: Ignoring --listen on onetime run
info: Caching catalog for pclient1.example.com
info: Applying configuration version '1343801984'
notice: /Stage[main]/Mysql::Config/

Hi,

I am new to puppet and have started evaluating various features in last few days. I am not a developer and am mostly going to use the modules available on github or puppet forge.

Currently I have tried all easier modules and they seem to work perfectly without any issues, but now the problem is arising when I am trying to use modules like mysql, tomcat etc...

For mysql I am using the module https://github.com/puppetlabs/puppetlabs-mysql

What I am observing is mysql is gets installed and everything but no db is added, also intermittently the password is not set, it is neither not blank nor does it set the password that I have mentioned. The nodes.pp that I am using is as follows

[root <at> pmast1 manifests]# cat /etc/puppet/manifests/nodes.pp
class baseclass {
class { 'mysql': }
class { 'mysql::server':
#config_hash => { 'root_password' => 'mypass' }
}
mysql::db { 'mydb':
user     => 'myuser',
password => 'mypass',
host     => 'localhost',
grant    => ['all'],
}
}

node 'pclient1.example.com' {
        include baseclass
}

Now as in nodes.pp if I try to set the password it gives me the error below on the puppet client node

[root <at> pclient1 ~]# puppetd --test
notice: Ignoring --listen on onetime run
info: Caching catalog for pclient1.example.com
info: Applying configuration version '1343801984'
notice: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: mysqladmin: connect to server at 'localhost' failed
notice: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: error: 'Access denied for user 'root' <at> 'localhost' (using password: NO)'
err: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]/returns: change from notrun to 0 failed: mysqladmin -u root  password mypass returned 1 instead of one of [0] at /etc/puppet/modules/mysql/manifests/config.pp:94
notice: /File[/root/.my.cnf]: Dependency Exec[set_mysql_rootpw] has failures: true
warning: /File[/root/.my.cnf]: Skipping because of failed dependencies
notice: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Dependency Exec[set_mysql_rootpw] has failures: true
warning: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Skipping because of failed dependencies
notice: Finished catalog run in 0.56 seconds


And in case I do not specify the password in the nodes.pp, not sure what password is sets but only adds the mysql service to the client node.

I am sure I am missing something and here but not sure what...

Also in case of tomcat I am having similar issues not sure how can I add applications or tomcat in the /usr/local/tomcat path.

Thanks for your help in advance.

Rakesh K.