Jira (PUP-10795) Accept multiple logdest locations in puppet.conf
Title: Message Title Josh Cooper commented on PUP-10795 Re: Accept multiple logdest locations in puppet.conf Puppet applications accept multiple -logdest parameters on the command line, but not in settings. To implement this, we would probably have to allow a comma separated list of log destinations, e.g. -logdest console,syslog,/path/to/log, and then register each logdestination component, e.g. Puppet::Util::Log.newdestination(). In theory a comma could be part of an existing logfile destination filename, but I think that's highly unlikely. 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.379455.1606836974000.90384.1606953300027%40Atlassian.JIRA.
Jira (PUP-1042) Change --write-catalog-summary option into a config setting
Title: Message Title Josh Cooper commented on PUP-1042 Re: Change --write-catalog-summary option into a config setting Implementation Notes: 1. Add a new setting named write_catalog_summary in lib/puppet/defaults.rb of type :boolean, default to false 2. Change Puppet::Application::Agent#setup so it defaults the write_catalog_summary to true. The value specified in puppet.conf or command line should override the application default. 3. Update Puppet::Application::Agent help text to mention the write_catalog_summary setting. 4. Remove https://github.com/puppetlabs/puppet/blob/96029b003cfbb5303426cbc110f350a0d4b6af06/lib/puppet/application/apply.rb#L19 5. Update https://github.com/puppetlabs/puppet/blob/96029b003cfbb5303426cbc110f350a0d4b6af06/lib/puppet/configurer.rb#L121-L122 so that we only write the class file and resource file if Puppet[:write_catalog_summary] is true. 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.21360.1387191693000.90381.1606953060037%40Atlassian.JIRA.
Jira (PUP-2774) class can `require` itself without raising an error
Title: Message Title
Josh Cooper commented on PUP-2774
Re: class can `require` itself without raising an error
The require function has been implemented using the 4x function API, so you'll want to look at https://github.com/puppetlabs/puppet/blob/96029b003cfbb5303426cbc110f350a0d4b6af06/lib/puppet/functions/require.rb#L71-L72. Note resource is an instance of Puppet::Parser::Resource while ref is an instance of Puppet::Resource, and the former subclasses the latter. So you can compare the value objects directly to determine if they are equivalent. Given the following manifest:
class a {
require a
}
include a
We expect it to raise a parse error during compilation with file, line, etc info. One option is to: 1. Add a new issue constant to Puppet::Pops::Issues 2. If resource == ref then call
raise Puppet::ParseErrorWithIssue.from_issue_and_stack(
Puppet::Pops::Issues::YOUR_NEW_CONSTANT,
{:operation => 'require'})
3. Add a test to spec/unit/functions/require_spec.rb to verify the excepted exception is raised when calling compile_to_catalog with the circular requirement. 4. Note this won't catch cycles among classes, e.g. A -> B -> A. Those will be caught later on. Alternatively, you could add logic to https://github.com/puppetlabs/puppet/blob/96029b003cfbb5303426cbc110f350a0d4b6af06/lib/puppet/parser/compiler/catalog_validator/relationship_validator.rb#L25 to ensure the resource is not the sam
Jira (PUP-2774) class can `require` itself without raising an error
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2774 class can `require` itself without raising an error Change By: Josh Cooper Labels: beginner help_wanted 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.38983.1402617581000.90343.1606952460096%40Atlassian.JIRA.
Jira (PUP-7040) Non-existent services throw an error when attempting to disable them
Title: Message Title
Josh Cooper commented on PUP-7040
Re: Non-existent services throw an error when attempting to disable them
I can't reproduce this problem. PUP-6822 also shows it's working as expected for linux, but wasn't for windows, so I'm assuming this was fixed in between:
# /usr/bin/systemctl is-enabled -- cups
Failed to get unit file state for cups.service: No such file or directory
# cat manifest.pp
service {'cups':
enable => false,
}
# puppet apply manifest.pp
Notice: Compiled catalog for XXX in environment production in 0.17 seconds
Notice: Applied catalog in 0.03 seconds
Add Comment
Jira (PUP-7522) Add the ability to view trusted fact values from an agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7522 Add the ability to view trusted fact values from an agent Change By: Josh Cooper Labels: beginner help_wanted 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.190624.1494544362000.90201.1606948380034%40Atlassian.JIRA.
Jira (PUP-8650) Repository error message uri is missing part of the path
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8650 Repository error message uri is missing part of the path Change By: Josh Cooper Labels: beginner help_wanted 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.244849.1523310203000.90199.1606948260138%40Atlassian.JIRA.
Jira (PUP-10251) Feature request: Add a way to turn looked up undef values in Hiera into "not found"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10251 Feature request: Add a way to turn looked up undef values in Hiera into "not found" Change By: Josh Cooper Labels: beginner 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.343178.1579803772000.90169.1606948080035%40Atlassian.JIRA.
Jira (PUP-10403) Puppet parser --help is missing the --tasks flag
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10403 Puppet parser --help is missing the --tasks flag Change By: Josh Cooper Labels: beginner help_wanted 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.353370.1585618793000.90157.1606947960026%40Atlassian.JIRA.
Jira (PUP-10797) puppet 7 gem is missing runtime dependency on scanf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10797 puppet 7 gem is missing runtime dependency on scanf Change By: Josh Cooper Team: Coremunity 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.379680.1606930635000.90144.1606947480052%40Atlassian.JIRA.
Jira (PUP-10797) puppet 7 gem is missing runtime dependency on scanf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10797 puppet 7 gem is missing runtime dependency on scanf Change By: Josh Cooper Sprint: Platform Core KANBAN 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.379680.1606930635000.90145.1606947480097%40Atlassian.JIRA.
Jira (PUP-10797) puppet 7 gem is missing runtime dependency on scanf
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10797 puppet 7 gem is missing runtime dependency on scanf Change By: Josh Cooper Assignee: Josh Cooper 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.379680.1606930635000.90143.1606947420082%40Atlassian.JIRA.
Jira (PUP-10797) puppet 7 gem is missing runtime dependency on scanf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10797 puppet 7 gem is missing runtime dependency on scanf Change By: Josh Cooper Issue Type: Task Bug 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.379680.1606930635000.90001.1606939560028%40Atlassian.JIRA.
Jira (PUP-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`
Title: Message Title Cas Donoghue commented on PUP-9578 Re: Remove distinction between `puppet parser validate` and `puppet parser validate --tasks` Nick Walker This seems like it is useful for a bolt user to validate plans. Should we prioritize making a clear workflow in bolt for the equivalent of using the --tasks flag? That way you would just use the bolt feature for this and keep using the puppet parser version for manifests. 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.301178.155320275.89975.1606938900026%40Atlassian.JIRA.
Jira (PUP-9692) hiera explain should redact values converted to Sensitive in --debug mode
Title: Message Title Cas Donoghue commented on PUP-9692 Re: hiera explain should redact values converted to Sensitive in --debug mode Josh Cooper were there any recent changes in how Sensitive works that would have fixed this issue? 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.307422.1556927311000.89951.1606938300038%40Atlassian.JIRA.
Jira (PUP-9714) Add support for nested hiera interpolation
Title: Message Title Maggie Dreyer commented on PUP-9714 Re: Add support for nested hiera interpolation In general, we are not prioritizing any Hiera features for the time being. If that changes, we can revisit this. 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.309648.1558477577000.89945.1606938120029%40Atlassian.JIRA.
Jira (PDB-4932) Sync summary queries can hang
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4932 Sync summary queries can hang Change By: Zachary Kent Story Points: 8 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.375125.1602801356000.89897.1606937280032%40Atlassian.JIRA.
Jira (PDB-4974) Wait on schedulers to shut down
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4974 Wait on schedulers to shut down Change By: Rob Browning Epic Link: PDB-4969 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.379687.16069.89896.1606937220028%40Atlassian.JIRA.
Jira (FACT-2854) Empty string in blocklist blocks all core facts
Title: Message Title Josh Cooper commented on FACT-2854 Re: Empty string in blocklist blocks all core facts Which facter version was this fixed in? 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.377407.1604652706000.89895.1606937160026%40Atlassian.JIRA.
Jira (FACT-2832) Fix AIX performance
Title: Message Title Josh Cooper commented on FACT-2832 Re: Fix AIX performance Which facter version was this fixed in? 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.374200.1602077563000.89874.1606936860339%40Atlassian.JIRA.
Jira (FACT-2837) Unable to block memory/swap tree via blocklist
Title: Message Title Josh Cooper commented on FACT-2837 Re: Unable to block memory/swap tree via blocklist Which facter version was this fixed in? 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.375055.1602770971000.89875.1606936860384%40Atlassian.JIRA.
Jira (FACT-2816) Ec2 facts return wrong information on physical machines
Title: Message Title Josh Cooper commented on FACT-2816 Re: Ec2 facts return wrong information on physical machines Which facter version was this fixed in? 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.373175.1601025894000.89873.1606936860297%40Atlassian.JIRA.
Jira (FACT-2840) Fix to_hash performance for Solaris platforms
Title: Message Title Josh Cooper commented on FACT-2840 Re: Fix to_hash performance for Solaris platforms Which facter version was this fixed in? 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.375223.1603109437000.89876.1606936860428%40Atlassian.JIRA.
Jira (FACT-2869) Puppet 7.0.0 facter changes is_virtual fact to string (from boolean)
Title: Message Title Josh Cooper updated an issue Facter / FACT-2869 Puppet 7.0.0 facter changes is_virtual fact to string (from boolean) Change By: Josh Cooper Affects Version/s: FACT 4.0.46 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.378976.160585180.89862.1606936740089%40Atlassian.JIRA.
Jira (FACT-2869) Puppet 7.0.0 facter changes is_virtual fact to string (from boolean)
Title: Message Title Josh Cooper updated an issue Facter / FACT-2869 Puppet 7.0.0 facter changes is_virtual fact to string (from boolean) Change By: Josh Cooper Labels: platform_7.1 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.378976.160585180.89861.1606936740045%40Atlassian.JIRA.
Jira (FACT-2874) facter 4.0.46 should load external fact files in lexicographical order
Title: Message Title Josh Cooper updated an issue Facter / FACT-2874 facter 4.0.46 should load external fact files in lexicographical order Change By: Josh Cooper Affects Version/s: FACT 4.0.46 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.379132.1606176297000.89837.1606936500163%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Josh Cooper updated an issue Facter / FACT-2880 facter 4 differing output from facter 3 for service_provider fact Change By: Josh Cooper Labels: platform_7.1 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.379364.1606744776000.89839.1606936500257%40Atlassian.JIRA.
Jira (FACT-2874) facter 4.0.46 should load external fact files in lexicographical order
Title: Message Title Josh Cooper updated an issue Facter / FACT-2874 facter 4.0.46 should load external fact files in lexicographical order Change By: Josh Cooper Labels: platform_7.1 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.379132.1606176297000.89838.1606936500207%40Atlassian.JIRA.
Jira (FACT-2859) [regression] External facts are loaded when using puppet lookup for a different node
Title: Message Title Josh Cooper updated an issue Facter / FACT-2859 [regression] External facts are loaded when using puppet lookup for a different node Change By: Josh Cooper Labels: platform_7.1 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.378374.1605310876000.89833.1606936440403%40Atlassian.JIRA.
Jira (FACT-2859) [regression] External facts are loaded when using puppet lookup for a different node
Title: Message Title Josh Cooper updated an issue Facter / FACT-2859 [regression] External facts are loaded when using puppet lookup for a different node Change By: Josh Cooper Affects Version/s: FACT 4.0.46 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.378374.1605310876000.89832.1606936440362%40Atlassian.JIRA.
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Josh Cooper updated an issue Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Josh Cooper The gem-based facter 4.0.x does not return the correct fqdn – it returns the hostname with dot instead of returning hostname with the domain suffix.Example: facter fqdn Output:myhostname.The correct output: myhostname.mydomain.comThis breaks scripts which issue http request to the fqdn (like: [http://myhostname.:1234|http://myhostname.:1234/] is not reachable). Add new os support on litmus modules*Before to start, make sure the new platform is provided by vmpooler and it's fully equipped* *an image with the new os is available from puppet agent team*[Here|https://confluence.puppetlabs.com/display/ECO/How+to+add+support+for+new+platforms] you can find a list with all the converted modules to use litmusStep1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml*metadata.json file* - check for section: operatingsystem_support - add new version under the intended operatingsystem and save*[ci-job-configs/jenkii/platform/projects/modules-unified.yaml|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml]* - check for the module and add new platform under smoke_platforms| pe_platforms (if this platform was released)Step2: Using pdksync, create PR with the changes on modules Step3: Create PR on [ci-job-configs|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml] Step4: Deploy experimental platform intended module Step5: Run ad-hoc tests using that experimental Step6: Check testing results Step7: If failures, fix them, re-execute all the testing part until they are green Step8: Ask for review/merge(-) check for vmpooler platform (-) pdksync: update metadata.json (-) pdksync: push changes, create commit (-) create PR on ci-job-configs (-) deploy experimental platform intended module (-) run tests through ad-hoc jenkins using that experimental (-) check testing report (-) if failures, fix them, re-execute ad-hoc until they are green (-) review/merge PR Add Comment
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Josh Cooper updated an issue Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Josh Cooper Environment: The gem-based facter 4.0.x does not return the correct fqdn – it returns the hostname with dot instead of returning hostname with the domain suffix.Example:facter fqdnOutput:myhostname.The correct output:myhostname.mydomain.comThis breaks scripts which issue http request to the fqdn (like: [http://myhostname.:1234|http://myhostname.:1234/] is not reachable). 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.379598.1606874598000.89822.1606936320435%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Josh Cooper updated an issue Facter / FACT-2884 How to disable Querying Ec2 metadata Change By: Josh Cooper In non-cloud environment, issuing the request to [http://169.254.169.254/latest/meta-data] causes delay in execution:Facter: Querying Ec2 metadata Facter: Trying to connect to [http://169.254.169.254/latest/meta-data/] but got: execution expiredHow to disable this query (don't need it in a non-cloud environment)?Tried setting the environment variable FACTER_virtual=generic but that does not suppress this query in non-cloud environment. Add new os support on litmus modules*Before to start, make sure the new platform is provided by vmpooler and it's fully equipped* *an image with the new os is available from puppet agent team*[Here|https://confluence.puppetlabs.com/display/ECO/How+to+add+support+for+new+platforms] you can find a list with all the converted modules to use litmusStep1: Using pdksync, check/update metadata.json, ci-job-configs/jenkii/platform/projects/modules-unified.yaml*metadata.json file* - check for section: operatingsystem_support - add new version under the intended operatingsystem and save*[ci-job-configs/jenkii/platform/projects/modules-unified.yaml|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml]* - check for the module and add new platform under smoke_platforms| pe_platforms (if this platform was released)Step2: Using pdksync, create PR with the changes on modules Step3: Create PR on [ci-job-configs|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/modules-unified.yaml] Step4: Deploy experimental platform intended module Step5: Run ad-hoc tests using that experimental Step6: Check testing results Step7: If failures, fix them, re-execute all the testing part until they are green Step8: Ask for review/merge(-) check for vmpooler platform (-) pdksync: update metadata.json (-) pdksync: push changes, create commit (-) create PR on ci-job-configs (-) deploy experimental platform intended module (-) run tests through ad-hoc jenkins using that experimental (-) check testing report (-) if failures, fix them, re-execute ad-hoc until they are green (-) review/merge PR Add Comment
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Josh Cooper updated an issue Facter / FACT-2884 How to disable Querying Ec2 metadata Change By: Josh Cooper Environment: In non-cloud environment, issuing the request to http://169.254.169.254/latest/meta-data causes delay in execution:Facter: Querying Ec2 metadataFacter: Trying to connect to http://169.254.169.254/latest/meta-data/ but got: execution expiredHow to disable this query (don't need it in a non-cloud environment)?Tried setting the environment variable FACTER_virtual=generic but that does not suppress this query in non-cloud environment. 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.379602.1606876774000.89820.1606936320348%40Atlassian.JIRA.
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Josh Cooper updated an issue Facter / FACT-2883 Gem-based Facter 4.0.x does not log the facts in debug mode Change By: Josh Cooper Labels: platform_7.1 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.379599.1606874914000.89810.1606936200480%40Atlassian.JIRA.
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Josh Cooper updated an issue Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Josh Cooper Labels: platform_7.1 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.379598.1606874598000.89809.1606936200434%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Sanjay Tripathi commented on FACT-2884 Re: How to disable Querying Ec2 metadata To elaborate on my previous comment, we would like to avoid making this change in the global facter.conf. Adding it in local facter.conf does not seem to be effective. The environment variable Facter_generic provided the flexibility of turning off EC2 queries without changing the global facter.conf. Can we get a similar solution in Facter 4.x? 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.379602.1606876774000.89766.1606933860137%40Atlassian.JIRA.
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Sanjay Tripathi commented on FACT-2883 Re: Gem-based Facter 4.0.x does not log the facts in debug mode Yes, the logging would be helpful as shown in the above snippet. Thanks for the prompt response. Can we minimize the other facter-related debug logging to avoid clutter? 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.379599.1606874914000.89740.1606933560027%40Atlassian.JIRA.
Jira (PDB-4974) Wait on schedulers to shut down
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4974 Wait on schedulers to shut down Change By: Rob Browning Assignee: Rob Browning 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.379687.16069.89739.1606933500059%40Atlassian.JIRA.
Jira (PDB-4974) Wait on schedulers to shut down
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4974 Wait on schedulers to shut down Issue Type: Bug Assignee: Unassigned Created: 2020/12/02 10:22 AM Priority: Normal Reporter: Rob Browning Although we'd expected to be waiting for our schedulers (at-at pools) to stop before returning from our start/stop methods, we weren't because at-at runs the relevant ScheduledThreadPoolExecutor shutdown function in a future and returns immediately. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10797) puppet 7 gem is missing runtime dependency on scanf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10797 puppet 7 gem is missing runtime dependency on scanf Change By: Josh Cooper Labels: platform_7.1 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.379680.1606930635000.89727.1606932540049%40Atlassian.JIRA.
Jira (PUP-10797) puppet 7 gem is missing runtime dependency on scanf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10797 puppet 7 gem is missing runtime dependency on scanf Change By: Josh Cooper Fix Version/s: PUP 7.1.0 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.379680.1606930635000.89729.1606932540153%40Atlassian.JIRA.
Jira (PUP-10797) puppet 7 gem is missing runtime dependency on scanf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10797 puppet 7 gem is missing runtime dependency on scanf Change By: Josh Cooper Affects Version/s: PUP 7.0.0 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.379680.1606930635000.89728.1606932540105%40Atlassian.JIRA.
Jira (FACT-2871) Regression: interfaces without an ipaddress assigned are not anymore reported
Title: Message Title Josh Cooper updated an issue Facter / FACT-2871 Regression: interfaces without an ipaddress assigned are not anymore reported Change By: Josh Cooper Labels: platform_7.1 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.379055.160591045.89717.1606932120179%40Atlassian.JIRA.
Jira (PUP-10790) user provider with uid/gid as Integer raises warning
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10790 user provider with uid/gid as Integer raises warning Change By: Josh Cooper Labels: platform_7.1 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.379059.1605916728000.89715.1606932120084%40Atlassian.JIRA.
Jira (FACT-2870) Can't run puppet on machines with VLANs as facts are failing
Title: Message Title Josh Cooper updated an issue Facter / FACT-2870 Can't run puppet on machines with VLANs as facts are failing Change By: Josh Cooper Labels: platform_7.1 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.379053.1605909534000.89716.1606932120131%40Atlassian.JIRA.
Jira (FACT-2881) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Josh Cooper updated an issue Facter / FACT-2881 puppet 7 treats nonexistent fact differently compared to puppet 6? Change By: Josh Cooper Labels: platform_7.1 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.379177.1606234679000.89719.1606932120268%40Atlassian.JIRA.
Jira (FACT-2881) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Josh Cooper updated an issue Facter / FACT-2881 puppet 7 treats nonexistent fact differently compared to puppet 6? Change By: Josh Cooper Affects Version/s: FACT 4.0.46 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.379177.1606234679000.89720.1606932120312%40Atlassian.JIRA.
Jira (FACT-2872) Regressions: secondary interfaces are not anymore reported
Title: Message Title Josh Cooper updated an issue Facter / FACT-2872 Regressions: secondary interfaces are not anymore reported Change By: Josh Cooper Labels: platform_7.1 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.379058.1605915439000.89718.1606932120224%40Atlassian.JIRA.
Jira (FACT-2872) Regressions: secondary interfaces are not anymore reported
Title: Message Title Josh Cooper updated an issue Facter / FACT-2872 Regressions: secondary interfaces are not anymore reported Change By: Josh Cooper Affects Version/s: FACT 4.0.46 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.379058.1605915439000.89713.1606932060089%40Atlassian.JIRA.
Jira (FACT-2870) Can't run puppet on machines with VLANs as facts are failing
Title: Message Title Josh Cooper updated an issue Facter / FACT-2870 Can't run puppet on machines with VLANs as facts are failing Change By: Josh Cooper Affects Version/s: FACT 4.0.46 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.379053.1605909534000.89714.1606932060132%40Atlassian.JIRA.
Jira (FACT-2871) Regression: interfaces without an ipaddress assigned are not anymore reported
Title: Message Title Josh Cooper updated an issue Facter / FACT-2871 Regression: interfaces without an ipaddress assigned are not anymore reported Change By: Josh Cooper Affects Version/s: FACT 4.0.46 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.379055.160591045.89711.1606932001060%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Josh Cooper commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact It'd be great if there was a PDK lint rule to catch this. It's a pretty common error when writing custom facts. I'm not sure how feasible that is though? /cc David Schmitt 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.379364.1606744776000.89707.1606931820023%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Sanjay Tripathi commented on FACT-2884 Re: How to disable Querying Ec2 metadata Yes, it does block the EC2 fact when the blocklist is added in facter.conf: Debug: Facter: blocking collection of EC2 facts Can facter.conf be kept in the config directory passed to puppet apply via --confdir? Asking because we may not want to modify the global facter.conf. 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.379602.1606876774000.89695.1606930680141%40Atlassian.JIRA.
Jira (PUP-10797) puppet 7 gem is missing runtime dependency on scanf
Title: Message Title Josh Cooper created an issue Puppet / PUP-10797 puppet 7 gem is missing runtime dependency on scanf Issue Type: Task Assignee: Unassigned Created: 2020/12/02 9:37 AM Priority: Normal Reporter: Josh Cooper Ruby 2.7 removed the scanf implementation (in Kernel, IO and String) from core ruby to a separate gem. Puppet's scanf function depends on that ruby method, but only expresses the scanf runtime dependency in its Gemfile, but not in the gem that is pushed to rubygems. See https://rubygems.org/gems/puppet/versions/7.0.0. As a result, if a module calls the puppet scanf function using puppet 7 (gem) and ruby 2.7, such as when running rspec tests, then you'll see (for example in https://github.com/puppetlabs/puppetlabs-puppetdb/pull/317) LoadError: cannot load such file -- scanf This doesn't affect module functionality when testing or running against puppet-agent 7 packages, because the scanf gem is included. AFAIK rubygems doesn't have a way to express conditional runtime dependencies (i.e. only add this dependency when running on ruby 2.7 and up). So the best thing may be to always add the runtime dependency for the puppet 7.x collection? If you're running the puppet 7 gem with ruby 2.5.0, then things will still work (the scanf gem is ignored).
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title
Tim Meusel commented on FACT-2880
Re: facter 4 differing output from facter 3 for service_provider fact
awesome, I tested it locally and your patch works for me:
~ # puppet agent -t --environment puppet7
Info: Using configured environment 'puppet7'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/alert_manager_running.rb]/content:
--- /opt/puppetlabs/puppet/cache/lib/facter/alert_manager_running.rb 2020-11-04 16:45:06.270485994 +0100
+++ /tmp/puppet-file20201202-8312-olysy6 2020-12-02 17:56:41.113642951 +0100
@@ -1,10 +1,9 @@
require 'puppet'
-service = Puppet::Type.type(:service).new(:name => 'alert_manager') # rubocop:disable Style/HashSyntax
-
Facter.add('prometheus_alert_manager_run
Jira (FACT-2881) puppet 7 treats nonexistent fact differently compared to puppet 6?
Title: Message Title Bogdan Irimie commented on FACT-2881 Re: puppet 7 treats nonexistent fact differently compared to puppet 6? Josh Cooper thanks for moving this to FACTER! I changed the branch name https://github.com/puppetlabs/facter/pull/2204 and the commit message. 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.379177.1606234679000.89639.1606927980079%40Atlassian.JIRA.
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title
Bogdan Irimie commented on FACT-2883
Re: Gem-based Facter 4.0.x does not log the facts in debug mode
Hi Sanjay Tripathi, please give https://github.com/puppetlabs/facter/pull/2203/files a try and let me know if the new log suites your needs. A snippet from the new log:
[2020-12-02 16:03:27.230497 ] DEBUG Facter::FactManager - fact "os.release" has resolved to: {"full"=>"20.1.0", "major"=>"20", "minor"=>"1"}
[2020-12-02 16:03:27.230507 ] DEBUG Facter::FactManager - fact "os.macosx.product" has resolved to: macOS
[2020-12-02 16:03:27.230519 ] DEBUG Facter::FactManager - fact "os.macosx.version" has resolved to: {"full"=>"11.0.1", "major"=>"11.0", "minor"=>"1"}
[2020-12-02 16:03:27.230528 ] DEBUG Facter::FactManager - fact "os.macosx.build" has resolved to: 20B29
[2020-12-02 16:03:27.230537 ] DEBUG Facter::FactManager - fact "os.name" has resolved to: Darwin
[2020-12-02 16:03:27.230546 ] DEBUG Facter::FactManager - fact "os.hardware" has resolved to: x86_64
[2020-12-02 16:03:27.230555 ] DEBUG Facter::FactManager - fact "os.architecture" has resolved to: x86_64
[2020-12-02 16:03:27.230566 ] DEBUG Facter::FactManager - fact "os.family" has resolved to: Darwin
[2020-12-02 16:03:27.230574 ] DEBUG Facter::FactManager - fact "kernelversion" has resolved to: 20.1.0
[2020-12-02 16:03:27.230657 ] DEBUG Facter::FactManager - fact "kernelrelease" has resolved to: 20.1.0
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2883 Gem-based Facter 4.0.x does not log the facts in debug mode Change By: Bogdan Irimie Assignee: 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.379599.1606874914000.89612.1606927260140%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2880 facter 4 differing output from facter 3 for service_provider fact Change By: Bogdan Irimie Assignee: 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.379364.1606744776000.89590.1606926840261%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2884 How to disable Querying Ec2 metadata Change By: Bogdan Irimie Assignee: 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.379602.1606876774000.89586.1606926780088%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title
Bogdan Irimie commented on FACT-2880
Re: facter 4 differing output from facter 3 for service_provider fact
Tim Meusel and Matt Darcy we managed to reproduce the behaviour you describe by installing `puppet-prometheus` module. The custom fact https://github.com/voxpupuli/puppet-prometheus/blob/master/lib/facter/alert_manager_running.rb seams to generate the problem because it has code outside the `setcode` block. After moving
service = Puppet::Type.type(:service).new(:name => 'alert_manager') # rubocop:disable Style/HashSyntax
inside the `setcode` block everything worked as expected. Just as a test, please change the custom fact to
require 'puppet'
Facter.add('prometheus_alert_manager_running') do
setcode do
begin
service = Puppet::Type.type(:service).new(:name => 'alert_manager') # rubocop:disable Style/HashSyntax
service.provider.status == :running
rescue Puppet::Error
false
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.379598.1606874598000.89425.1606918560041%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title
Bogdan Irimie commented on FACT-2884
Re: How to disable Querying Ec2 metadata
Hi Sanjay Tripathi Setting the FACTER_virtual=generic will not work in Facter 4. This worked in Facter 3 because EC2 facts made a check on `virtual` fact before they were resolved. If you don't need EC2 facts, an elegant solution is to block them using `facter.conf`. The default location for `facter.conf` is `/etc/puppetlabs/facter/facter.conf` e.g.
facts : {
blocklist : [ "EC2" ],
}
You can check if EC2 fact are resolved by running `facter --debug` and searching for `Querying Ec2 metadata`. If you block the EC2 facts, you should not see this message in debug mode.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Bogdan Irimie Story Points: 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.379598.1606874598000.89404.1606910580038%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2880 facter 4 differing output from facter 3 for service_provider fact Change By: Bogdan Irimie Story Points: 5 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.379364.1606744776000.89403.1606910520032%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2884 How to disable Querying Ec2 metadata Change By: Bogdan Irimie Story Points: 1 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.379602.1606876774000.89400.1606909860057%40Atlassian.JIRA.
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2883 Gem-based Facter 4.0.x does not log the facts in debug mode Change By: Bogdan Irimie Story Points: 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.379599.1606874914000.89401.1606909860099%40Atlassian.JIRA.
Jira (FACT-2874) facter 4.0.46 should load external fact files in lexicographical order
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2874 facter 4.0.46 should load external fact files in lexicographical order 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.379132.1606176297000.89402.1606909860143%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2884 How to disable Querying Ec2 metadata Change By: Bogdan Irimie Assignee: 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.379602.1606876774000.89398.1606909800045%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Bogdan Irimie assigned an issue to Unassigned Facter / FACT-2884 How to disable Querying Ec2 metadata Change By: Bogdan Irimie Assignee: 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.379602.1606876774000.89399.1606909800100%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Matt Darcy commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact debugging for Arm hosts uploaded as text documents. 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.379364.1606744776000.89394.1606908120105%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Matt Darcy updated an issue Facter / FACT-2880 facter 4 differing output from facter 3 for service_provider fact Change By: Matt Darcy Attachment: pi-puppet6-facter4-sshd-resource-output.rtf 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.379364.1606744776000.89393.1606908120049%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Matt Darcy updated an issue Facter / FACT-2880 facter 4 differing output from facter 3 for service_provider fact Change By: Matt Darcy Attachment: pi-puppet7-facter4-sshd-resource-output.rtf 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.379364.1606744776000.89392.1606907580037%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Tim Meusel commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact Hi, I put all the infos into a gist, because the comments in Jira don't allow so many characters: https://gist.github.com/bastelfreak/4fd5f15f232d965480e21db7a5ef428b let me know if you need more information 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.379364.1606744776000.89391.1606907280037%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Mihai Buzgau commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact Tim Meusel Matt Darcy can you please provide the output for the following commands: puppet resource service sshd --debug and for facter os --debug since we were not able to reproduce this on the above-mentioned OSes it would be great if you could paste the output for both Puppet 6 and Puppet 7 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2882) Gem-based Facter 4.0.x does not return the complete FQDN
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2882 Gem-based Facter 4.0.x does not return the complete FQDN Change By: Bogdan Irimie Sprint: ghost-2.12 Sub-team: ghost 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.379598.1606874598000.89333.1606896420025%40Atlassian.JIRA.
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2883 Gem-based Facter 4.0.x does not log the facts in debug mode Change By: Bogdan Irimie Sprint: ghost-2.12 Sub-team: ghost 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.379599.1606874914000.89332.1606896300028%40Atlassian.JIRA.
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2884 How to disable Querying Ec2 metadata Change By: Bogdan Irimie Sprint: ghost-2.12 Sub-team: ghost 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.379602.1606876774000.89328.1606896120025%40Atlassian.JIRA.
