Jira (PUP-3073) Error message "Could not send report": appear when puppet client is pulling config from puppet master

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Error message "Could not send report": appear when puppet client is pulling config from puppet master The regexp in question is in Puppet's zaml.rb in a method to_zaml that is added to String. Thus, this logic is executed for every string when it is converted to YAML. Thus, if this was a general problem, we would see failures any time something was serialized to yaml. The primary suspicion is therefore the Regexp implementation itself (in the Ruby runtime). Please check that this is not running on an older 1.8.7 ( say older than p370 or so). There could also be issues with the string itself that is being matched, and that this string causes the regexp matcher to fail. That is something to look at if the version of the Ruby runtime is one that is known to work ok in general. (Looking at the string and digging in further requires debuggin/instrumentation in zaml.rb to examine the string being matched against). Add Comment   Puppet / PUP-3073 Error message "Could not send report": appear when puppet client is pulling config from puppet master Please find attached log files for more details {code} Error message "Could not send report": appear when puppet client is pulling config from puppet master with vlan configuration i.e..vlan count greater than 460 and less than 700. root> show vlans Routing instance VLAN name Tag Interfaces default-switch ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.