Bug 1571973

Description of problem: 


Version-Release number of selected component (if applicable): 6.2.10

(Customer version 6.2.10, local reproducer version 6.2.12 and also 6.3.0 with puppet 3. )

How reproducible:  Always 


Steps to Reproduce:
1.  Create a rb file to report custom fact on a host registered with Satellite:

# cat /var/lib/puppet/facts/custom_fact.rb
Facter.add(:custom_fact) do
  setcode do
     Facter::Util::Resolution.exec('ls -1 /opt/acme/ | egrep \'dir\' | sort | tr \'\n\' \',\' | sed -e \'s/,$//g\'')
  end
end


2.  Create a directory under /opt/acme/

# mkdir -p /opt/acme/dir1

3.  Check the facter output on the host

[root@host72 ~]# facter -p | grep custom_fact
custom_fact => dir1

4. Run puppet agent to report the custom fact.

5. Check the hammer host facts output: (or the facts from the satellite webui for the same host)

[root@satellite ~]# hammer host facts --name host72.example.com | grep custom_fact
custom_fact                          | dir1  


6.  Remove the directory from the host

# rm -rf /opt/acme/dir1

7. Check facter output on the host. It should now report a null value.

[root@host72 ~]# facter -p | grep custom
custom_fact => 

8. Run puppet agent to report the custom fact


9. Check the hammer host facts output: (or the facts from the satellite webui for the same host)

[root@satellite ~]# hammer host facts --name host72.example.com | grep custom_fact
[root@satellite ~]


So the custom fact key:value gets completely discarded from the Satellite end.


Actual results:

custom facts get discarded completely 

Expected results:

Satellite should indicate that custom fact has a null value. Something like:


[root@satellite ~]# hammer host facts --name host72.example.com | grep custom_fact
custom_fact  |   null

Additional info: