http://blog.gmane.org/gmane.comp.sysutils.puppet.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53163 <pre>Team, I am in the process of investigating issues that going to popup during migration process. Currently I have installed puppet 3.1.1 from yum repository of puppetlabs The installation process is pretty much strait forward but when I try to test the modules which were written based on the puppet-0.25.4, Most of the files sourced from the puppet server to agents using the following format, source =&gt; [ "puppet:///bamssh/sshd_config.$hostname", "puppet:///bamssh/sshd_config.$virtual", "puppet:///bamssh/sshd_config.$operatingsystemrelease" ], I am getting the following error message when I run the following command on master server ... (puppet apply bamssh/test/init.pp --debug) -------------------------------------------------------------------------------------------------------------------------------------------------------------------- *Error: /Stage[main]/Bamssh/File[/etc/ssh/sshd_config]: Could not evaluate: Could not retrieve information from environment production source(s) puppet:///modules/bamssh/sshd_config.oel-puppet-master, puppet:///modules/bamssh/sshd_config.virtualbox, puppet:///bamssh/sshd_config.5.9* *Notice: /Stage[main]/Bamssh/Service[sshd]: Dependency File[/etc/ssh/sshd_config] has failures: true* *Warning: /Stage[main]/Bamssh/Service[sshd]: Skipping because of failed dependencies* --------------------------------------------------------------------------------------------------- When I specify the modules in the path, everything went fine when I run the same command (puppet apply bamssh/test/init.pp --debug) ... *source =&gt; [ "puppet:///modules/bamssh/sshd_config.$hostname", "puppet:///modules/bamssh/sshd_config.$virtual", "puppet:///modules/bamssh/sshd_config.$operatingsystemrelease" ],* ------------------------ Debug: Executing '/sbin/service sshd status' Debug: /Schedule[never]: Skipping device resources because running on a host Debug: /Schedule[weekly]: Skipping device resources because running on a host Debug: /Schedule[puppet]: Skipping device resources because running on a host Debug: Finishing transaction 70344638024840 Debug: Storing state Debug: Stored state in 0.01 seconds Notice: Finished catalog run in 0.32 seconds ------------------------------------------------------------------------------------------------------------ There are many places that requires this change, is there any round about to use old format in specifying path without the word "modules" word in sourcing file from puppet server to client (node) Could someone advise best-way to migrate from puppet-0.25.4 to the latest puppet, I will appreciate if someone share their experiences in migrating old puppet version to the latest ... Thank you very much in advance ,,,... </pre> Jagan Kommineni 2013-05-18T17:16:11 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53162 <pre>Hello, i'm starting using Puppet on my personal lab. There I'd like to reproduce a multi base tomcat installation as follows: * Multiple jdk installations (multiple 1.6.x, multiple 1.7.x) * Multiple tomcat installations (multiple 6.0.x, multiple 7.0.x) Here is the problem: using the Package definition, i'm unable to have multiple jdk version (as 1.6.4 supersedes 1.6.3, leaving only the last one installed correctly), so I created a custom define that uses a File definition to copy multiple directories (/opt/java/jdk-$version) from my puppetmaster (recurse + purge) and used this as follows: tomcat::home { "6.0.37": version =&gt; "6.0.37"} jdk::home { "1.6.24": version =&gt; "1.6.24"} but i'm unable to create a simple check on my tomcat istances like a require tomcat-6.0.37. How can i accomplish what i need? Thanks in advance. Luca Gervasi </pre> Luca Gervasi 2013-05-18T08:38:47 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53161 <pre>Hi list, We are organising our first workshop on how to start testing modules with puppet. This will be held on Friday, 31 May, at 7 PM. Details can be found on our meetup.com page : http://www.meetup.com/Belgian-Puppet-User-Group/events/113028972/ Hope to see you there Johan </pre> Johan De Wit 2013-05-18T20:49:56 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53157 <pre>I've got a puppet 2.6 deployment (w. passenger) with mcollective 1.0 sprinkled in, happily managing about 200 centos/rhel nodes. Recently we added Foreman 1.1 in just to get a reporting dashboard. We never used storeconfigs (didn't want to throw a DB into the mix as we grew it out) and it's starting to show cracks - not in performance, just in hackiness (lots of 'module::settings::shared_between_2_modules' and so on, just to share state between nodes). hiera is helping a lot there, though we're using a creaky old version i added in by hand. What I'd like to do this summer is get us up to puppet 3.x , uplift mcollective and look at PuppetDB in there too (mainly to share facts etc. outside the puppet admin team; we have a homegrown inventory CRUD webapp that essentially duplicates all the information we already have in puppet, mainly because we don't have an easy way to expose it). My reading suggests it's worth going to puppet 3 first (fresh puppetmaster, copy over /etc/puppet and SSL bits and bobs, migrate nodes to test and eventually flip DNS for puppet.ourthing.com over). Then mcollective, then add in puppetdb later on. The only other fly in the ointment is we currently get puppet from EPEL and so need to start mirroring the puppetlabs repos I guess. Does this sound sane-ish? Or would people recommend trying a 2.7 stepping stone first? My main worry is the scoping changes in 3.x, since without storeconfigs we have a lot of globals flying around... </pre> Dick Davies 2013-05-18T09:27:13 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53156 <pre>Puppet 3.2.1-rc1 is a bugfix release candidate for the 3.x series of Puppet. This release addresses two major issues that were uncovered in 3.2.0 and caused us to pull that release (#20726 and #20742). It also includes a fix for Solaris support (#19760). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1-rc1.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.2.1.rc1.gem or by using `gem install puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.2.1-rc1.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.2.1-rc1.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.2.1-rc1: https://projects.puppetlabs.com/projects/puppet/ ========================== ## Puppet 3.2.1-rc1 Contributors ## ========================== Andrew Parker, Hailee Kenney, Josh Cooper, Josh Partlow, Matthaus Owens ============================ ## Puppet 3.2.1-rc1 Release Notes ## ============================ ### Issues fixed: * [Bug #19760]: install sun packages failed with: `Error: /Stage[main]/Inf_sol10defaultpkg/Package[SMCcurl]: Could not evaluate: Unable to get information about package SMCcurl because of: No message` * [Bug #20726]: usermod command arguments out of order * [Bug #20742]: unauthenticated clients unable to communicate with puppet master (running in passenger) ### Known Regressions On Windows, Puppet 3.2.1 is unable to manage the home directory for a user account. ([Bug #20768]) This is a regression from Puppet 3.1.1; it was introduced by switching to Ruby 1.9 in the Windows .msi package. This bug will be fixed soon in a point release, but wasn't severe enough to delay shipping. ### All 3.2.1 Changes To see a list of the issues addressed by this release, check out the 3.2.1 version in our issue tracker at: https://projects.puppetlabs.com/versions/405 ========================= ## Puppet 3.2.1-rc1 Changelog ## ========================= Andrew Parker (3): 76664ae (Maint) Give each test a meaningful name ab670d1 (#20742) Handle DNs that cannot be parsed de34775 (#20742) Only use certifcate info if there is a CN Josh Cooper (1): 4274d66 (#20726) Manage home has issues on Solaris Josh Partlow (4): 0588e57 (#20726) Add user managehome acceptance tests 6f92379 Revert "Merge branch 'pull-1512'" 46df39d (#20726) Include password for useradd managehome tests on windows 866ecbc (maint) Change load order for puppet/provider/package/windows/package Matthaus Owens (1): 2576f8f (packaging) Update PUPPETVERSION to 3.2.1-rc1 Nick Fagerlund (1): b301ada Maint: Improve documentation of filebucket attributes Stefan Schulte (3): 5e091bb (#19760) Use combine when running pkginfo 887c2037 (#19760) Use pkginfo method instead of execute f04d271 (#19760) Remove unnecessary stubbing in sun_spec </pre> Matthaus Owens 2013-05-17T23:29:40 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53154 <pre>Hey Folks, I am looking at using puppet to help manage/coordinate system integration among several teams collaborating on an appliance product. This is a little different than other environments where I've used puppet for managing large numbers of systems. In the appliance case, we need to build &amp; manage only a single system so a puppetmaster becomes extra baggage that is not really needed - what features will not work without one tho? Will erb templates still work? Will modules also function without a puppet master? i'm wondering if anyone has already shared their experiences with the group using puppet in this kind of mode. If so, please share and I will summarize. Thanks, Vince </pre> Vince Taluskie 2013-05-17T22:52:11 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53149 <pre>Hi All, I've run into a bit of a tangle. I currently have two puppet masters which are "load balanced" with round robin DNS (one is also the CA). I'm using dns_alt_names to let them each answer to puppet.my.domain.com For the past year this has been fine. About a week ago I tried to add a third &amp; while all my Linux clients are happy with the new arrangement, my smaller number of FreeBSD9 systems fail with: puppet-agent[73345]: Failed to apply catalog: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: (null) when hitting the newly deployed server. If I give the specific host name as the --server argument (rather than the alternative name that get the round robin dns) puppet agent connects runs properly. I've tracked this down to the FreeBSD client using SNI where as the Linux clients do not and the older servers don't support SNI so it is ignored. All server are using apache mod_ssl and passenger, but I'm not sure how to proceed. I could generate a "puppet.my.domain.com" certificate, distribute it to all the servers and set up name based virtual hosts that SNI is designed to facilitate, but then I can't selectively revoke the certs if there's a security issue with one server, so I'd rather keep my per host certificates with dns_alt_names. This is probably more of an apache question now, but does anyone here know how to get Apache to accept an SNI for a name that is a dns_alt_name of a cert rather than the CN? Or more puppetly if there's a config option to not send an SNI from the client? Though that seems the wrong way to fix the problem. Thanks, -Jon </pre> Jonathan Proulx 2013-05-17T19:46:24 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53147 <pre>Between tagging 3.2.0 final and actually releasing it, a bug was discovered in the user provider related to managehome on redhat based systems (https://projects.puppetlabs.com/issues/20726). Rather than ship 3.2.0 with that bug, we're readying Puppet 3.2.1 for a fresh rc series to address this issue. We anticipate a release candidate for 3.2.1 later today. And many thanks to our users who try out our release candidates and catch these issues. -- Matthaus Owens Release Manager, Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Early Bird discount - save 25%! </pre> Matthaus Owens 2013-05-17T18:03:14 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53145 <pre>hi, I have upgraded puppet from 2.7 to 3.0 and reinstalled puppetdb and converted the new certs to truststore.jks and keystore.jks under the correct directory. I am using activeMq with mcollective below is puppet.conf [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl pluginsync = true certname = puppet.srv.my.net.uk certdnsname = puppet.srv.my.net.uk certificate_revocation = false [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig pluginsync = true report = true archive_files = true [master] ssl_client_header = HTTP_X_SSL_SUBJECT ssl_client_verify_header = SSL_CLIENT_VERIFY reports = store, http reporturl = http://puppet.srv.my.net.uk/reports/upload storeconfigs = true storeconfigs_backend = puppetdb certname = puppet.srv.my.net.uk certdnsname = puppet.srv.my.net.uk I ran puppetmaster in daemon verbose mode and get this error Error: Permission denied - /root at /etc/puppet/modules/motd/manifests/config.pp:2 on node bladon.srv.my.net.uk Wrapped exception: Permission denied - /root Error: Permission denied - /root at /etc/puppet/modules/motd/manifests/config.pp:2 on node bladon.srv.my.net.uk Error: Permission denied - /root at /etc/puppet/modules/motd/manifests/config.pp:2 on node bladon.srv.my.net.uk Error: Report processor failed: Connection refused - connect(2) Info: Caching node for bladon.srv.my.net.uk Info: 'replace facts' command for bladon.srv.my.net.uk submitted to PuppetDB with UUID bcd26215-f3ce-4434-8da2-fcc7e818723b Info: Caching node for bladon.srv.my.net.uk Notice: Compiled catalog for bladon.srv.my.net.uk in environment production in 1.98 seconds Info: Caching catalog for bladon.srv.my.net.uk Info: 'replace catalog' command for bladon.srv.my.net.uk submitted to PuppetDB with UUID f03476d3-0e73-4629-a385-fff466d84269 Info: Could not find file_bucket_file for 'md5/2cb091b0a500c609b3feebd040703400/etc/motd' Info: FileBucket adding {md5}2cb091b0a500c609b3feebd040703400 Error: Not authorized to call find on /file_metadata/utils/o2prop.rb Error: Not authorized to call search on /file_metadata/mcollective/mcollective with {:links=&gt;"manage", :recurse=&gt;true, :checksum_type=&gt;"md5"} Error: Not authorized to call find on /file_metadata/mcollective/mcollective Error: Report processor failed: Connection refused - connect(2) can anyone suggest me the steps to fix the issue? kshk </pre> Raj K SHK 2013-05-17T15:56:07 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53143 <pre>Hi all is there a way to keep a history of facts for a given node, other than taking a periodic snapshot of the inventory service? Thanks </pre> carlo montanari 2013-05-17T15:29:26 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53134 <pre>Was wondering if someone has implemented the management of multiple MySQL instances using puppet on the same server? Essentially we want to use the same MySQL binaries but implement multiple distinct MySQL instances connecting via a specific port number. Puppet Forge has a great MySQL implementation including databases, users and permissions but it doesn't seem to allow for managing multiple instances. Any information would be greatly appreciated. </pre> Peter Krawetzky 2013-05-17T14:12:49 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53130 <pre> I have to change a file in c:\Program Files &lt;x86&gt;\MSBuild\Microsoft.Cpp\v4.0. I have tried various ways to encapsule the Windows path with spaces but to no avail. The following file { "\"c:\\program files &lt;x86&gt;\\MSBuild\\Microsoft.Cpp\\v4.0\\Microsoft.CppCommon.targets\"": ensure =&gt; present, source =&gt; 'puppet:///modules/install_programs/Microsoft.CppCommon.targets', } causes this error: info: Caching catalog for w7entbase.metratech.com err: Failed to apply catalog: Parameter path failed: File paths must be fully qualified, not '"c:\program files &lt;x86&gt;\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets"' at /etc/puppetlabs/puppet/modules/test/manifests/init.pp:17 Any suggestions will be greatly appreciated. Werner </pre> wernerbahlke 2013-05-17T13:28:20 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53126 <pre>Due to upgrading to Debian 7 Wheezy , I choose to rebuilt our puppet setup. Now all went well except that I have one issue , changes made via puppet dashboard do not get pushed to the client. I have used the APT repository from puppetlabs to install all the servers and clients. I can run puppet agent -t --debug and no errors popup clean catalog run, and the reports in puppet dashboard show up cleanly as well. Yet when I add clases direct or via group inheritance to the nodes they do not get this pushed to them. Now I use puppetdb and the puppet dashboard mysql on a separate server buut also there I do not see any errors, except that my inventory SSL certificate doesn't match but that I have had on the previous setup as well and that shouldn't be the issue. Any ideas to where else I can look or maybe heighten debugging somewhere to get an idea ? Thanks, Jelle </pre> Jelle B. 2013-05-17T08:25:47 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53117 <pre>Hi all, I know that there are likely a few ways to solve the following. I just don't know what the best way may be :) We're trying to work out how do something similar to the following scenario. How do we apply a policy to uninstall CUPS from all servers, except for a configurable group of "some". To put it another way, how can we have an policy that will configure CUPS on a known list of servers (hiera array perhaps?), and uninstall from all other $kernel=Linux machines? Best to get the install list right first then feed via ENC, or? Regs, Stephen </pre> Stephen Wallace 2013-05-17T00:33:25 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53114 <pre>I'm using Fedora 18 KDE in VirtualBox, fresh install this morning with full updates using yum. I installed puppet by adding the puppet labs yum repo and then "sudo yum install puppet", so now I'm running puppet version 3.1.1 Running "puppet --version" or "sudo puppet agent --test" gave me the following error: */usr/share/rubygems/rubygems/custom_require.rb:36:in `require': cannot load such file -- puppet/util/command_line (LoadError)* * from /usr/share/rubygems/rubygems/custom_require.rb:36:in `require'* * from /usr/bin/puppet:3:in `&lt;main&gt;'* As far as I can tell with my limited knowledge of Ruby, Linux and Puppet, /usr/bin/puppet has a line "require 'puppet/util/command_line'" which executes via /usr/bin/ruby. The custom_require.rb script (part of ruby) then looks for a file puppet/util/command_line relative to itself which it can't find. Looking at an AWS Linux box where puppet is working, I can see that the custom_require.rb file is located at /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb, whereas on my Fedora box the file is located at /usr/share/rubygems/rubygems/custom_require.rb, the problem is that puppet has installed it's ruby files in /usr/lib/ruby/site_ruby/1.8, but they should actually be in /usr/share/rubygems. The first fix was to add "RUBYLIB=/usr/lib/ruby/site_ruby/1.8" in /etc/environment and "export RUBYLIB=/usr/lib/ruby/site_ruby/1.8" at the beginning of /etc/rc.d/init.d/puppet but that felt pretty dirty so now I've done this: *sudo mv /usr/lib/ruby/site_ruby/1.8/* /usr/share/rubygems/ * *sudo rm -r /usr/lib/ruby/site_ruby/1.8 * *sudo ln -s /usr/share/rubygems /usr/lib/ruby/site_ruby/1.8* If anyone has a better solution I'm all ears, ideally I'd like to just use yum for puppet and any of it's dependencies, tweak the puppet.conf file and everything work (like it does in EC2, etc), Do I have to install another version of ruby?? Or set an environment variable before installing puppet so it knows where to put the files?? Maybe it's just Fedora's weird ruby install process? Here's a yum list just in case: $ sudo yum list installed | grep ruby libselinux-ruby.x86_64 2.1.12-7.3.fc18 &lt; at &gt;updates ruby.x86_64 1.9.3.392-29.fc18 &lt; at &gt;updates ruby-augeas.x86_64 0.4.1-4.fc18 &lt; at &gt;fedora ruby-irb.noarch 1.9.3.392-29.fc18 &lt; at &gt;updates ruby-libs.x86_64 1.9.3.392-29.fc18 &lt; at &gt;updates ruby-shadow.x86_64 1.4.1-17.fc18 &lt; at &gt;fedora rubygem-bigdecimal.x86_64 1.1.0-29.fc18 &lt; at &gt;updates rubygem-io-console.x86_64 0.3-29.fc18 &lt; at &gt;updates rubygem-json.x86_64 1.6.8-1.fc18 &lt; at &gt;updates rubygem-rdoc.noarch 3.12-6.fc18 &lt; at &gt;updates rubygems.noarch 1.8.25-6.fc18 &lt; at &gt;updates </pre> Tom Poulton 2013-05-16T23:22:35 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53112 <pre>Greetings, When writing modules are people namespacing them to avoid collisions with puppetlabs' modules? I wrote some (very simple) modules: mysql postgresql that now have namespace conflicts when I am trying to install the puppetlabs modules of the same name. Is there a best practice or style guide that people follow when namespacing their in-house modules? For instance: site::umn::duluth::postgresql ?? Thanks for any hints or feedback! -mz </pre> Matt Zagrabelny 2013-05-16T22:10:44 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53111 <pre>I am developing a custom provider and have a requirement on a gem. Is there any way to use the gem with a custom provider without installing the gem on the managed node? Ideally I want to keep the gem isolated from other puppet code to avoid any potential conflicts as well. I am currently running under puppet 3.0. </pre> Schofield 2013-05-16T21:53:28 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53109 <pre>I need to be able to run a certain class ONLY when it is called manually from the client. I created a class named "manual" and can run it from the client like this: puppet agent --no-daemonize --onetime --verbose --tags=manual However it only works if that class is specified in the node definition. I don't want this class to run automatically on the normal node run with the other classes. Is there any way to do this? </pre> Nev 2013-05-16T20:38:23 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53097 <pre>Hi I am trying to install vim-puppet for syntax highlight of puppet manifest file. I first installed vim-puppet and then vim. Then I ran "vim-addon-manager -w install puppet" I am still unable to see the colours on site.pp bala&lt; at &gt;WheezyMaster:~$ vim-addon-manager # Name User Status System Status editexisting removed removed justify removed removed matchit removed removed puppet *installed installed* bala&lt; at &gt;WheezyMaster:~$ bala&lt; at &gt;WheezyMaster:~$ vim --version VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Feb 10 2013 06:46:22) bala&lt; at &gt;WheezyMaster:~$ dpkg -l | grep vim ii vim 2:7.3.547-7 i386 Vi IMproved - enhanced vi editor ii vim-addon-manager 0.5.2 all manager of addons for the Vim editor ii vim-common 2:7.3.547-7 i386 Vi IMproved - Common files ii vim-gnome 2:7.3.547-7 i386 Vi IMproved - enhanced vi editor - with GNOME2 GUI ii vim-gui-common 2:7.3.547-7 all Vi IMproved - Common GUI files ii vim-puppet 2.7.18-4 all syntax highlighting for puppet manifests in vim ii vim-runtime 2:7.3.547-7 all Vi IMproved - Runtime files ii vim-tiny 2:7.3.547-7 i386 Vi IMproved - enhanced vi editor - compact version bala&lt; at &gt;WheezyMaster:~$ Could you please tell me where am I going wrong ? </pre> Balasubramaniam Natarajan 2013-05-16T14:27:47 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53091 <pre>So I am having issue with a manifest that contains the class below. I was in hopes somebody could point me in the correct direction; Original class, works on many others systems I have this deployed to, class base::yum_plugins{ require base::yum_repos package {yum-versionlock: ensure =&gt; latest} package {yum-security: ensure =&gt; latest} } However on a machine we are building a template out of it fails. Debug: Executing '/bin/rpm -q yum-versionlock --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} ' Error: Could not update: Could not find package yum-versionlock Error: /Stage[main]/Base::Yum_plugins/Package[yum-versionlock]/ensure: change from absent to latest failed: Could not update: Could not find package yum-versionlock Notice: /File[/etc/yum/pluginconf.d/versionlock.list]: Dependency Package[yum-versionlock] has failures: true Warning: /File[/etc/yum/pluginconf.d/versionlock.list]: Skipping because of failed dependencies Debug: Finishing transaction 70184260275260 Debug: Storing state Debug: Stored state in 0.02 seconds Notice: Finished catalog run in 6.66 seconds Debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (yaml) Debug: report supports formats: b64_zlib_yaml raw yaml; using yaml [root&lt; at &gt;rhel6Template ~]# ^C [root&lt; at &gt;rhel6Template ~]# /bin/rpm -q yum-versionlock package yum-versionlock is not installed [root&lt; at &gt;rhel6Template ~]# /bin/rpm -q yum-plugin-versionlock yum-plugin-versionlock-1.1.30-14.el6.noarch Change class to represent yum-plugin-versionlock and it fails slightly different, class base::yum_plugins{ require base::yum_repos package {yum-plugin-versionlock: ensure =&gt; latest} package {yum-security: ensure =&gt; latest} Error: Failed to apply catalog: Could not find dependency Package[yum-versionlock] for File[/etc/yum/pluginconf.d/versionlock.list Yet Setting up Install Process Package yum-plugin-versionlock-1.1.30-14.el6.noarch already installed and latest version Nothing to do and [root&lt; at &gt;rhel6Template pluginconf.d]# cd /etc/yum/pluginconf.d/ [root&lt; at &gt;rhel6Template pluginconf.d]# ls product-id.conf rhnplugin.conf security.conf subscription-manager.conf versionlock.conf versionlock.list Any help woudld be greatly appreciated; Mike </pre> michael.r.bowden< at >gmail.com 2013-05-16T12:35:38 http://comments.gmane.org/gmane.comp.sysutils.puppet.user/53090 <pre>Is there a way to fetch the list of hosts using any puppet web api? I am trying to create a report by querying and aggregating facts data from the inventory service. However, while I can fetch facts for a given hostname, I cannot find a way to remotely query the list of all hostnames. TIA, Sandip </pre> Sandip Bhattacharya 2013-05-16T12:06:26 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.sysutils.puppet.user