similar to: Yum Repositories appear to be offline

I wonder if PuppetLabs will work with Amazon to try to add Puppet as an option to OpsWorks as well ? I don''t think people using Puppet with AWS in a stable fashion would try to move to OpsWorks and migrate everything to Chef, but new customers/startups would think twice in choosing Puppet if the service offered in AWS OpsWorks is based on Chef. I haven''t tried OpsWorks yet,

I can''t seem to find any direct reference yo this in the puppet 3.0 docs so does anyone know if puppet 3.0 can handle yum groupinstalls without resorting to using an exec? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/5QboggWCwh4J. To

Hi all, Being new to puppet 3 and to Ruby. Does there exist a chart of the Ruby I should know? Hugs, Sandra -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/yuEGLZKgC_4J. To post to this group, send email to puppet-users@googlegroups.com. To

Hello all, Does anyone currently manage Cisco ASA''s out there via Puppet, if so how ? Due to the size of our network it would be great if Puppet could manage Object-groups and ACL''s etc to try and standardize across our ASA hosts. e.g. On one ASA an Object-group would be called monitoring_server on another ASA mon_srv another ASA monsrv It makes understanding the

Sharing my stoopid mistake in the hopes of saving someone else the same grief: I had a boolean toggle that was not performing as expected. Long story short: I had put quotes around the word "false" class { ''foo'' : boolFlag => "false" } was coming up TRUE To fix it, lose the quotes class { ''foo'' : boolFlag => false } “Sometimes I

Hello- I''m running puppet enterprise 2.5.1 and just installed the puppet- rundeck gem. When I try and start puppet-rundeck, I receive the message below: You need to have Puppet 0.25.5 or later installed /usr/lib64/ruby/gems/1.8/gems/puppet-rundeck-0.0.7/lib/puppet- rundeck.rb:34:in `configure'': uninitialized constant Class::Puppet (NameError) from ./puppet-rundeck:62

So some of you may be aware that Tim Sharpe from GitHub wrote a Puppet linting tool: $ gem install puppet-lint $ puppet-lint mymanifest.pp Source: https://github.com/rodjek/puppet-lint The linting tool checks Puppet code for "best practice" based on the Puppet Labs Style Guide: http://docs.puppetlabs.com/guides/style_guide.html A lot of us have been using puppet-lint (and puppet

OS - RHEL5.7 Installation Source - epel-testing repo Puppet server version - 2.6.6 puppetd version - 2.6.6 I searched Google and none of the answers were a match for my set up... I can do ''puppetd --test'' from the client and things work as expected. When doing puppet kick hostname I get the following: Triggering hostname Host hostname failed: hostname not match with the server

kindly provide me link for documents for puppet other than puppet lab I am specifically looking at how to create a module/manifest -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com.

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 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

Hi all We''ve just released version 0.3.4 of the puppet-module tool used to create and retrieve modules from the Puppet Labs Forge (http://forge.puppetlabs.com). You can update using Ruby gems: $ gem install puppet-module There are several important changes in this release: * Add ability to install modules with hyphens * Add check for symlink when installing * Install modules to their

Started the discussion in puppet users mailing list based on recommendation from luke. This discussion is to a follow up regarding bug#1955 "Could not find server puppet" - installation/configuration error". jamtur01''s last recommendation: Rather than renaming things try the certname option (see http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference). But

Hi, I am working on some tools that read and write pp files, and I wonder if there are some pp files available somewhere that can be used to test a parser. I am especially interested in if there are some tests written that capture invalid syntax. - henrik -- 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

All too quickly we''re back with a maintenance release: 2.6.3. This release addresses some issues in the 2.6.2 release. 2.6.3 is a maintenance release in the 2.6.x branch and it contains only bug fixes and no new features or other changes. The release candidate is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.3rc1.tar.gz Please note that all final

I have successfully updated puppet clients from my master using the built-in WEBrick server. When I updated my setup to using Apache2+passenger, my clients get this error message: err: Could not retrieve catalog from remote server: Error 400 on SERVER: You cannot save facts to the code store; it is only used for getting facts from Facter warning: Not using cache on failed catalog err: Could not

Hi, I have create the following module: modules/foo `-- manifests |-- definitions | `-- line.pp `-- init.pp $ cat modules/foo/manifests/init.pp import "definitions/*.pp" $ cat modules/foo/manifests/definitions/line.pp define myline($file, $line, $ensure = ''present'') { .... } I try to use the definition in a class: class testfile { file {

I''ve upgraded to puppet v2.6.2 on ubuntu (clients and server) and now I get this error messages related to pluginsync: info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate'': wrong header line format err: /File[/var/lib/puppet/lib]: Could not evaluate: wrong header line format Could not retrieve file

All, Trying to install puppet-2.6.3 on CentOS 5.4 and I get the following. [root@stsdev-pri ~]# gem install puppet-2.6.3 ERROR: http://rubygems.org/ does not appear to be a repository ERROR: Error installing puppet-2.6.3: puppet requires facter (>= 1.5.1, runtime) Facter is installed: [root@stsdev-pri ~]# facter -v 1.5.8 Ruby is installed: [root@stsdev-pri ~]# ruby --version ruby