Issue #14725 has been updated by Justin Honold.
How about throwing an error when a hash is requested and a shadow lib isn't present? IIRC, it simply does nothing, and doesn't report it (in verbose mode). ---------------------------------------- Bug #14725: Puppet daemon requires reload in order to detect newly-installed shadow libraries? https://projects.puppetlabs.com/issues/14725#change-64403 Author: Justin Honold Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: I manage a variety of Ubuntu and RHEL hosts using Puppet, presently installed via RubyGems. I recently saw fit to manage a password hash using Puppet, which didn't work as expected. The 'user' type documentation informed me that I needed ruby-libshadow installed. I added that to my setups on both sides, tested with a 'puppetd -tv' on both sides to confirm function, and deployed site-wide. It apparently did not work on any systems with an already-running 'puppetd' (daemon mode), and I'm surmising that it's because the library was checked at daemon initialization, as opposed to the point of execution. Is that the case? If so, is there anything that can be done about that? On one hand I don't like excessive lookups, but on the other it is no fun to restart all of my daemons. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
