Jira (PDB-5084) Fix ssl-setup client-auth insinuation
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5084 Fix ssl-setup client-auth insinuation Change By: Rob Browning Sprint: HA 2020-04-07 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.393060.1616792845000.175559.1616793060081%40Atlassian.JIRA.
Jira (PDB-5084) Fix ssl-setup client-auth insinuation
Title: Message Title Rob Browning created an issue PuppetDB / PDB-5084 Fix ssl-setup client-auth insinuation Issue Type: Bug Affects Versions: PDB 6.15.0 Assignee: Rob Browning Created: 2021/03/26 2:07 PM Priority: Normal Reporter: Rob Browning Running puppetdb ssl-setup -f as sometimes suggested by the postinst ends up adding a duplicated assignment to the end of the jetty.ini file, i.e. client-auth = want = client-auth = want. Add Comment This message was sent by Atlassian Jira
Jira (PDB-5083) puppetlabs-puppetdb module release job uses wrong ruby version
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5083 puppetlabs-puppetdb module release job uses wrong ruby version Issue Type: CI Blocker Assignee: Unassigned Created: 2021/03/26 1:53 PM Fix Versions: PDB n/a Priority: Normal Reporter: Austin Blatt the module release job looks for ruby 2.5.7, which does not exist. Upgrading the ruby version to the ruby 2.6 version that exists on the machine allowed the job to succeed. https://jenkins-master-prod-1.delivery.puppetlabs.net/view/modules/view/puppetdb/view/master/ Add Comment
Jira (FACT-3000) Dot notation implemented in Facter 4 is incomplete
Title: Message Title
Reid Vandewiele updated an issue
Facter / FACT-3000
Dot notation implemented in Facter 4 is incomplete
Change By:
Reid Vandewiele
Facter 4 introduced compositive fact structuring via dot-notation as a feature. However, the dot-notation implementation used is incomplete, and behaves differently from dot-notation elsewhere in the ecosystem.Specifically, Facter 4 dot-notation splits key segments incorrectly, because it does not recognize the use of double or single quotes to indicate keys which contain literal dot characters.The reference implementation for dot-notation is found in Puppet, [here|https://github.com/puppetlabs/puppet/blob/85bd9ed07e3e6c956f1972624a50be914292e1ab/lib/puppet/pops/lookup/sub_lookup.rb#L6-L44].Full dot-notation should be supported everywhere Facter 4 currently evaluates dot-notation strings to segment structured fact names. This includes external fact output (text, json, yaml), as well as {{Facter.add()}}.*Today's behavior*Consider the following plain-text custom fact file:{code}foo.bar._one_=1foo.bar.two=2foo."i.have.dots"=3"me.too"=4{code}Today, Facter returns the following for these facts.{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"\"i": { "have": {"dots\"": "3" }} }, "\"me": {"too\"": "4" }}{code}This is incorrect.*Correct behavior*Full and correct support for dot-notation SHOULD give:{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"i.have.dots": "3" }, "me.too": "4"}{code}
Add Comment
Jira (FACT-3000) Dot notation implemented in Facter 4 is incomplete
Title: Message Title
Reid Vandewiele updated an issue
Facter / FACT-3000
Dot notation implemented in Facter 4 is incomplete
Change By:
Reid Vandewiele
Facter 4 introduced compositive fact structuring via dot-notation as a feature. However, the dot-notation implementation used is incomplete, and behaves differently from dot-notation elsewhere in the ecosystem.Specifically, Facter 4 dot-notation splits key segments incorrectly, because it does not recognize the use of double or single quotes to indicate keys which contain literal dot characters.The reference implementation for dot-notation is found in Puppet, [here|https://github.com/puppetlabs/puppet/blob/85bd9ed07e3e6c956f1972624a50be914292e1ab/lib/puppet/pops/lookup/sub_lookup.rb#L6-L44]. Full dot-notation should be supported everywhere Facter 4 currently evaluates dot-notation to segment structured fact names. This includes external fact output (text, json, yaml), as well as {{Facter.add()}}. *Today's behavior*Consider the following plain-text custom fact file:{code}foo.bar._one_=1foo.bar.two=2foo."i.have.dots"=3"me.too"=4{code}Today, Facter returns the following for these facts.{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"\"i": { "have": {"dots\"": "3" }} }, "\"me": {"too\"": "4" }}{code}This is incorrect.*Correct behavior*Full and correct support for dot-notation SHOULD give:{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"i.have.dots": "3" }, "me.too": "4"}{code}
Add Comment
Jira (FACT-3000) Dot notation implemented in Facter 4 is incomplete
Title: Message Title
Reid Vandewiele updated an issue
Facter / FACT-3000
Dot notation implemented in Facter 4 is incomplete
Change By:
Reid Vandewiele
Facter 4 introduced compositive fact structuring via dot-notation as a feature. However, the dot-notation implementation used is incomplete, and behaves differently from dot-notation elsewhere in the ecosystem.Specifically, Facter 4 dot-notation splits key segments incorrectly, because it does not recognize the use of double or single quotes to indicate keys which contain literal dot characters.The reference implementation for dot-notation is found in Puppet, [here|https://github.com/puppetlabs/puppet/blob/85bd9ed07e3e6c956f1972624a50be914292e1ab/lib/puppet/pops/lookup/sub_lookup.rb#L6-L44].*Today's behavior*Consider the following plain-text custom fact file:{code}foo.bar._one_=1foo.bar.two=2foo."i.have.dots"=3"me.too"=4{code}Today, Facter returns the following for these facts.{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"\"i": { "have": {"dots\"": "3" }} }, "\" foo me ": {"too\"": "4" }}{code}This is incorrect.*Correct behavior*Full and correct support for dot-notation SHOULD give:{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"i.have.dots": "3" }, "me.too": "4"}{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-3000) Dot notation implemented in Facter 4 is incomplete
Title: Message Title
Reid Vandewiele updated an issue
Facter / FACT-3000
Dot notation implemented in Facter 4 is incomplete
Change By:
Reid Vandewiele
Facter 4 introduced compositive fact structuring via dot-notation as a feature. However, the dot-notation implementation used is incomplete, and behaves differently from dot-notation elsewhere in the ecosystem.Specifically, Facter 4 dot-notation splits key segments incorrectly, because it does not recognize the use of double or single quotes to indicate keys which contain literal dot characters.The reference implementation for dot-notation is found in Puppet, [here|https://github.com/puppetlabs/puppet/blob/85bd9ed07e3e6c956f1972624a50be914292e1ab/lib/puppet/pops/lookup/sub_lookup.rb#L6-L44].*Today's behavior*Consider the following plain-text custom fact file:{code}foo.bar._one_=1foo.bar.two=2foo." I i . Have have . Dots dots "=3"me.too"=4{code}Today, Facter returns the following for these facts.{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"\"i": { "have": {"dots\"": "3" }} }, "\"foo": {"too\"": "4" }}{code}This is incorrect.*Correct behavior*Full and correct support for dot-notation SHOULD give:{code:json}{ "foo": {"bar": { "one": "1", "two": "2"},"i.have.dots": "3" }, "me.too": "4"}{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-3000) Dot notation implemented in Facter 4 is incomplete
Title: Message Title Reid Vandewiele created an issue Facter / FACT-3000 Dot notation implemented in Facter 4 is incomplete Issue Type: Bug Assignee: Unassigned Created: 2021/03/26 12:57 PM Priority: Normal Reporter: Reid Vandewiele Facter 4 introduced compositive fact structuring via dot-notation as a feature. However, the dot-notation implementation used is incomplete, and behaves differently from dot-notation elsewhere in the ecosystem. Specifically, Facter 4 dot-notation splits key segments incorrectly, because it does not recognize the use of double or single quotes to indicate keys which contain literal dot characters. The reference implementation for dot-notation is found in Puppet, here. Today's behavior Consider the following plain-text custom fact file: foo.bar._one_=1 foo.bar.two=2 foo."I.Have.Dots"=3 "me.too"=4 Today, Facter returns the following for these facts.
Jira (PUP-10996) Add 'scripts' directory to Puppet Module type
Title: Message Title Lucy Wyman created an issue Puppet / PUP-10996 Add 'scripts' directory to Puppet Module type Issue Type: Improvement Assignee: Lucy Wyman Created: 2021/03/26 11:39 AM Priority: Normal Reporter: Lucy Wyman Based on this Bolt Github issue. This change is expected to impact all Puppet modules and enable loading scripts from the scripts/ directory of a Puppet module. https://github.com/puppetlabs/bolt/issues/2729 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-5070) Determine query that provides (dotted) factpaths
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5070 Determine query that provides (dotted) factpaths Change By: Austin Blatt Fix Version/s: PDB n/a Release Notes: Not Needed 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.392629.1616610675000.175285.1616776980039%40Atlassian.JIRA.
Jira (FACT-2987) Facter 4 outputs hypervisors.zone_id fact differently on Solaris
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-2987 Facter 4 outputs hypervisors.zone_id fact differently on Solaris Change By: Luchian Nemes Assignee: Luchian Nemes 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.391214.1615904193000.175231.1616774460031%40Atlassian.JIRA.
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title Gabriel Nagy commented on FACT-2996 Re: Performance regression gathering networking facts in facter 4.x What I could imagine is, that it is searching for a default route and fails because there isn't any on this system. Hmm, that undefined method `each' for nil:NilClass error could be what you are saying. You can email me the logs at gabriel.nagy [at] puppet.com. Just to be on the safe side, could you also provide logs for a Facter 3 debug run, and the outputs of ip route show and ip -6 route show (if applicable). I'm assuming ip route get default doesn't return anything on your system? Thanks 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.392713.1616618206000.175197.1616772300280%40Atlassian.JIRA.
Jira (FACT-2999) Facter cannot autoload provider from stdlib inside puppetserver repl
Title: Message Title Maggie Dreyer created an issue Facter / FACT-2999 Facter cannot autoload provider from stdlib inside puppetserver repl Issue Type: Bug Assignee: Unassigned Created: 2021/03/26 8:21 AM Priority: Normal Reporter: Maggie Dreyer When starting puppetserver from the repl, I get the following stack trace while trying to resolve facts: 2021-03-26 08:10:19,454 ERROR [clojure-agent-send-pool-0] [puppetserver] Facter error while resolving custom facts in /Users/aileen/.puppetlabs/opt/puppet/cache/lib/facter/service_provider.rb Could not autoload puppet/provider/service/upstart: Could not autoload puppet/provider/service/debian: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass backtrace: /Users/aileen/code/server/puppetserver/ruby/puppet/lib/puppet/provider/service/init.rb:24:in `block in ' org/jruby/RubyModule.java:3249:in `module_eval' /Users/aileen/code/server/puppetserver/ruby/puppet/lib/puppet/util/classgen.rb:132:in `genthing'
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title André Keller commented on FACT-2996 Re: Performance regression gathering networking facts in facter 4.x Hi Gabriel, Is there a way I can share the debug log with you, without having to share it publicly here? Having a closer look at the debug log it seems that it does not do it once per interface, but once per fact. f.e. [2021-03-26 15:59:16.664573 ] DEBUG Facter::Resolvers::Linux::Networking - Could not resolve dhcp, got undefined method `each' for nil:NilClass [2021-03-26 15:59:43.926525 ] DEBUG Facter::Resolvers::Linux::Networking - Could not resolve netmask6, got undefined method `each' for nil:NilClass [2021-03-26 16:00:11.381382 ] DEBUG Facter::Resolvers::Linux::Networking - Could not resolve network6, got undefined method `each' for nil:NilClass [2021-03-26 16:00:38.451925 ] DEBUG Facter::Resolvers::Linux::Networking - Could not resolve ip, got undefined method `each' for nil:NilClass ... After each of those occurances it goes over the whole interfaces again and at the end, it will do ip route show/ip -6 route show. The debug log does not say what it is actually looking for in the routing table though. What I could imagine is, that it is searching for a default route and fails because there isn't any on this system. I'm happy to provide the debug log, but I'd rather not sure it publicly here. Regards André Add Comment
Jira (FACT-2983) Facter 4 outputs ldom facts differently on Solaris SPARC
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-2983 Facter 4 outputs ldom facts differently on Solaris SPARC Change By: Gabriel Nagy Assignee: Gabriel Nagy 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.391210.1615903111000.175155.1616771040048%40Atlassian.JIRA.
Jira (FACT-2993) Facter 4.0.52 does not provide trusted['hostname'] in Docker environments
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2993 Facter 4.0.52 does not provide trusted['hostname'] in Docker environments Change By: Mihai Buzgau Labels: community 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.391951.1616498838000.175057.1616765880078%40Atlassian.JIRA.
Jira (FACT-2998) Facter breaks when querying for custom facts
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2998
Facter breaks when querying for custom facts
Change By:
Gheorghe Popescu
When you query for a custom structured fact, Facter uses Hash#dig to cicle through keys, but this can fail if the value of one of the cicled keys is not a Hash.Simple ruby example:{code:ruby}❯ ruby -e '{"a" => "b"}.dig("a", "z")'Traceback (most recent call last): 1: from -e:1:in `'-e:1:in `dig': String does not have #dig method (TypeError){code}Steps to reproduce in Facter:1. create a custom fact{code:ruby}Facter.add('foo.bar') do setcode { 'baz' }end{code}Query for that fact name and an extra key:{code:ruby}❯ bx facter foo.bar.xfacter-4.0.52/lib/facter/framework/formatters/formatter_helper.rb:28:in `dig': String does not have #dig method (TypeError){code}Same for Facter.value{code:ruby}2.7.2 :001 > require 'facter'2.7.2 :003 > Facter.value('foo.bar.x')facter-4.0.52/lib/facter/models/fact_collection.rb:22:in `block in value'NoMethodError (undefined method `fetch' for "baz":String){code}Another thing is that even for core facts, Facter ignores parts of the query, if it is partial matched:{code:ruby}❯ bx facter os.family.xyzDarwin2.7.2 :006 > Facter.value('os.family.a.b') => "Darwin"{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2998) Facter breaks when querying for custom facts
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2998
Facter breaks when querying for custom facts
Change By:
Gheorghe Popescu
When you query for a custom structured fact, Facter uses Hash#dig to cicle through keys, but this can fail if the value of one of the cicled keys is not a Hash.Simple ruby example:{code:ruby}❯ ruby -e '{"a" => "b"}.dig("a", "z")'Traceback (most recent call last): 1: from -e:1:in `'-e:1:in `dig': String does not have #dig method (TypeError){code}Steps to reproduce in Facter:1. create a custom fact{code:ruby}Facter.add('foo.bar') do setcode { 'baz' }end{code}Query for that fact name and an extra key:{code:ruby}❯ bx facter foo.bar.xfacter-4.0.52/lib/facter/framework/formatters/formatter_helper.rb:28:in `dig': String does not have #dig method (TypeError){code}Same for Facter.value{code:ruby}2.7.2 :001 > require 'facter'2.7.2 :003 > Facter.value('foo.bar.x')facter-4.0.52/lib/facter/models/fact_collection.rb:22:in `block in value'NoMethodError (undefined method `fetch' for "baz":String){code} Another thing is that for core facts, Facter ignores parts of the query, if it is partial matched:
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2998) Facter breaks when querying for custom facts
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2998
Facter breaks when querying for custom facts
Change By:
Gheorghe Popescu
When you query for a custom structured fact, Facter uses Hash#dig to cicle through keys, but this can fail if the value of one of the cicled keys is not a Hash.Simple ruby example:{code:ruby}❯ ruby -e '{"a" => "b"}.dig("a", "z")'Traceback (most recent call last): 1: from -e:1:in `'-e:1:in `dig': String does not have #dig method (TypeError){code}Steps to reproduce in Facter:1. create a custom fact{code:ruby}Facter.add('foo.bar') do setcode { 'baz' }end{code}Query for that fact name and an extra key:{code:ruby}❯ bx facter foo.bar.xfacter-4.0.52/lib/facter/framework/formatters/formatter_helper.rb:28:in `dig': String does not have #dig method (TypeError){code}Same for Facter.value{code:ruby}2.7.2 :001 > require 'facter'2.7.2 :003 > Facter.value('foo.bar.x')facter-4.0.52/lib/facter/models/fact_collection.rb:22:in `block in value'NoMethodError (undefined method `fetch' for "baz":String){code}Another thing is that for core facts, Facter ignores parts of the query, if it is partial matched: {code:ruby}❯ bx facter os.family.xyzDarwin2.7.2 :006 > Facter.value('os.family.a.b') => "Darwin"{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2998) Facter breaks when querying for custom facts
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2998
Facter breaks when querying for custom facts
Change By:
Gheorghe Popescu
When you query for a custom structured fact, Facter uses Hash#dig to cicle through keys, but this can fail if the value of one of the cicled keys is not a Hash.Simple ruby example:{code:ruby}❯ ruby -e '{"a" => "b"}.dig("a", "z")'Traceback (most recent call last): 1: from -e:1:in `'-e:1:in `dig': String does not have #dig method (TypeError){code}Steps to reproduce in Facter:1. create a custom fact{code:ruby}Facter.add('foo.bar') do setcode { 'baz' }end{code}Query for that fact name and an extra key:{code:ruby}❯ bx facter foo.bar.xfacter-4.0.52/lib/facter/framework/formatters/formatter_helper.rb:28:in `dig': String does not have #dig method (TypeError){code} Same for Facter.value {code:ruby}2.7.2 :001 > require 'facter'2.7.2 :003 > Facter.value('foo.bar.x')facter-4.0.52/lib/facter/models/fact_collection.rb:22:in `block in value'NoMethodError (undefined method `fetch' for "baz":String){code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2998) Facter breaks when querying for custom facts
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2998 Facter breaks when querying for custom facts Change By: Gheorghe Popescu Summary: CLI Facter breaks when querying for custom facts 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.392966.1616764289000.175046.1616764380028%40Atlassian.JIRA.
Jira (FACT-2998) CLI breaks when querying for custom facts
Title: Message Title
Gheorghe Popescu created an issue
Facter / FACT-2998
CLI breaks when querying for custom facts
Issue Type:
Bug
Affects Versions:
FACT 4.0.52
Assignee:
Unassigned
Created:
2021/03/26 6:11 AM
Priority:
Normal
Reporter:
Gheorghe Popescu
When you query for a custom structured fact, Facter uses Hash#dig to cicle through keys, but this can fail if the value of one of the cicled keys is not a Hash. Simple ruby example:
❯ ruby -e '{"a" => "b"}.dig("a", "z")'
Traceback (most recent call last):
1: from -e:1:in `'
-e:1:in `dig': String does not have #dig method (TypeError)
Steps to reproduce in Facter: 1. create a custom fact
Jira (FACT-2984) Facter 4 outputs mountpoints facts differently on macOS
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-2984 Facter 4 outputs mountpoints facts differently on macOS Change By: Luchian Nemes Assignee: Luchian Nemes 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.391211.1615903504000.175028.1616757540031%40Atlassian.JIRA.
Jira (PDB-5063) Stop returning stack traces from the API endpoint
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu PuppetDB / PDB-5063 Stop returning stack traces from the API endpoint 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.391374.1615936508000.175000.1616754540059%40Atlassian.JIRA.
Jira (FACT-2996) Performance regression gathering networking facts in facter 4.x
Title: Message Title Gabriel Nagy commented on FACT-2996 Re: Performance regression gathering networking facts in facter 4.x Hi André Keller, This shouldn't happen normally. I have 9 interfaces and in my case the routing table is read twice (there is room for improvement here to only read it once). It would help if you can provide us some debug logs with the affected Facter runs (such as facter networking --debug). 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.392713.1616618206000.174992.1616753520093%40Atlassian.JIRA.
Jira (PDB-5064) Handle \0x00 byte error and return a generic error message
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5064 Handle \0x00 byte error and return a generic error message Change By: Bogdan Irimie Sprint: ghost-7.04.2021 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.391375.1615936736000.174980.1616750880026%40Atlassian.JIRA.
Jira (PDB-5064) Handle \0x00 byte error and return a generic error message
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5064 Handle \0x00 byte error and return a generic error message Change By: Bogdan Irimie Team: HA 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.391375.1615936736000.174979.1616750400028%40Atlassian.JIRA.
Jira (PDB-5063) Stop returning stack traces from the API endpoint
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5063 Stop returning stack traces from the API endpoint Change By: Bogdan Irimie Sprint: ghost-7.04.2021 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.391374.1615936508000.174978.1616750220034%40Atlassian.JIRA.
Jira (PDB-5063) Stop returning stack traces from the API endpoint
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5063 Stop returning stack traces from the API endpoint Change By: Bogdan Irimie 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.391374.1615936508000.174977.1616749920033%40Atlassian.JIRA.
Jira (PUP-10974) service enable=mask fails when service isn't present
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10974 service enable=mask fails when service isn't present Change By: Mihai Buzgau Labels: community 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.392819.1616696402000.174954.1616741400033%40Atlassian.JIRA.
Jira (FACT-2994) selinux fact is not properly detected by Facter 4
Title: Message Title Mihai Buzgau assigned an issue to Gabriel Nagy Facter / FACT-2994 selinux fact is not properly detected by Facter 4 Change By: Mihai Buzgau Assignee: Mihai Buzgau Gabriel Nagy 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.391989.1616519382000.174953.1616741340109%40Atlassian.JIRA.
Jira (FACT-2997) Domain fact cannot be resolved on travis without ffi
Title: Message Title Mihai Buzgau assigned an issue to Gheorghe Popescu Facter / FACT-2997 Domain fact cannot be resolved on travis without ffi Change By: Mihai Buzgau Assignee: Gheorghe Popescu 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.392776.1616656236000.174952.1616741340050%40Atlassian.JIRA.
Jira (FACT-2997) Domain fact cannot be resolved on travis without ffi
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2997 Domain fact cannot be resolved on travis without ffi Change By: Mihai Buzgau 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.392776.1616656236000.174946.1616739240050%40Atlassian.JIRA.
Jira (FACT-2997) Domain fact cannot be resolved on travis without ffi
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2997 Domain fact cannot be resolved on travis without ffi Change By: Mihai Buzgau Sprint: NW - 2021-03-31 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.392776.1616656236000.174947.1616739240116%40Atlassian.JIRA.
