Jira (FACT-2799) Missing output when resolving custom facts with Facter 4

36 views
Skip to first unread message

Luchian Nemes (Jira)

unread,
Sep 15, 2020, 11:56:03 AM9/15/20
to puppe...@googlegroups.com
Luchian Nemes created an issue
 
Facter / Bug FACT-2799
Missing output when resolving custom facts with Facter 4
Issue Type: Bug Bug
Assignee: Unassigned
Created: 2020/09/15 8:55 AM
Environment:

How to set the environment:

Install Puppet Agent >= 7 (since it comes with Facter 4)

wget http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb
dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb

Make the new binaries easily accesible
echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc
source ~/.bashrc

Check Puppet version
puppet --version

Check Facter version
facter --version

Install Puppet Server

wget http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb
dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -y

Check if it installed correctly (make sure you've run above commands correctly)
puppetserver --version

Start the Puppet Server service
service puppetserver start

Configure Puppet Server address
puppet config set server $(facter fqdn)

Make sure Puppet Agent and Puppet Server communicate accordingly
puppet agent -t

Install this module that contains a custom fact
puppet module install eputnam-i18ndemo

You can see the content of this custom fact
cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb
Facter.add('i18ndemo_fact') do
setcode do
raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo')
end
end

How to reproduce the issue:

With the module above/custom fact in place, do the first 'puppet agent -t' run:

puppet agent -t

Do the second run and now observe the expected raise:

puppet agent -t

How to reset environment to reproduce the issue again:

rm -rf /opt/puppetlabs/puppet/cache/lib/facter/
Priority: Normal Normal
Reporter: Luchian Nemes

Puppet Version: 7.0.0
Puppet Server Version: 7.0.0
OS Name/Version: Ubuntu 16.04

 

The first 'puppet agent -t' run seems to not show any signs of custom facts being resolved. This only happens if:

  • this is the run when they are synced from server
  • Facter 4.x is being used (Facter 3 works as expected)
  • agent node has Ubuntu 16.04 as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those)

 

Initial finding of issue:
It was spotted in the first step of this Puppet acceptance test: https://github.com/puppetlabs/puppet/blob/main/acceptance/tests/i18n/modules/puppet_agent.rb#L64

This test is needed forPUP-10610.

 
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Luchian Nemes (Jira)

unread,
Sep 15, 2020, 11:57:04 AM9/15/20
to puppe...@googlegroups.com
Luchian Nemes updated an issue
Change By: Luchian Nemes

Luchian Nemes (Jira)

unread,
Sep 15, 2020, 11:57:04 AM9/15/20
to puppe...@googlegroups.com
Luchian Nemes updated an issue
Change By: Luchian Nemes
Acceptance Criteria: Here is a barebones Puppet acceptance test. Behaviour on other operating systems, with Facter3/Facter4 and the possible fix can be quickly checked using this.

{code:ruby}
test_name 'Untitled' do

  tag 'audit:high',
      'audit:acceptance'

  require 'puppet/acceptance/i18ndemo_utils'
  extend Puppet::Acceptance::I18nDemoUtils

  step 'Install the i18ndemo module on master' do
    install_i18n_demo_module(master)
  end

  agents.each do |agent|
    teardown do
      vardir = on(agent, puppet('config print vardir')).stdout.chomp
      agent.rm_rf("#{vardir}/lib/facter")
    end

    step "Run 'puppet agent -t' and expect greatness" do
      on(agent, puppet("agent -t")) do |result|
        assert_match(/i18ndemo_fact\: this is a raise from a custom fact from eputnam-i18ndemo/, result.stderr)
      end
    end
  end
end
{code}

Luchian Nemes (Jira)

unread,
Sep 15, 2020, 12:12:04 PM9/15/20
to puppe...@googlegroups.com
Luchian Nemes updated an issue
*Puppet Version: 7.0.0*
*Puppet Server Version: 7.0.0*
*OS Name/Version: Ubuntu 16.04*

  

 The first * 'puppet agent -t' * run seems to not show any signs of custom facts being resolved. This only happens if:
- this is the run when they are synced from server
- * Facter 4.x * is being used (Facter 3 works as expected)
- agent node has * Ubuntu 16.04 * as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those)

 h2.  
 h2. How to set the environment
h4. Install Puppet Agent >= 7 (since it comes with Facter 4)

{color:#c1c7d0}>{color} wget [http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb]
{color:#c1c7d0}>{color} dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb
h4. Make the new binaries easily accesible

{color:#c1c7d0}>{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc
{color:#c1c7d0}>{color} source ~/.bashrc
h4. Check Puppet version

{color:#c1c7d0}>{color} puppet --version

 
{panel}
7.0.0
{panel}
 
h4. Check Facter version

{color:#c1c7d0}>{color} facter --version

 
{panel}
4.0.37
{panel}
 
h4. Install Puppet Server

{color:#c1c7d0}>{color} wget [http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb]
{color:#c1c7d0}>{color} dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -y
h4. Check if it installed correctly (make sure you've run above commands correctly)

{color:#c1c7d0}>{color} puppetserver --version

 
{panel}
puppetserver version: 7.0.0.SNAPSHOT.2020.09.11T0333
{panel}
 
h4. Start the Puppet Server service

{color:#c1c7d0}>{color} service puppetserver start
h4. Configure Puppet Server address

{color:#c1c7d0}>{color} puppet config set server $(facter fqdn)
h4. Make sure Puppet Agent and Puppet Server communicate accordingly

{color:#c1c7d0}>{color} puppet agent -t
h4. Install this module that contains a custom fact

{color:#c1c7d0}>{color} puppet module install eputnam-i18ndemo
h4. You can see the content of this custom fact

{color:#c1c7d0}>{color} cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb
{panel}

Facter.add('i18ndemo_fact') do
    setcode do
       {color:#de350b} raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo'){color}
    end
end
{panel}
h2.  
h2. How to reproduce the issue
h4. With the module above/custom fact in place, do the first 'puppet agent -t' run:

{color:#c1c7d0}>{color} puppet agent -t
{panel}
*{color:#00875a}Info: Using configured environment 'production'{color}*
*{color:#00875a}Info: Retrieving pluginfacts{color}*
*{color:#00875a}Info: Retrieving plugin{color}*
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created
.

.

.
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/util/puppet_settings.rb]/ensure: defined content as '\{sha256}af86574985faba7b25893444917da5197f00bbb39182f7a56123cca6ee71e0f4'
*{color:#00875a}Info: Retrieving locales{color}*
{color:#ffab00} *Info: Loading facts*{color}
{color:#ffab00} *Info: Caching catalog for fqdn*{color}
*{color:#00875a}Info: Applying configuration version '1600186054'{color}*
Notice: Applied catalog in 0.02 seconds

 
{panel}
 
h4. Do the second run and now observe the expected raise:

{color:#c1c7d0}>{color} puppet agent -t
{panel}


*{color:#00875a}Info: Using configured environment 'production'{color}*
*{color:#00875a}Info: Retrieving pluginfacts{color}*
*{color:#00875a}Info: Retrieving plugin{color}*
*{color:#00875a}Info: Retrieving locales{color}*
{color:#ffab00}*Info: Loading facts*{color}
*{color:#de350b}Error: Facter: Error while resolving custom fact fact='i18ndemo_fact', resolution='<anonymous>': i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo{color}*
{color:#ffab00}*Info: Caching catalog for fqdn*{color}
*{color:#00875a}Info: Applying configuration version '1600186185'{color}*
{panel}
h2.  
h2. How to reset environment to reproduce the issue again
h4. Just remove facter cache:

{color:#c1c7d0}>{color} rm -rf /opt/puppetlabs/puppet/cache/lib/facter/
h2.  
h2. Initial finding of issue :

It was spotted in the first step of this Puppet acceptance test: [https://github.com/puppetlabs/puppet/blob/main/acceptance/tests/i18n/modules/puppet_agent.rb#L64]

This test is needed forPUP for PUP -10610.

 

Luchian Nemes (Jira)

unread,
Sep 15, 2020, 12:14:05 PM9/15/20
to puppe...@googlegroups.com
Luchian Nemes updated an issue
*Puppet Version: 7.0.0*
*Puppet Server Version: 7.0.0*
*OS Name/Version: Ubuntu 16.04*

The first *'puppet agent -t'* run seems to not show any signs of custom facts being resolved. This only happens if:
- this is the run when they are synced from server
- *Facter 4.x* is being used (Facter 3 works as expected)
- agent node has *Ubuntu 16.04* as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those)
This test is needed for PUP-10610.

 

Luchian Nemes (Jira)

unread,
Sep 15, 2020, 12:15:05 PM9/15/20
to puppe...@googlegroups.com
        raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo')

Luchian Nemes (Jira)

unread,
Sep 15, 2020, 12:19:03 PM9/15/20
to puppe...@googlegroups.com
Luchian Nemes updated an issue
*Puppet Version: 7.0.0*
*Puppet Server Version: 7.0.0*
*OS Name/Version: Ubuntu 16.04*

 

The first *'puppet agent -t'* run seems to not show any signs of custom facts being resolved. This only happens if:
- this is the run when they are synced from server
- *Facter 4.x* is being used (Facter 3 works as expected)
- agent node has *Ubuntu 16.04* as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those)

 h2.  
h2. How to set the environment
h4. Install Puppet Agent >= 7 (since it comes with Facter 4) :


{color:# c1c7d0 57d9a3 } > ➜ {color} wget [http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb]
{color:# c1c7d0 57d9a3 } > ➜ {color} dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb
h4. Make the new binaries easily accesible accessible:

{color:# c1c7d0 57d9a3 } > ➜ {color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc
{color:# c1c7d0 57d9a3 } > ➜ {color} source ~/.bashrc
h4. Check Puppet version

{color:# c1c7d0 57d9a3 } > ➜ {color} puppet --version

{panel}
7.0.0
{panel}
h4. Check Facter version
:

{color:# c1c7d0 57d9a3 } > ➜ {color} facter --version

{panel}
4.0.37
{panel}
h4. Install Puppet Server
:

{color:# c1c7d0 57d9a3 } > ➜ {color} wget [http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb]
{color:# c1c7d0 57d9a3 } > ➜ {color} dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -y

h4. Check if it installed correctly (make sure you've run above commands correctly)

{color:# c1c7d0 57d9a3 } > ➜ {color} puppetserver --version

{panel}
puppetserver version: 7.0.0.SNAPSHOT.2020.09.11T0333
{panel}
h4. Start the Puppet Server service

{color:# c1c7d0 57d9a3 } > ➜ {color} service puppetserver start

h4. Configure Puppet Server address

{color:# c1c7d0 57d9a3 } > ➜ {color} puppet config set server $(facter fqdn)

h4. Make sure Puppet Agent and Puppet Server communicate accordingly

{color:# c1c7d0 57d9a3 } > ➜ {color} puppet agent -t

h4. Install this module that contains a custom fact

{color:# c1c7d0 57d9a3 } > ➜ {color} puppet module install eputnam-i18ndemo

h4. You can see the content of this custom fact

{color:# c1c7d0 57d9a3 } > ➜ {color} cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb

{panel}
Facter.add('i18ndemo_fact') do
    setcode do
        raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo')
    end
end
{panel}
h2.  

h2. How to reproduce the issue
h4. With the module above/custom fact in place, do the first 'puppet agent -t' run:

{color:# c1c7d0 57d9a3 } > ➜ {color} puppet agent -t

{panel}
*{color:#00875a}Info: Using configured environment 'production'{color}*
*{color:#00875a}Info: Retrieving pluginfacts{color}*
*{color:#00875a}Info: Retrieving plugin{color}*
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created
.

.

.
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/util/puppet_settings.rb]/ensure: defined content as '\{sha256}af86574985faba7b25893444917da5197f00bbb39182f7a56123cca6ee71e0f4'
*{color:#00875a}Info: Retrieving locales{color}*
{color:#ffab00} *Info: Loading facts*{color}
{color:#ffab00} *Info: Caching catalog for fqdn*{color}
*{color:#00875a}Info: Applying configuration version '1600186054'{color}*
Notice: Applied catalog in 0.02 seconds

 
{panel}
h4. Do the second run and now observe the expected raise:

{color:# c1c7d0 57d9a3 } > ➜ {color} puppet agent -t

{panel}
*{color:#00875a}Info: Using configured environment 'production'{color}*
*{color:#00875a}Info: Retrieving pluginfacts{color}*
*{color:#00875a}Info: Retrieving plugin{color}*
*{color:#00875a}Info: Retrieving locales{color}*
{color:#ffab00}*Info: Loading facts*{color}
*{color:#de350b}Error: Facter: Error while resolving custom fact fact='i18ndemo_fact', resolution='<anonymous>': i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo{color}*
{color:#ffab00}*Info: Caching catalog for fqdn*{color}
*{color:#00875a}Info: Applying configuration version '1600186185'{color}*
{panel}
h2.  

h2. How to reset environment to reproduce the issue again
h4. Just remove facter cache:

{color:# c1c7d0 57d9a3 } > ➜ {color} rm -rf /opt/puppetlabs/puppet/cache/lib/facter/
h2.
 
h2. Initial finding of issue

It was spotted in the first step of this Puppet acceptance test: [https://github.com/puppetlabs/puppet/blob/main/acceptance/tests/i18n/modules/puppet_agent.rb#L64]

This test is needed for PUP-10610.

 

Luchian Nemes (Jira)

unread,
Sep 15, 2020, 12:23:04 PM9/15/20
to puppe...@googlegroups.com
Luchian Nemes updated an issue
*Puppet Version: 7.0.0*
*Puppet Server Version: 7.0.0*
*OS Name/Version: Ubuntu 16.04*

 

The first *'puppet agent -t'* run seems to not show any signs of custom facts being resolved. This only happens if:
- this is the run when they are synced from server
- *Facter 4.x* is being used (Facter 3 works as expected)
- agent node has *Ubuntu 16.04* as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those)

 
h2. How to set the environment
h4. Install Puppet Agent >= 7 (since it comes with Facter 4):

{color:#57d9a3}➜{color} wget [http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb]
{color:#57d9a3}➜{color} dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb
h4. Make the new binaries easily accessible:

{color:#57d9a3}➜{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc
{color:#57d9a3}➜{color} source ~/.bashrc
h4. Check Puppet version :

{color:#57d9a3}➜{color} puppet --version

{panel}
7.0.0
{panel}
h4. Check Facter version:

{color:#57d9a3}➜{color} facter --version

{panel}
4.0.37
{panel}
h4. Install Puppet Server:

{color:#57d9a3}➜{color} wget [http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb]
{color:#57d9a3}➜{color} dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -y

h4. Check if it installed correctly (make sure you've run above commands correctly)
:

{color:#57d9a3}➜{color} puppetserver --version

{panel}
puppetserver version: 7.0.0.SNAPSHOT.2020.09.11T0333
{panel}
h4. Start the Puppet Server service
:

{color:#57d9a3}➜{color} service puppetserver start

h4. Configure Puppet Server address
:

{color:#57d9a3}➜{color} puppet config set server $(facter fqdn)

h4. Make sure Puppet Agent and Puppet Server communicate accordingly
:

{color:#57d9a3}➜{color} puppet agent -t

h4. Install this module that contains a custom fact
:

{color:#57d9a3}➜{color} puppet module install eputnam-i18ndemo

h4. You can see the content of this custom fact
:

{color:#57d9a3}➜{color} cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb

{panel}
Facter.add('i18ndemo_fact') do
    setcode do
{color:#de350b}         raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') {color}
    end
end
{panel}

 
h2. How to reproduce the issue
h4. With the module above/custom fact in place, do the first 'puppet agent -t' run:

{color:#57d9a3}➜{color} puppet agent -t

{panel}
*{color:#00875a}Info: Using configured environment 'production'{color}*
*{color:#00875a}Info: Retrieving pluginfacts{color}*
*{color:#00875a}Info: Retrieving plugin{color}*
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created
.

.

.
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/util/puppet_settings.rb]/ensure: defined content as '\{sha256}af86574985faba7b25893444917da5197f00bbb39182f7a56123cca6ee71e0f4'
*{color:#00875a}Info: Retrieving locales{color}*
{color:#ffab00} *Info: Loading facts*{color}
{color:#ffab00} *Info: Caching catalog for fqdn*{color}
*{color:#00875a}Info: Applying configuration version '1600186054'{color}*
Notice: Applied catalog in 0.02 seconds

 
{panel}
h4. Do the second run and now observe the expected raise:

{color:#57d9a3}➜{color} puppet agent -t

{panel}
*{color:#00875a}Info: Using configured environment 'production'{color}*
*{color:#00875a}Info: Retrieving pluginfacts{color}*
*{color:#00875a}Info: Retrieving plugin{color}*
*{color:#00875a}Info: Retrieving locales{color}*
{color:#ffab00}*Info: Loading facts*{color}
*{color:#de350b}Error: Facter: Error while resolving custom fact fact='i18ndemo_fact', resolution='<anonymous>': i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo{color}*
{color:#ffab00}*Info: Caching catalog for fqdn*{color}
*{color:#00875a}Info: Applying configuration version '1600186185'{color}*
{panel}
 
h2. How to reset environment to reproduce the issue again
h4. Just remove facter cache:

{color:#57d9a3}➜{color} rm -rf /opt/puppetlabs/puppet/cache/lib/facter/


 
h2. Initial finding of issue

It was spotted in the first step of this Puppet acceptance test: [https://github.com/puppetlabs/puppet/blob/main/acceptance/tests/i18n/modules/puppet_agent.rb#L64]

This test is needed for PUP-10610.

 

Mihai Buzgau (Jira)

unread,
Sep 16, 2020, 9:18:03 AM9/16/20
to puppe...@googlegroups.com
Mihai Buzgau updated an issue
Change By: Mihai Buzgau
Sub-team: ghost

Mihai Buzgau (Jira)

unread,
Sep 16, 2020, 9:18:04 AM9/16/20
to puppe...@googlegroups.com
Mihai Buzgau updated an issue
Change By: Mihai Buzgau
Team: Night's Watch

Mihai Buzgau (Jira)

unread,
Sep 16, 2020, 9:18:04 AM9/16/20
to puppe...@googlegroups.com
Mihai Buzgau updated an issue
Change By: Mihai Buzgau
Sprint: PR - Triage ready for triage

Bogdan Irimie (Jira)

unread,
Sep 16, 2020, 9:41:04 AM9/16/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ready for triage ghost-23.09

Bogdan Irimie (Jira)

unread,
Sep 16, 2020, 9:41:05 AM9/16/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Story Points: 3

Florin Dragos (Jira)

unread,
Sep 22, 2020, 5:28:04 AM9/22/20
to puppe...@googlegroups.com
Florin Dragos assigned an issue to Florin Dragos
Change By: Florin Dragos
Assignee: Florin Dragos

Bogdan Irimie (Jira)

unread,
Sep 23, 2020, 9:11:04 AM9/23/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ghost-23.09 , ready for triage 2

Bogdan Irimie (Jira)

unread,
Sep 25, 2020, 10:55:04 AM9/25/20
to puppe...@googlegroups.com
Bogdan Irimie commented on Bug FACT-2799
 
Re: Missing output when resolving custom facts with Facter 4

Facter::FactLoader `@external_facts` object id's depending on the run

start_object_id LOAD for run 12: 10760
 
end_object_id LOAD for run 12: 15860
 
-------------------- Start Run id: 12
 
start_object_id for run 12: 15860
 
start_object_id LOAD for run 13: 15860
 
end_object_id LOAD for run 13: 15880
 
-------------------- Start Run id: 13
 
start_object_id for run 13: 15880
 
end_object_id for run 13: 15880
 
>>>>>>>>>>>>>>>>>>>> END Run id: 13
 
start_object_id LOAD for run 14: 15880
 
end_object_id LOAD for run 14: 15900
 
-------------------- Start Run id: 14
 
start_object_id for run 14: 15900
 
end_object_id for run 14: 15900
 
>>>>>>>>>>>>>>>>>>>> END Run id: 14
 
start_object_id LOAD for run 15: 15900
 
end_object_id LOAD for run 15: 15920
 
-------------------- Start Run id: 15
 
start_object_id for run 15: 15920
 
end_object_id for run 15: 15920
 
>>>>>>>>>>>>>>>>>>>> END Run id: 15
 
start_object_id LOAD for run 16: 15920
 
end_object_id LOAD for run 16: 15940
 
-------------------- Start Run id: 16
 
start_object_id for run 16: 15940
 
end_object_id for run 16: 15940
 
>>>>>>>>>>>>>>>>>>>> END Run id: 16
 
start_object_id LOAD for run 17: 15940
 
end_object_id LOAD for run 17: 15960
 
-------------------- Start Run id: 17
 
start_object_id for run 17: 15960
 
end_object_id for run 17: 15960
 
>>>>>>>>>>>>>>>>>>>> END Run id: 17
 
start_object_id LOAD for run 18: 15960
 
end_object_id LOAD for run 18: 15980
 
-------------------- Start Run id: 18
 
start_object_id for run 18: 15980
 
end_object_id for run 18: 15980
 
>>>>>>>>>>>>>>>>>>>> END Run id: 18
 
end_object_id for run 12: 15980
 
>>>>>>>>>>>>>>>>>>>> END Run id: 12

Bogdan Irimie (Jira)

unread,
Sep 28, 2020, 4:08:05 AM9/28/20
to puppe...@googlegroups.com

root@gowned-decking:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter# facter os
 
{
 
  architecture => "amd64",
 
  distro => {
 
    codename => "xenial",
 
    description => "Ubuntu 16.04.5 LTS",
 
    id => "Ubuntu",
 
    release => {
 
      full => "16.04",
 
      major => "16.04"
 
    }
 
  },
 
  family => "Debian",
 
  hardware => "x86_64",
 
  name => "Ubuntu",
 
  release => {
 
    full => "16.04",
 
    major => "16.04"
 
  },
 
  selinux => {
 
    enabled => false
 
  }
 
}
 
root@gowned-decking:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter# rm -rf /opt/puppetlabs/puppet/cache/lib/facter/
 
root@gowned-decking:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter# puppet agent -t
 
Info: Using configured environment 'production'
 
Info: Retrieving pluginfacts
 
Info: Retrieving plugin
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/facter_dot_d.rb]/ensure: defined content as '{sha256}8a17c7f9b470dbaaff51e7a4f2103c4e5c4d92667c4b7396cd55d76ebcedab1b'
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/i18ndemo_fact.rb]/ensure: defined content as '{sha256}970d26ac91fd7b801062e0c17dcbf6b4ef46be2dd1d4e18adcc1ba0912158006'
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/package_provider.rb]/ensure: defined content as '{sha256}4f396a5e0b1016e4ceeb7e9273423171d5a51e083e489c9f8477de88f2c254b6'
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/pe_version.rb]/ensure: defined content as '{sha256}9d3a1b46fd1e2d2b604a68994d4b8197b9ca1d8344fe5fa2c2797d8de5742f6f'
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/puppet_settings.rb]/ensure: defined content as '{sha256}727f7e6d154cbb5773cea227f6a17019b0a3a73624bbfaa6590ed1de8314ae7b'
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/root_home.rb]/ensure: defined content as '{sha256}e857cd21ee4fe14739c8e0f330de645f1f54c41229d608731d4af29a55b8d532'
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/service_provider.rb]/ensure: defined content as '{sha256}1beaee8dd3c87c9d887184b9e69c3053762f2261a6ebceaa75f682dab54ba823'
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/util]/ensure: created
 
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/util/puppet_settings.rb]/ensure: defined content as '{sha256}af86574985faba7b25893444917da5197f00bbb39182f7a56123cca6ee71e0f4'
 
Info: Retrieving locales
 
Info: Loading facts
 
Error: Facter: Error while resolving custom fact fact='i18ndemo_fact', resolution='<anonymous>': i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo
 
Info: Caching catalog for gowned-decking.delivery.puppetlabs.net
 
Info: Applying configuration version '1601280423'
 
Notice: Applied catalog in 0.01 seconds

Bogdan Irimie (Jira)

unread,
Sep 28, 2020, 7:16:04 AM9/28/20
to puppe...@googlegroups.com

The issue can be reproduce only with facter using the fallowing custom fact:

Facter.value('os.name')
 
 
 
Facter.add(:my_custom_fact) do
 
  confine :kernel => :darwin
 
  setcode do
 
    Facter.value('os.name')
 
  end
 
end

Bogdan Irimie (Jira)

unread,
Sep 28, 2020, 8:55:03 AM9/28/20
to puppe...@googlegroups.com
Bogdan Irimie assigned an issue to Bogdan Irimie
 
Change By: Bogdan Irimie
Assignee: Florin Dragos Bogdan Irimie
Reply all
Reply to author
Forward
0 new messages