search for: stahnma

Dear Patrice, I have noticed that you are referencing to the Stahnma repository for Spacewalk Client Tools. These are quite old and I would suggest to use the tools from: http://spacewalk.redhat.com/yum instead. Mr. Suchy already pushed some of the packages to Fedora/EPEL so they might be available there, soon. Besides that the Spacewalk Team is thinking about a...

Hy I m new to puppet. I ''d like to install epel.repo on a my node and this is the module that I ve created class epel { package { ''epel'': provider => ''rpm'', ensure => installed, source => ''http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm'' } } Now my connection on node when I

Puppet Labs is really thrilled to announce, in conjunction with EMC, our new open source bare metal provisioning tool: Razor. Razor is next generation provisioning software that handles bare metal hardware and virtual server provisioning with inventory discovery and tagging, rule-based policy management, and extensible broker plugin integration. It integrates closely with Puppet and Facter. The

How do folks feel about getting Puppet job listings on this list? I''ve rejected a few that we quite spammy, but when the subject matter really is a system admin with puppet experience, the decision becomes a bit different. I''m looking for general feelings. A simple +1 or -1 would be great. Mike -- You received this message because you are subscribed to the Google Groups

Hi all, i planned for a startup to install one of this gui tools. But if i look in the documentation, or google it, i find no results which helps. If i would like to install the rpm package i get the following dependencies problems rpm -i puppet-dashboard-1.2.3-1.el6.noarch.rpm warning: puppet-dashboard-1.2.3-1.el6.noarch.rpm: Header V4 RSA/SHA1 signature: NOKEY, key ID 4bd6ec30 error: Failed

Hi, I am trying to install puppet-dashboard on my puppet server, which is running CentOS 5.4. However, I cannot find a RPM for REHL 5 on http://yum.puppetlabs.com/. So the question is how I can get the puppet-dashboard rpm for CentOS 5.4? Thanks. Hai Tao -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send

Since our move to github for pull requests and patches, the usefulness of puppet-dev has declined significantly. puppet-dev used to be a great list for development discussion of puppet and the ecosystem around it. With the information and pull request emails from github, unless everybody has finely-tuned their email clients, the puppet-dev list has turned into mostly noise. We have a goal to

Greetings, I''d like to remove the cruft (no longer maintained) areas of yum.puppetlabs.com. I fear they only cause confusion and offer less-than-desirable experience for our users. I''d like to remove /base /prosvc /porsvc.unsigned /SRMS /sources I''d like to do this some time next week. The stuff mostly found in base is available elsewhere and signed properly. The

Got the following: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload package: Could not autoload /usr/local/lib/site_ruby/1.8/puppet/provider/package/windows.rb: no such file to load -- windows/error at /etc/puppet/modules/php/manifests/init.pp:28 on node This after I reverted back to puppet v2.7.11 on my master. Not running windows anywhere... why am I

Puppet 2.7.8rc1 is available. 2.7.8rc1 contains everything that was being previewed in the 2.7.7rc series as well as some new content. Key highlight in this release (beyond items from 2.7.7rc series) are: * Allow providers to be selected in the run they become suitable * Showdiff is now not auto-enabled when running in noop mode * Provide default subjectAltNames while bootstrapping

Does anyone know where I can get the latest puppet, 2.7.1 as RPM''s? The spec file that comes with the puppet 2.7.1 source is broken again, and only version 0.25.5 seems to be available via EPEL, which means that the website''s assertion that you can get puppet as an RPM from there is somewhat untrue. Douglas. -- You received this message because you are subscribed to the

This a feature release candidate (number 3) of Puppet Dashboard. If you''re wondering what happened to rc2, it was internal only. Our CI system found a few issues before we released it to the public. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download

I want to use Puppet and Facter on a machine where I don''t have sudo or root access privileges. I won''t be using Puppet for anything that requires that level of access, so I should be OK if I can get it on the box. Any advice on how to proceed? Currently the Facter installer complains that it doesn''t have privileges for /usr/bin/facter. I assume Puppet will have the same

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

I am finding that the puppetlabs-apache module is somehow adding 30-60 seconds onto a host''s catalog compile time when the puppetmaster has no other hosts contacting or generating catalogs. The Puppetmaster is setup to use Puppet-2.7.18 - Apache & Passenger. RIght now only 2 hosts are even configured to use this new PM, the PM itself and a Foreman host. With neither hosts

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)

We''ve run into a couple of bugs deemed "must fix" for puppet 2.6.10. Thus we will be delaying the 2.6.10 rc until these are fixed. We are hoping to have them squashed within the next week. As a reminder, 2.6.10 is the last planned release in the 2.6 branch of Puppet. For more background on 2.6.10 see:

It''s the time of year again where we gather the Puppet faithful from around the world and hold PuppetConf. What started last year in Portland is moving to San Francisco this year, with a bigger venue, more tracks and amazing speakers. PuppetConf 2012 takes place in San Francisco, from September 27–28. So, why am I emailing you today about it? Well, early bird pricing ends today.

Puppet 2.6.12 is a security update release in the 2.6.x branch. The only changes since 2.6.11 are security fixes for the following vulnerability: * CVE-2011-3872, Altnames Vulnerability For more details on this vulnerability, follow the link on our blog post: http://puppetlabs.com/blog/important-security-announcement-altnames-vulnerability/ Other information available at:

This release addresses issues with the Puppet 2.7.0rc3 series. This release is available for download at: <http://goog_1305397870/> http://www.puppetlabs.com/downloads/puppet/puppet-2.7.0rc4.tar.gz See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected