On Thu, May 31, 2012 at 6:07 PM, Brice Figureau <[email protected]> wrote:
> I'll run a test over the week-end to see if I can reproduce the issue > with 2.7.14. It's possible something changed in the puppet codebase and > puppet-load doesn't properly encode the facts it sends to the master, > which in turn doesn't get unserialized as they should. Just as a hunch, I wonder whether, given the problems I had getting compatible versions of various gems installed it may be a problem there (I'm on an air-gapped environment, so had to download, transfer and install the individual .gem files). In case it's useful, here's the output of 'gem list': activemodel (3.0.12) activerecord (3.0.12) activesupport (3.0.12) addressable (2.2.8) arel (2.0.10) builder (3.0.0, 2.1.2) cookiejar (0.3.0) daemon_controller (0.2.5) em-http-request (1.0.2) em-socksify (0.2.0) eventmachine (1.0.0.beta.4) fastthread (1.0.7) http_parser.rb (0.5.3) i18n (0.6.0, 0.5.0) json (1.4.3) mime-types (1.16) multi_json (1.3.5) mysql (2.8.1) passenger (3.0.12) rack (1.1.0) rake (0.8.7) rest-client (1.6.1) sqlite3-ruby (1.2.4) tzinfo (0.3.33) Cheers, Matt. -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
