[Puppet Users] Help! Could not autoload puppet/provider/package/rpm
Hi all, I am using Puppet agent 3.7.3 on Red Hat Linux. On one of my machines, when I run puppet agent --test, I received error: Puppet (err): Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock Puppet (err): Could not autoload puppet/type/package: Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock Puppet (err): Could not retrieve catalog from remote server: Could not intern from text/pson: Could not autoload puppet/type/package: Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock Puppet (err): Could not retrieve catalog; skipping run Any clue why this happens? Thanks, Stacey -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b58774f5-14ad-43f3-8460-52d8a6c9add7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Breaking change named as improvement in facter 2.0
https://tickets.puppetlabs.com/browse/FACT-163 TLDR: The custom fact loading logic has been changed in facter-2.0 from recursive to only top level directories. This is definitely a change in behaviour and must be marked as a breaking change instead marked as an improvement. In puppet 2.7 and facter 1.6.7 we had defined custom facts in the following locations /var/lib/puppet/lib/facter/*network*/cus_net_fact.rb /var/lib/puppet/lib/facter/*network*/cus_net_fact2.rb /var/lib/puppet/lib/facter/*os*/cus_os_fact.rb But after moving to puppet 3.x and facter 2.4 these facts are not available due to the change https://tickets.puppetlabs.com/browse/FACT-163 The change in behaviour is not obvious and not documented clearly. While moving from puppet 2.7 to 3.x the facter version changes directly from 1.6.7 to 2.4 (skipping 2.0,2.1,2.2,2.3). Hence looking at the changelog of facter 2.4 doesn't give any information regarding this. Even in facter 2.0 where this change was made its not obvious as its marked as improvement and not as a breaking change. * The release notes for facter 2.0 need to be fixed. Also a note in release notes of facter 2.4 need to be made as users are more likely to jump form facter 1.6 to 2.4 when changing from puppet 2.7 to 3.x * The default assumption while doing the change according to facter 2.0 release notes is wrong. Facter was doing a recursive search for both command line and in puppet. We have been depending on recursive lookup and I have checked again with a fresh puppet 2.7 installation that facter does a recursive lookup in both puppet and command line. https://docs.puppetlabs.com/facter/2.0/release_notes.html#improvements In Facter 1.x the fact search path would be recursively loaded, but only when using Facter via the command line. In Facter 2.0 only fact files at the top level of the search path will be loaded, which matches the behavior when loading facts with Puppet. * Since forge modules are not using this behaviour doesn't guarantee that its not used elsewhere. If the behaviour changes irrespective of whether its used in forge modules or whether its a documented behaviour, it needs to mentioned as a breaking change. https://tickets.puppetlabs.com/browse/FACT-163 An inspection of all current forge modules shows that no existing module is using this behavior * Is the change really needed? Having the custom facts in different folders helps in categorization IMO. OS, network, application facts can be kept at separate folders which improves readability, instead of all the scripts in the same folder. * If the change is indeed required for performance reasons then it can be added as a note in upgrade notes of puppet, as most users ll not be able to link this change to facter. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/36ff1db4-ff35-4ab9-8427-d439ee30f418%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: HP-UX Puppet Agent
Hi everyone, It would be very nice to have any feedback on how to have a *functionnal PE Agent on HP-UX *as the one from Michael Glatz: Agent OS: *HP-UX 11.31 Itanium* Ruby: 1.9.1 (depot from iexpress) Puppet 2.7.12 - Installed from Source Facter 1.6.7 - Installed from Source Thank you for any replies :) Have a pretty nice day. Kindest Regards, Le mardi 18 mars 2014 16:15:08 UTC+1, Rick Copley a écrit : Hi, has anyone had success getting a puppet agent to run in HP-UX 11.31? On Thursday, April 5, 2012 11:32:15 AM UTC-4, Justin Stoller wrote: On Thu, Apr 5, 2012 at 8:22 AM, Nan Liu n...@puppetlabs.com wrote: On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz mfg...@gmail.com wrote: Removing the default group worked for the most part but I am still running into some issues It cataloged correctly and even ran the test class I created notice: Starting Puppet client version 2.7.12 debug: Finishing transaction 545631632 debug: Loaded state in 0.00 seconds processor - invalid major number usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c char_major] [-e major] [major] ... uname: illegal option -- p usage: uname [-amnrsvil] [-S nodename] debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for agent debug: Using cached certificate_revocation_list for ca info: Caching catalog for agent debug: Creating default schedules debug: Loaded state in 0.00 seconds info: Applying configuration version '1333637360' debug: /Schedule[daily]: Skipping device resources because running on a host debug: /Schedule[monthly]: Skipping device resources because running on a host debug: /Schedule[hourly]: Skipping device resources because running on a host notice: /Stage[main]/Core_permissions/File[/etc/fstab]/group: group changed 'sys' to 'root' debug: /Stage[main]/Core_permissions/File[/etc/fstab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/crontab]/ensure: created debug: /Stage[main]/Core_permissions/File[/etc/crontab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/passwd]/group: group changed 'sys' to 'root' notice: /Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode changed '0444' to '0644' debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: Class[Core_permissions]: The container Stage[main] will propagate my refresh event 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 549485440 debug: Storing state debug: Stored state in 0.04 seconds notice: Finished catalog run in 0.11 seconds debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using yaml I am now receiving this issue again mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT undefined method `each' for nil:NilClass Backtrace /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in `extended' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `extended' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in `extend' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in `extended' /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in `extend' /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in `create_from_yaml' /opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in `create_from_yaml_file' If you are using ruby 1.9.1, it is known to be problematic: http://docs.puppetlabs.com/guides/faq.html Also it automatically added the node back to default, anyway to prevent that? Looks like there's a background task automatically adding nodes. I don't know a good way around this issue. You can move the pe-* class to another group but you will need to manually add nodes to that group afterwards. There's a cron job that calls a rake task that will automatically add nodes that it knows about to the default group. You will most likely need to A) move the offending classes out of the default group as Nan suggests, or B) disable the cron job and manually add new nodes to the appropriate groups, or C) write a new cron job/rake task that will only add the
Re: [Puppet Users] Augeas editing of fstab
On Fri, Mar 20, 2015 at 7:20 AM Anthony Clark dizzysau...@gmail.com wrote: Hi there, I'm trying to add the nobarrier option to our XFS mount options in /etc/fstab using Augeas. I've tried this: Could you perhaps post working and failing examples of fstab entries? Wil -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMmm3r7BnYySLJhjG%2BwZu3Qr46BfY-Dmz%3DDBNPvxwAP74Yqycg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Use value from a hash defined in hiera datasource elsewhere in the same hiera datasource
On Sat, Mar 21, 2015 at 10:43 AM Craig Wickesser codecr...@gmail.com wrote: But I was hoping to just extract the value from the hash. Thoughts? Unless I am misunderstanding, I don't think that's possible. The 2nd bullet in Notes box in Interpolation Tokens in the Hiera Guide ( http://docs.puppetlabs.com/hiera/1/variables.html#interpolation-tokens) says: Additionally, Hiera cannot interpolate an individual element of any array or hash, even if that element’s value is a string. Wil -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMmm3r48acnr0GHqSoSnDGw%2BBmmnxRFLe3P1daafizUuCkcaTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: HP-UX Puppet Agent version 3.7.4
Hi Corentin, The only option we have is installing from gems. This is I believe possible as soon as you have ruby and rubygems installed. Keep in mind that the documentation you will find (like the one from Martin Alfke, wo did a successful install of puppet 2.x) installed the 2.x version of puppet. You are looking to get the 3.7.4 version installed, and a recent version of facter is also needed. If someone has dome experience installing a 3.x series of puppet, this would be great to hear about it. Grts Johan On 23/03/15 16:04, Corentin Blanche wrote: Hi everyone, It would be very nice to have any feedback on how to have a *functionnal PE Agent on HP-UX *as the one from Michael Glatz: Agent OS: *HP-UX 11.31 Itanium* Ruby: 1.9.1 (depot from iexpress) Puppet 2.7.12 - Installed from Source Facter 1.6.7 - Installed from Source Thank you for any replies :) Have a pretty nice day. Kindest Regards, Le mardi 18 mars 2014 16:15:08 UTC+1, Rick Copley a écrit : Hi, has anyone had success getting a puppet agent to run in HP-UX 11.31? On Thursday, April 5, 2012 11:32:15 AM UTC-4, Justin Stoller wrote: On Thu, Apr 5, 2012 at 8:22 AM, Nan Liu n...@puppetlabs.com wrote: On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz mfg...@gmail.com wrote: Removing the default group worked for the most part but I am still running into some issues It cataloged correctly and even ran the test class I created notice: Starting Puppet client version 2.7.12 debug: Finishing transaction 545631632 debug: Loaded state in 0.00 seconds processor - invalid major number usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c char_major] [-e major] [major] ... uname: illegal option -- p usage: uname [-amnrsvil] [-S nodename] debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for agent debug: Using cached certificate_revocation_list for ca info: Caching catalog for agent debug: Creating default schedules debug: Loaded state in 0.00 seconds info: Applying configuration version '1333637360' debug: /Schedule[daily]: Skipping device resources because running on a host debug: /Schedule[monthly]: Skipping device resources because running on a host debug: /Schedule[hourly]: Skipping device resources because running on a host notice: /Stage[main]/Core_permissions/File[/etc/fstab]/group: group changed 'sys' to 'root' debug: /Stage[main]/Core_permissions/File[/etc/fstab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/crontab]/ensure: created debug: /Stage[main]/Core_permissions/File[/etc/crontab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/passwd]/group: group changed 'sys' to 'root' notice: /Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode changed '0444' to '0644' debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: Class[Core_permissions]: The container Stage[main] will propagate my refresh event 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 549485440 debug: Storing state debug: Stored state in 0.04 seconds notice: Finished catalog run in 0.11 seconds debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using yaml I am now
Re: [Puppet Users] Help! Could not autoload puppet/provider/package/rpm
On Mon, Mar 23, 2015 at 6:35 AM staceytian4...@gmail.com wrote: Hi all, I am using Puppet agent 3.7.3 on Red Hat Linux. On one of my machines, when I run puppet agent --test, I received error: Puppet (err): Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock Puppet (err): Could not autoload puppet/type/package: Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock Puppet (err): Could not retrieve catalog from remote server: Could not intern from text/pson: Could not autoload puppet/type/package: Could not autoload puppet/provider/package/rpm: No such file or directory - /tmp/puppet20150323-27791-6xy78b.lock Puppet (err): Could not retrieve catalog; skipping run Any clue why this happens? SELinux enabled post-install, so various bits don't have the right labels? It might take a while, but restorecon(8) might help? Maybe start with `restorecon -n -v -r /`? Wil -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMmm3r5PdMDjRN2aaYeQ_NH-0hNCRSQOYKTE9dARhHGe28X4wA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Augeas editing of fstab
On Saturday, March 21, 2015 at 1:20:22 AM UTC+11, Anthony Clark wrote: Hi there, I'm trying to add the nobarrier option to our XFS mount options in /etc/fstab using Augeas. I've tried this: Possibly a bit heretical on this list, but I find Augeas is more trouble than it is worth and you are usually better off using templates or native resources For your case, have you tried managing the mount points with the mount resource and passing the list of options to the options parameter? John -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b9a5632c-546a-4903-8300-8d53a56411ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Am I seeing PUP-3863?
On Mon, Mar 23, 2015 at 11:37 AM Wil Cooley wcoo...@nakedape.cc wrote: I see now too that I was not just being lazy; neither the Functions section of the Language Guide nor the Custom Functions Guide -- searching for undef, null, empty and return does not yield this datum: I spoke too soon: There's a table at the bottom of the Functions section of the Language Guide that has both empty and undef; I dunno how I missed it. (Somehow I also thought that I could return :undef from Ruby to get an undef in Puppet; I'm not sure where that came from.) Wil -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMmm3r7DDtp1XSxK0%3DfVxN4qewL%3DPwYu0-cq6%2BE%2BVtF%3D%2BQ4qmg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Am I seeing PUP-3863?
On Sun, Mar 22, 2015 at 9:05 AM Henrik Lindberg henrik.lindb...@cloudsmith.com wrote: That is because an undef is passed as an empty string when given to functions (functions in general are still 3.x. API when using future parser, and also in 4.0). This explains some of the errors I've had in the past but been unable to understand. I recall now trying to find out what to expect to be returned when writing functions rspec examples and being stymied by the absense of this critical detail from the documentation. I see now too that I was not just being lazy; neither the Functions section of the Language Guide nor the Custom Functions Guide -- searching for undef, null, empty and return does not yield this datum: http://docs.puppetlabs.com/puppet/3.7/reference/lang_functions.html http://docs.puppetlabs.com/guides/custom_functions.html It also reveals one of the limitations of testing functions w/rspec-puppet: Since the result of the function call does not go through the Puppet compiler itself but stays all within Ruby, results can be misleading. (The alternative, testing the results of the function call within a hosts example using either `:pre_condition` or `fixtures/manifests/site.pp` is non-obvious and not terribly well-documented.) I'll file bugs on the docs now. Wil -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMmm3r5_S-COV7HMQKyKTpt4wfmZB-XfHi6FXXQhJaq-QB4hwg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: WPUG: Reusable Puppet Modules - Development Testing (lecture)
Thanks. Interesting slides! Regards, Martijn Op zaterdag 14 maart 2015 01:32:29 UTC+1 schreef Krzysztof Suszyński: Hi, I'm pleased to publish slides for lecture: Reusable Puppet Modules - Development Testing that I've performed on WPUG (Warsaw Puppet User Group) on March 11th, 2015. http://slides.com/cardil/reusable-puppet-module-development-and-testing I hope at least some of you will find this presentation useful. Cheers. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b72ba53b-e106-43dc-8e97-7d606a315880%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
