Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2799 Missing output when resolving custom facts with Facter 4 Change By: Bogdan Irimie Assignee: Florin Dragos Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371890.160018534.44187.1601297700235%40Atlassian.JIRA.
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Bogdan Irimie commented on FACT-2799
Re: Missing output when resolving custom facts with Facter 4
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
Add Comment
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Bogdan Irimie commented on FACT-2799
Re: Missing output when resolving custom facts with Facter 4
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",
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Bogdan Irimie commented on 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
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2799 Missing output when resolving custom facts with Facter 4 Change By: Bogdan Irimie Sprint: ghost-23.09 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371890.160018534.41166.160080339%40Atlassian.JIRA.
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Florin Dragos assigned an issue to Florin Dragos Facter / FACT-2799 Missing output when resolving custom facts with Facter 4 Change By: Florin Dragos Assignee: Florin Dragos Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371890.160018534.40214.1600766880030%40Atlassian.JIRA.
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2799 Missing output when resolving custom facts with Facter 4 Change By: Bogdan Irimie Sprint: ready for triage ghost-23.09 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371890.160018534.37139.1600263660091%40Atlassian.JIRA.
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2799 Missing output when resolving custom facts with Facter 4 Change By: Bogdan Irimie Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371890.160018534.37138.1600263660037%40Atlassian.JIRA.
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2799 Missing output when resolving custom facts with Facter 4 Change By: Mihai Buzgau Sprint: PR - Triage ready for triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371890.160018534.37128.1600262280191%40Atlassian.JIRA.
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2799 Missing output when resolving custom facts with Facter 4 Change By: Mihai Buzgau Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371890.160018534.37127.1600262280147%40Atlassian.JIRA.
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2799 Missing output when resolving custom facts with Facter 4 Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371890.160018534.37126.1600262280103%40Atlassian.JIRA.
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
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) h2. How to set the environmenth4. 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.debh4. Make the new binaries easily accessible:{color:#57d9a3}➜{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc{color:#57d9a3}➜{color} source ~/.bashrch4. 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 -yh4. 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 starth4. 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 -th4. Install this module that contains a custom fact : {color:#57d9a3}➜{color} puppet module install eputnam-i18ndemoh4. 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 issueh4. 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 ...
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
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) h2. h2. How to set the environmenth4. 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.debh4. Make the new binaries easily accesible accessible: {color:# c1c7d0 57d9a3 } > ➜ {color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc {color:# c1c7d0 57d9a3 } > ➜ {color} source ~/.bashrch4. 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 -yh4. 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 starth4. 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 -th4. Install this module that contains a custom fact{color:# c1c7d0 57d9a3 } > ➜ {color} puppet module install eputnam-i18ndemoh4. 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 issueh4. 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}*
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
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)h2. h2. How to set the environmenth4. 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.debh4. Make the new binaries easily accesible{color:#c1c7d0}>{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc {color:#c1c7d0}>{color} source ~/.bashrch4. 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 -yh4. 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 starth4. 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 -th4. Install this module that contains a custom fact{color:#c1c7d0}>{color} puppet module install eputnam-i18ndemoh4. 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 raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') end end{panel}h2. h2. How to reproduce the issueh4. 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:
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
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)h2. h2. How to set the environmenth4. 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.debh4. Make the new binaries easily accesible{color:#c1c7d0}>{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc {color:#c1c7d0}>{color} source ~/.bashrch4. 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 -yh4. 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 starth4. 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 -th4. Install this module that contains a custom fact{color:#c1c7d0}>{color} puppet module install eputnam-i18ndemoh4. 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 issueh4. 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 ...
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
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) 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.debh4. Make the new binaries easily accesible{color:#c1c7d0}>{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc {color:#c1c7d0}>{color} source ~/.bashrch4. 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 -yh4. 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 starth4. 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 -th4. Install this module that contains a custom fact{color:#c1c7d0}>{color} puppet module install eputnam-i18ndemoh4. 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 issueh4. 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 ...
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
Luchian Nemes
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.debdpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.debMake the new binaries easily accesibleecho 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrcsource ~/.bashrcCheck Puppet versionpuppet --versionCheck Facter versionfacter --versionInstall Puppet Serverwget 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.debdpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -yCheck if it installed correctly (make sure you've run above commands correctly)puppetserver --versionStart the Puppet Server serviceservice puppetserver startConfigure Puppet Server addresspuppet config set server $(facter fqdn)Make sure Puppet Agent and Puppet Server communicate accordinglypuppet agent -tInstall this module that contains a custom factpuppet module install eputnam-i18ndemoYou can see the content of this custom factcat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rbFacter.add('i18ndemo_fact') do setcode do raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') endendHow to reproduce the issue:With the module above/custom fact in place, do the first 'puppet agent -t' run:puppet agent -tDo the second run and now observe the expected raise:puppet agent -tHow to reset environment to reproduce the issue again:rm -rf /opt/puppetlabs/puppet/cache/lib/facter/
Add Comment
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
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' doinstall_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")endstep "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) endend endend{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes created an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Issue Type:
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
Reporter:
Luchian Nemes
