Issue #15634 has been updated by eric sorenson.
Hi Ryan, thanks for the report -- Can you help to provide a way to reproduce this? I'm wondering whether the problem is that the 'gem list' output is intermingling the list with the error on the same file descriptor, or whether it's our fault for not capturing stdin and stderr separately. I don't know how to generate the output you're seeing. ---------------------------------------- Bug #15634: Malformed gemspec prevents Gem provider from parsing output https://projects.puppetlabs.com/issues/15634#change-69174 Author: Ryan Conway Status: Unreviewed Priority: High Assignee: Category: Target version: Affected Puppet version: 2.7.14 Keywords: Branch: I've found that if you end up with a broken Ruby Gem on a system, for example, if a Gem has a malformed Gemspec, this is output at the top of the response from 'gem list', and then prevents the Gem provider for the Package type from successfully parsing the installed version of a gem it is managing. Puppet then assumes that the gem is absent, and installs it. This on its own isn't ideal, but the real trouble comes if you have other resources depending on the gem, as every catalog run will trigger a refresh of those dependents, which could cause more serious issues depending on what those resources do. Testing on 2.7.14, but I expect it will affect the latest too. Thanks, Ryan -- 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.
