similar to: Puppet doc questions/problems

When I run "puppet resource user <ldadpuser>" I get a resource definition back for that user. However, when I run "puppet resource user" I do NOT see <ldapuser> in the list. Is this intended behavior? Is there a way to get a list of all users, whether they are ldap or local? This node is running puppet 2.7.19 on Ubuntu 12.04 against a 2.7.19 master on Ubuntu

I am using puppet 2.7.14 on Ubuntu 10.04 LTS. I have the following gems: *** LOCAL GEMS *** diff-lcs (1.1.3) hiera (0.3.0) hiera-puppet (0.3.0) metaclass (0.0.1) mocha (0.12.1) puppet-lint (0.1.13) puppetlabs_spec_helper (0.2.0) rake (0.9.2.2) rspec (2.11.0) rspec-core (2.11.1) rspec-expectations (2.11.2) rspec-mocks (2.11.1) rspec-puppet (0.1.3) When I run "rake help" I get the

Does puppet doc require a specific version of any gems (such as rdoc or rake) to operate? I''m getting some errors when I try to generate my rdoc now. # puppet doc --output /var/www/test --modulepath /etc/puppet/environments/test/modules -m rdoc RDoc::RDocError is deprecated and will be removed in RDoc 4 Could not generate documentation: uninitialized constant RDoc::RDoc::Generator

Puppet 2.7.17 is a maintenance release for Puppet in the 2.7.x series. It contains a fix for the ubuntu service regression in 2.7.16 (#15027, #15028, #15029). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-2.7.17.tar.gz Windows package is available at https://downloads.puppetlabs.com/windows/puppet-2.7.17.msi RPMs are available at

I recently started trying to use rspec-puppet and puppetlabs-rspec-helper. When I ran ''rspec-puppet-init'' in one o fmy modules, it created a series of symlinks. Now, when I run puppet doc (via a rake task supplied by The Foreman, but also when I call it directly) I get the following error: Could not generate documentation: Definition ''mongodb::addmongouser''

Team, I am trying to setup new Puppet master server on Centos 5.4. I am getting the below error which running yum install puppet-server puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems --> Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems --> Missing

I''m using Dashboard 1.2.10 on an Ubuntu 10.04 LTS system, and Puppet 2.7.19 When I do an inventory search, I get a blank screen. In the logs, I found the following: Processing NodesController#search (for X.X.X.X at 2012-10-05 08:44:57) [GET] Parameters: {"action"=>"search", "controller"=>"nodes",

I''ve got a single puppet master (2.7.19 + facter 1.6.11) controlling a number of nodes (2.7.17 + facter 1.6.8-10). On all of thse, fact absed variables work as expected (such as $::operatingsystem and $::fqdn). However, on my puppet master, when I run ''puppet agent --test'' all fact based variables are combing back as empty strings. For example. I have a line in a

Here''s one I learned: I originally had # Ensure /etc/hosts contains the basics host { "${fqdn}": host_aliases => $hostname, ip => $ipaddress, } And thru some trial and error, got down to this (which puppet-lint does not gripe about) # Ensure /etc/hosts contains the basics host { $fqdn: host_aliases => $hostname, ip => $ipaddress, }

Hi, I have been working on a new puppet code formatter for Geppetto for some time, and it is now starting to work quite well. The plan is to release it in Geppetto 3.0. If you want to, you can help by sending "formatting puzzles" - i.e. "given input x, produce formatted result y". I am esp. looking for code where it is impossible to follow "the style guide" -

Hi! I''m a newbie in Puppet with some Chef experience. Now trying to convert my pet project from Chef to Puppet. When I start a Tomcat is takes some time (several seconds). I need to wait a line "Server startup in" in Tomcat''s log before proceeding. Here is a way which I used in Chef:

I''m running puppet in a local VM to do some testing, and all of our systems are behind a proxy. I''ve got the http_proxy environment variable set properly, but when I try to use puppet module install <foo> it doesn''t seem to honor it and can''t connect. I used wget to download it, but even when I use modulepath it still tries to connect to the forge and

Puppet 2.6.14 is a security release in the 2.6.x branch which addresses CVEs 2012-1053 and 2012-1054. All users of Puppet 2.6.x are encouraged to upgrade when possible to Puppet 2.6.14. Other information available at: http://puppetlabs.com/security or visit http://puppetlabs.com/security/cve/cve-2012-1053 and http://puppetlabs.com/security/cve/cve-2012-1053 Detailed feature release notes are

Hi, I''m using Puppet 3.2.1 and heavily relying on hiera data bindings. I have the following situation: class software ( $my_content = undef, ) { file { ''/path/to/file'': content => $software::my_content, } } in hieradata/software.yaml (hiera.yaml seems ok): software::my_content: template(''mymodule/myfile.erb'') With this configuration I

I''m using puppet 0.25.5 and just discovered two file resource bugs. I suspect the bugs did not exist in 0.24 because the code were using that triggers them has been the same for a long time and while it is possible we did not notice the problem earlier, it seems unlikely as it has been triggering failures in our automated system tests since around the time we upgraded. Anyway,

Hi all, I''m having some problems working with puppet-selinux[1] I''ve successfully deployed the module in nodes.pp and got it to set various SELinux modes, by using class { selinux: mode => ''permissive'' } or class { selinux: mode => ''enforcing'' } Now I want to load a custom SELinux policy file. According to the docs, the correct

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

Hi. I''m getting lots of warning like this one from puppet-lint: WARNING: line 67 has more than 80 characters Now, I don''t like warnings, so any idea how should I rewrite this line for example, to void the warning? package {''rpmforge-release'': ensure => ''0.5.2-2.el6.rf'', provider => ''rpm'', source =>

I was in the process of setting up puppet environments. I pulled code from my main modules and manifests directories into the prod environment folder, deployed a newer branch of that code to a ''stg'' environment folder, updated puppet.conf on the master, and reconfigured puppet.conf on my agents to use the new environments. All looked fine until I checked puppet dashboard a

*Hello folks** **I have trying to install puppet dashboard on our ubuntu 10.04 setup but am currently stuck on the following problem.**after the installation and the db sync the application refuses import any reports. In the background job notifier i find error messages like this one below.** **Does anyone know how to proceed from here?** **bram** * *Importing report report-1540-1.yaml* at