Issue #17358 has been updated by eric sorenson. Status changed from Unreviewed to Closed Assignee set to Ben Ford
I would expect requiring gems from inside ruby code on any Puppet before the upcoming 3.1 to be fraught with peril. See #7316 for more info. If you can get a clean repro case feel free to re-open. ---------------------------------------- Bug #17358: Requiring a non-available gem in a plugin causes unrelated things to blow up https://projects.puppetlabs.com/issues/17358#change-77831 Author: Ben Ford Status: Closed Priority: Normal Assignee: Ben Ford Category: Target version: Affected Puppet version: 2.7.19 Keywords: Branch: I wrote a Hiera backend for a client. I wrote against PE, so i used ActiveSupport, forgetting that it's not installed on POSS. Immediately after adding it as a backend in my hiera.yaml, the metaphorical doody started flying. The backend obviously didn't work, but facts and other plugins also stopped working. Facter didn't even work from the command line unless I set FACTERLIB. And worse, there was absolutely no notice of the failed require in the output, even with --debug. Unfortunately, I cannot replicate this on my own install! -- 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.
