New Fact not getting loaded into PuppetDB

[yasin-amadmia-mck]

Team, so we have a situation whereby a particular custom fact that was newly added to the node does'nt seem to get stored in the PuppetDB Database.
When i do facter -p is_lvm on the agent/node, I get it printed on screen true which is expected. However, when I curl the /facts endpoint for PuppetDB, and query it, it does'nt return anything. I also checked the DB manually and it is not present.
In this instance, the puppertserver and the node where I am running puppent agent -t --environment=some-env is same.
One interesting line of error we see is this

Debug: HTTP POST https://puppetserver:8140/puppet/v3/catalog/<agent>?environment=<some-env> returned 500 Server Error
Debug: Caching connection for https://<agent>:8140
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Unknown variable: '::is_lvm'. (file: file.pp, line: xx column: x) on node <node>
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

now that ::is_lvm is the custom fact that we adding.

lib/facter/lvm.rb

Facter.add(:is_lvm) do
  setcode do
    if File.writable?('<some-path>')
      true
    else
      false
    end
  end
end

It is worth noting that on another node, the same puppet agent run -t --environment=<some-environment> completes successfully when applying same classes. For this node, the puppetserver is also the same. Basically nodes (failing and working) has same puppetserver. I also confirmed via curl /facts that for this node, the custom fact is_lvm is present in puppetDB.

PS: I also cleared certificate of the node where it is failing but same issue.

on Agent delete <puppetdir>/ssl/

on puppetca, 

puppetserver ca clean --certname <node>