Mr. Bollinger, you sir are the winner! I just wish I had a prize :) Not so much a ruby version issue, but your point about the to_a method being removed got me looking into all the facts we've got rolling around, and there just happens to be one fact that uses this call. So I'm off to go repair that, and much appreciate that hint in the right direction! Someone else mentioned getting rid of custom facts, but it didn't lead me to look at a ruby version issue.
Thanks a bunch to all! On Tuesday, March 3, 2015 at 9:14:12 AM UTC-5, jcbollinger wrote: > > > > On Wednesday, February 25, 2015 at 3:43:18 PM UTC-6, smalderma wrote: >> >> Hi, >> >> I'm working on enabling our environment to support EL7 Linux systems. We >> mostly run OracleLinux, but also have CentOS and RHEL. >> >> I've got a CentOS 6 PuppetMaster running Foreman 1.7.2, Puppet 3.6.2 >> (from puppetlabs repo) doing my provisioning. I have provisioning working >> for both Oracle Linux 7 and CentOS 7. The systems kickstart, install >> puppet inform Foreman that they're done building and reboot. >> >> After the reboots, the puppet agent on both systems produce this: >> >> Failed to apply catalog: Could not retrieve local facts: undefined method >>> `to_a' for "ens33":String >>> >> and >> >>> Failed to apply catalog: Could not retrieve local facts: undefined >>> method `to_a' for "ens192":String >>> >> >> I'm at something of a loss as to why. While I'm new at the EL7 release, >> I know there have been issues with facter requiring net-tools to be >> installed....and it is. Both agents are installed out of EPEL 7 at version >> 3.6.2 with facter 2.2. Would anyone happen to have an idea on this? >> > > > In Ruby 1.8.7, the String class has a 'to_a' method. In Ruby 1.9 and > later, it does not. I am inclined to think, therefore, that the messages > mean your Puppet and the Ruby it is running on are mismatched. > > Puppet claims compatibility with Ruby 1.8.7, Ruby 1.9.3, and Ruby 2.0.x > (and it half claims to support 2.1.x). If you are using a different Ruby > then switch to one of those. If you have more than one Ruby installed, > then look into the possibility that Puppet is running on a different one > than you intend, or worse: that it is somehow running on one Ruby, but > pulling some components from another. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e40aec20-ab2d-48ed-afe8-7faf14181e07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
