similar to: selinux symlink patch

Hi Heidi, Now We tried to install the puppet and puppet-server packages from puppetlabs, but we faced below discrepancy. Please look into this and let us know your suggestions because issue was not found in Puppet community as well. There was 1 issue related to this but it dint help us (http://projects.puppetlabs.com/issues/16634 ) We went through

Hi, I wrote a little "hello world" script and I am a little concerned by execution that hangs for long periods of time. *computer:* Windows XP Professional Service Pack 3 Intel(R) Xeon(R) CPU W3550 @ 3.07GHz 3.07GHz, 3.50 GB of RAM *init.pp:* class hello { notice(''Hello world!'') } *command line:* puppet apply --debug -e ''include hello''

I am running puppet 3.2.1, using the puppetlabs repos, on centos 6.4. I keep getting these messages in the log: (every 30 minutes) Jun 3 11:24:55 yoda puppet-master[20292]: Failed to set SELinux context system_u:object_r:puppet_etc_t:s0 on /etc/puppet/auth.conf Jun 3 11:24:55 yoda puppet-master[20292]: Failed to set SELinux context system_u:object_r:puppet_etc_t:s0 on

My install was working for a couple of months until I rebooted my puppet server. The clients do not report an error when I run puppet agent -t. I''ve attempted to remove certificates and renew. The clients get new certificates, but the console still does not update. Even the puppet server itself is not updating as a client. After reboot the only thing I have noticed that changed

I have these three modules with the following structure: |-- modules | |-- create_resources | | |-- LICENSE | | |-- Modulefile | | |-- README | | |-- lib | | | `-- puppet | | | `-- parser | | | `-- functions | | | `-- create_resources.rb | | |-- spec | | | |-- spec.opts | | | |-- spec_helper.rb | | | `-- unit

When running cloud-init im getting the following error Cloud-init v. 0.7.9 running 'modules:config' at Mon, 04 Dec 2017 18:07:26 +0000. Up 2597.52 seconds. Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile

Hi, I''m new to Puppet so may be going about this completely the wrong way, or perhaps it is an selinux problem rather than a Puppet problem. I have a problem copying a file and changing the seltype. I don''t think it is Nagios specific. Code is something like: file { ''/usr/sbin/nrpe'': source =>

Hi, I''m gettinng a dependency cycle when using PE 2.7, puppetlabs::mrepo, "role classes" and hiera : I''m trying to mirror RHN repos : # ROLE CLASS > class site::yum_repository{ > > $repos = hiera(''site::yum_repository::repos'') > create_resources(mrepo::repo::rhn, $repos) > } > # HIERA DEFAULTS >

G''day. We recently found some issues with the `links => follow` setting in recursive file copying; the designed behaviour is that it should allow you to determine if the master serves a symlink in a module as a symlink, or as the content of the file that the symlink points to. The full details are here: https://projects.puppetlabs.com/issues/12418 The short version is that toggling

Hello list, I try to install puppet agent on Debian Lenny. I got following error. Seems the repo is broken : ----------------------------------------------------------------------------------------------------------------------------------- node001:~# wget http://apt.puppetlabs.com/puppetlabs-release-lenny.deb --2012-10-12 02:12:12-- http://apt.puppetlabs.com/puppetlabs-release-lenny.deb

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''ve configured puppet to use storedconfigs and puppetDB, If I start the puppet master using the init script puppetmaster I get a permission denied error when a node connects: Master: [root@puppet ~]# service puppetmaster start Starting puppetmaster: [ OK ] Node: [root@puppet-slave ~]# puppet agent --test err: Could not retrieve catalog from remote

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

All, There are now development package repos located at yum.puppetlabs.com and apt.puppetlabs.com. Moving forward, these repos will contain Release Candidate packages of Puppet, Facter, Puppet Dashboard, MCollective and Hiera, including the soon to be released RCs of Puppet 3.0 and its dependencies, Facter 2.0 and Hiera 1.0. Packages are available to easily add these repos to yum and apt

Puppet 3.2.4 is now available. 3.2.4 addresses two security vulnerabilties discovered in the 3.x series of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and CVE-2013-4761. All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade to 3.2.4. For more information on these vulnerabilities, please visit http://puppetlabs.com/security/cve/cve-2013-4761

Just tried to install mod_passenger from puppetlabs yum repo, and it is failing with the following error: ---> Package mod_passenger.i686 0:2.2.5-1 set to be updated --> Processing Dependency: rubygem-passenger = 2.2.5-1 for package: mod_passenger ---> Package mod_passenger.x86_64 0:2.2.5-1 set to be updated --> Processing Dependency: rubygem-passenger = 2.2.5-1 for package:

Hi, I followed puppetlab procedure to install open source version of puppet agent 3.x. It works for CentOS 6.4 but not RHEL 6.4, anyone has pointer where I missed ? [root@mon04 ~]# yum install puppet Loaded plugins: product-id, refresh-packagekit, security, subscription-manager This system is receiving updates from Red Hat Subscription Management. rhel-6-server-cf-tools-1-rpms

Hello, First of all I am new to the Puppet technology. I am trying to get my puppet agent (windows) to reach my puppet master (Linux) server. In this tutorial: http://docs.puppetlabs.com/learning/agent_master_basic.html It claims to test your puppet agent you need to use the ''puppet agent --test'' command. My result when I tried this is: C:\Program Files (x86)\Puppet

Hello all, Can someone please explain why there is a manifests folder in /etc/puppetlabs/puppet e.g. /etc/puppetlabs/puppet/manifests If there is a manifests folder within each modules folder in /etc/puppetlabs/puppet e.g. /etc/puppetlabs/puppet/modules/ntp/manifests Is this directory /etc/puppetlabs/puppet/manifests for building out your config tree''s and calling modules etc. if

I''m reasonably confident that the problem I''m having here is upstream. RHEL5: # yum repolist | grep puppet puppetlabs-deps Puppet Labs Dependencies El 5 - x86_64 45 puppetlabs-products Puppet Labs Products El 5 - x86_64 161 # yum clean all Loaded plugins: security Cleaning up Everything # yum repolist 2>&1 | grep puppet