similar to: upgrade to 3.0, ruby and rhel 5

Hello Everybody, I am trying to install puppet on Red Hat Enterprise Linux Server release 5.8 Beta (Tikanga) I have installed the following rpms sudo rpm -ivh http://yum.puppetlabs.com/el/5/products/i386/puppetlabs-release-5-6.noarch.rpm I am getting the following error when I am trying to install puppet server sudo yum install puppet-server puppet-3.0.1-1.el5.noarch

Hi, I''m having a weird issue and was wondering if anyone else had run into it. I recently upgraded from puppet 2.7 -> 3.0.1 After cleaning up some gems on my puppet master everything seemed to be working ok. I had originally used the EPEL repo''s to deploy puppet, but switched to the Puppet Labs repos so I could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR

This is the third time I''ve sent a message about this. Does anybody know what''s going on? I''m going to file a bug if this isn''t fixed soon. RHEL6: http://yum.puppetlabs.com/el/6/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.sqlite.bz2 from

Does anyone have any insight into this error message? err: Could not retrieve catalog from remote server: Error 400 on SERVER: The fact named fact_stomp_server does not appear to be a valid hostname. The value of '''' does not match ''^[a-zA-Z0-9.-]+$''. A common cause of this problem is running puppet agent as a normal user instead of root, or the fact is

Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz Available in native package format in the Puppet Labs yum and apt repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Please report

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

Hi, I have sent this mail to info@puppetlabs.com and received no answer, so I''m posting here as well; I hope somebody at PuppetLabs will be able to help. I have a local mirror of apt.puppetlabs.com which has been broken for at least a few days: the apt/dists/ subdirectory only contains symlinks to non-existent files. [mirror@excellent dists]$ ls -l total 0 lrwxrwxrwx 1 mirror mirror 29

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

There''s a problem installing puppet on Solaris 10 -- in this situation, we aren''t really doing anything with puppet there. The version we''re using is: ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-solaris2.9] Here''s the first error: # gem update puppet > > Updating installed gems > > Updating puppet > > Building native extensions. This

Hi, I am having problems installing Puppet Server. My gem list follows and then the attempt to install puppet-server. The specific errors are: Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs) Requires: ruby-augeas Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs) Requires: rubygem-json Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

Fedora 16 reached end of life on 2013-02-12 [1], so we are no longer building new packages for it and will remove it from our yum repository on Monday, May 6. [1] - https://lists.fedoraproject.org/pipermail/announce/2013-February/003144.html -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop

Hello Everybody, I am looking for a way to trigger puppet rum remotely. so that i don''t need to login into individual nodes and perform the puppet agent --test from there. Is there any alternative to puppet kick in puppet 3.0, since its being deprecated in telly. Also , can anybody tell how to configure foreman 1 to trigger puppet run from the gui in puppet

Hello, I''m trying to install facter latest on OEL 5.5 but can''t because virt-what doesn''t appear to be in the oracle repositories or EPEL. Can anyone confirm/deny this? Thanks, Spencer Krum -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it,

Puppet Dashboard 1.2.13 is a maintenance and bugfix release of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at:

What is the best and easy''t way to let all nodes ssh passwordless to each other ? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com.

Puppet 2.7.19 (Puppet Enterprise 2.7.0) When I try to uninstall/purge the product using command below, /var/lib/peadmin/.* remains ./puppet-enterprise-uninstaller -pd [root@puppettarget peadmin]# ls -la total 44 drwx------ 5 502 502 4096 Feb 13 13:13 . drwxr-xr-x. 24 root root 4096 Feb 13 15:13 .. -rw------- 1 500 500 1952 Feb 12 16:18 .bash_history -rw-r--r-- 1 502 502 192 Feb 11

Hello, I am working on building an internal repo for RHEL6 x86_64 and I don''t see any augeas rpms in the puppetlabs repo? There are for i686 but not x86_64? Are the rpms "noarch" that can be used for both? -chrisl -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

When I deploy a module I wrote with couple of custom facts, those facts do not show up in factor. But when I point FACTORLIB to the directory with those factor, they work just fine. I am running a masterless puppet version 2.7.22 and factor 1.7.1 The module structure looks like so: -license ---lib -----facter -------license.rb -------hardware_serial.rb -----puppet Any idea what is causing

Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to accompany Puppet 3.0 and Hiera 1.0. It includes Puppet functions for hiera and also the puppet backend for hiera lookups. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz * Apt and yum development repositories * Apple package

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip