Issue #3298 has been updated by Jonathan Booth.
This is causing me troubles as well. I can see <62k reports getting in, and >70k reports not, I don't know if 64k is the exact break-point for me or not. I hacked around it with a rake db:reset then 'ALTER TABLE ...' to turn text to a mediumtext field. Googling seems to indicate that changing the 'report' record to have a ':limit=>16.megabytes' (however one does that properly in rails) would fix it, at least for some version of activerecord. I haven't tried that (successfully) though. Alternately, push it up above 16.megabytes just in case that isn't enough into the 1.gigabytes to get the field as big as it could be -- a fairly simple manifest for me is cracking the 110k-report-yaml range (it sets up a few user accounts, ssh, ntp, apache, passenger, puppetmaster, and dashboard and not much more) and that's still fairly basic. ---------------------------------------- Bug #3298: reports.report datatype leads to data loss http://projects.puppetlabs.com/issues/3298 Author: Richard Clamp Status: Needs design decision Priority: Normal Assigned to: Category: Target version: Keywords: Branch: Affected URL: reports.report is currently a TEXT type, which can lead to truncation of the report after the first 64k. This leads to a few odd problems, as most of the times we've seen it in our install it pushes the metrics data off the end. -- 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.
