Issue #2374 has been updated by Andrew Otto.
I'm pretty sure this is not a duplicate of #1365. That bug is same symptom, but specifically refers to multiple custom facts defined in the same file. This is way worse. I can't even use the standard facts that come with facter. Running <pre> facter processorcount </pre> doesn't return anything. However, <pre> facter | grep processorcount </pre> does. I'd really like to upgrade puppet and facter, but many of our monitoring scripts are using facter, and if it breaks I can't upgrade. ---------------------------------------- Bug #2374: Facter CLI does not work when naming variables http://projects.reductivelabs.com/issues/2374 Author: Andrew Otto Status: Duplicate Priority: High Assigned to: Category: Target version: Complexity: Unknown Keywords: facter variable command line CLI Many, but not all, of the facter variables do not work when naming them on the command line. This only happens with newer versions of facter. I have version 1.3.8 running on some machines, and have no problem. [o...@web1 ~]$ facter --version 1.5.5 [o...@web1 ~]$ puppet --version 0.24.8 [o...@web1 ~]$ uname -a Linux web1 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux [o...@web1 ~]$ cat /etc/issue CentOS release 5.3 (Final) Kernel \r on an \m [o...@web1 ~]$ facter | awk '{print $1;}' | xargs facter architecture => x86_64 domain => couchsurfing.com facterversion => 1.5.5 fqdn => web1.couchsurfing.com hardwareisa => x86_64 hardwaremodel => x86_64 hostname => web1 id => otto interfaces => eth0,eth0_1,eth1,sit0 ipaddress => 10.0.2.142 ipaddress_eth0 => 10.0.2.142 ipaddress_eth0_1 => 192.168.0.41 is_virtual => kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.18-128.1.6.el5 kernelversion => 2.6.18 lsbdistcodename => Final lsbdistdescription => CentOS release 5.3 (Final) lsbdistid => CentOS lsbdistrelease => 5.3 lsbmajdistrelease => 5 lsbrelease => :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch macaddress => 00:30:48:61:2C:F4 macaddress_eth0 => 00:30:48:61:2C:F4 macaddress_eth0_1 => 00:30:48:61:2C:F4 macaddress_eth1 => 00:30:48:61:2C:F5 memoryfree => memorysize => netmask => 255.255.255.224 netmask_eth0 => 255.255.255.224 netmask_eth0_1 => 255.255.255.0 network_eth0 => network_eth0_1 => operatingsystem => CentOS operatingsystemrelease => 5.3 physicalprocessorcount => 2 processor0 => processor1 => processor2 => processor3 => processor4 => processor5 => processor6 => processor7 => processorcount => ps => ps -ef puppetversion => 0.24.8 rubysitedir => /usr/lib/ruby/site_ruby/1.8 rubyversion => 1.8.5 selinux => false sshdsakey => sshrsakey => swapfree => swapsize => timezone => UTC uniqueid => a8c02900 uptime => 36 min uptime_days => 0 uptime_hours => 0 uptime_seconds => 2188 virtual => physical -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
