Issue #15350 has been updated by Ryan Coleman.
Upon request, here's the full yaml output for reference: <pre> ➜ puppet envpuppet facter --yaml --- macaddress_fw0: a4:b1:97:ff:fe:75 domain: puppetlabs.lan network_vboxnet0: 172.21.0.0 sp_l2_cache_core: 256 KB sp_boot_volume: PuppetHD sp_smc_version_system: 1.68f98 productname: "MacBookPro8,1" osfamily: &id004 Darwin netmask_vboxnet0: 255.255.255.0 macosx_productversion_minor: "4" macosx_buildversion: 11E53 virtual: physical netmask_lo0: 255.0.0.0 swapsize: 4096.00M ipaddress_vboxnet0: 172.21.0.1 macaddress_en2: 02:50:f2:00:00:01 sp_uptime: up 27:23:16:39 memorytotal: &id001 8.00 GB ipaddress6: fd0b:a68e:753:d85b:3e07:54ff:fe2c:aa9b path: /Users/ryan/software/puppet/sbin:/Users/ryan/software/puppet/bin:/Users/ryan/software/facter/bin:/Users/ryan/software/puppet-scaffold/bin:/Users/ryan/software/puppet-module-tool/bin:/Users/ryan/bin:/Users/ryan/puppetlabs/github/puppet/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin macosx_productname: Mac OS X sp_serial_number: C02GK1JJDV14 memorysize: *id001 sp_number_processors: "2" sp_packages: "1" uptime_hours: 671 macaddress: b8:8d:12:2e:82:d2 architecture: &id002 x86_64 sp_secure_vm: secure_vm_enabled is_virtual: "false" macaddress_p2p0: 0a:8d:12:2e:82:d2 kernelversion: 11.4.0 sp_local_host_name: puppetlabs07 sp_platform_uuid: 92DBF57E-F3C0-5191-8A04-0D0C834DCA48 netmask: 255.255.254.0 hardwareisa: i386 swapfree: 1170.16M sp_os_version: Mac OS X 10.7.4 (11E53) sp_mmm_entry: MMM_stateMMM_enabled macosx_productversion: 10.7.4 puppetversion: 2.7.16 uptime_days: 27 ps: ps auxwww macaddress_vboxnet0: 0a:00:27:00:00:00 sp_user_name: Ryan Coleman (ryan) sp_machine_name: MacBook Pro hardwaremodel: *id002 uptime_seconds: 2416570 macaddress_en1: b8:8d:12:2e:82:d2 ipaddress_en1: 192.168.100.217 hostname: puppetlabs07 network_en1: 192.168.100.0 memoryfree: 54.40 MB sp_boot_rom_version: MBP81.0047.B27 operatingsystemrelease: &id003 11.4.0 kernelrelease: *id003 ipaddress_lo0: 127.0.0.1 interfaces: "lo0,gif0,stf0,en0,fw0,en1,p2p0,en2,vboxnet0,utun0" swapencrypted: true network_lo0: 127.0.0.0 sp_kernel_version: Darwin 11.4.0 macosx_productversion_major: "10.7" facterversion: 1.6.7 uptime: 27 days timezone: PDT sp_physical_memory: 8 GB fqdn: puppetlabs07.puppetlabs.lan sp_l3_cache: 4 MB sp_current_processor_speed: 2.8 GHz rubyversion: 1.8.7 kernel: *id004 sp_boot_mode: normal_boot sp_machine_model: "MacBookPro8,1" sp_64bit_kernel_and_kexts: "yes" processorcount: "4" kernelmajversion: "11.4" macaddress_en0: 3c:07:54:2c:aa:9b operatingsystem: *id004 ipaddress: 192.168.100.217 sp_cpu_type: Intel Core i7 id: ryan netmask_en1: 255.255.254.0 </pre> ---------------------------------------- Bug #15350: Fact, when output as yaml produce inconsistent values that look like *id00X https://projects.puppetlabs.com/issues/15350#change-66245 Author: Ryan Coleman Status: Rejected Priority: Normal Assignee: Category: Target version: Keywords: facter amazon ec2 Branch: Affected Facter version: 1.6.7 [root@ip-10-161-19-135 puppet-enterprise]# facter --version 1.6.7 [root@ip-10-161-19-135 puppet-enterprise]# cat /etc/system-release Amazon Linux AMI release 2011.09 I initially discovered this problem with osfamily when output as yaml but it looks like many other facts return garbage, inconsistently. <pre> [root@ip-10-161-19-135 puppet-enterprise]# facter --yaml | grep *id memorysize: *id001 kernelrelease: *id002 osfamily: *id003 [root@ip-10-161-19-135 puppet-enterprise]# facter --yaml | grep *id osfamily: *id001 operatingsystemrelease: *id002 memorysize: *id003 [root@ip-10-161-19-135 puppet-enterprise]# facter --yaml | grep *id osfamily: *id001 memorysize: *id002 kernelrelease: *id003 [root@ip-10-161-19-135 puppet-enterprise]# facter --yaml | grep *id kernel: *id001 memorysize: *id002 operatingsystemrelease: *id003 </pre> To Reproduce: * Create an EC2 instance with the 2011.09 Amazon Linux (I used ami-951945d0) * Install PE 2.5.1 ( I installed Agent only role, just wanted Facter) * Execute `facter --yaml` and look for facts whose values start with *id Addendum: While I initially discovered this on Amazon, I can reproduce when running Facter 1.6.7 from source on my MBP (10.7.3). Simply execute facter --yaml -- 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.
