Parimi V. wrote: > # /usr/local/ruby/bin/facter > /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > operatingsystemrelease.rb:79: private method `chomp' called for > nil:NilClass (NoMethodError) > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/resolution.rb:117:in `call' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/resolution.rb:117:in `value' > from /usr/local/ruby-1.8.7-p72/lib/ruby/1.8/timeout.rb:53:in > `timeout' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/resolution.rb:115:in `value' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/fact.rb:75:in `value' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/loader.rb:72:in `inject' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/fact.rb:71:in `each' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/fact.rb:71:in `inject' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/fact.rb:71:in `value' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/fact.rb:117:in `searching' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/fact.rb:67:in `value' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/collection.rb:104:in `to_hash' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/loader.rb:72:in `inject' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/collection.rb:103:in `each' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/collection.rb:103:in `inject' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/facter/ > util/collection.rb:103:in `to_hash' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/ > facter.rb:92:in `send' > from /usr/local/ruby-1.8.7-p72/lib/ruby/site_ruby/1.8/ > facter.rb:92:in `to_hash' > from /usr/local/ruby/bin/facter:121 > # >
I experienced the same problem. I guess this is because OpenSolaris isn't properly supported by facter yet? The previous version worked alright, but after adding the operatingsystemrelease fact on Solaris (#1555 on redmine) it broke on OpenSolaris. This is because the /etc/release file (where this fact gets it's value from) is formated differently on Solaris 10 than it is on OpenSolaris. I tried to fix this a while ago, and I accidentally started a thread on opensolaris-discuss [1], where I was told that using /etc/release in scripts is generally a bad idea because it may change without a notice. There is also some confusion as to what operatingsystemrelease should be set to on Solaris. I'd probably go for uname -r, which yields 5.10 on Solaris and 5.11 on OpenSolaris. But then it's the same as the kernelversion so not very useful... Another option would be to use the bi-weekly build numbers on OpenSolaris (e.g. snv_99). I'd love to hear some opinions on what this should be set to. Cheers, Andrew. [1] http://opensolaris.org/jive/message.jspa?messageID=299469 -- . __/_/_ w: http://darq.com/ . __/_/_ t: 020 7100 1447 . / / e: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
