Jira (FACT-3093) Facter fails to resolve custom/environment facts in some circumstances

unread,

Nov 10, 2021, 5:09:02 AM11/10/21

to puppe...@googlegroups.com

Adam Tkac created an issue

Hello facter upstream,

when upgrading facter from 4.0.51 to the latest (4.2.5), I found that under certain circumstances, facter fails to resolve custom/environment facts.

Reproducer:

$ cat facter/1.rb

Facter.add(:ec2data_type) do

  setcode do

    "cl_ftp"

end

end

$ cat facter/2.rb

if not Facter.value(:nonexistant_fact)

    Facter.add(:nonexistant_fact) do

      setcode do

        "asd"

end

end

end

# FACTER_EC2DATA_TYPE=cl_ftp FACTERLIB=$(pwd)/facter facter ec2data_type

<nothing is returned>

Feel free to ask me if you need more information.

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)

unread,

Nov 15, 2021, 9:14:03 AM11/15/21

to puppe...@googlegroups.com

Ciprian Badescu commented on

Adam Tkac, calling Facter.value outside setcode block is causing this kind of issues.

The same effect can be obtained using confine }}and {{has_weight statements and will be correctly solved by Facter. Can you try that?

unread,

Dec 2, 2021, 1:29:02 PM12/2/21

to puppe...@googlegroups.com

Ciprian Badescu commented on

Adam Tkac, thank you for feedback!

Reply all

Reply to author

Forward