Jira (PDB-5070) Determine query that provides (dotted) factpaths
Title: Message Title
Josh Cooper commented on PDB-5070
Re: Determine query that provides (dotted) factpaths
Facter 3 creates core legacy facts where part of the name can include network interface names, block devices, etc so those need to be filtered out as well. For posterity, the query I came up with is:
{
"query":
["and",
["~", "name", ".*\\..*"],
["not",
["or",
["~", "name", "^blockdevice_.+_(model|size|vendor)"],
["~", "name", "^(ipaddress|macaddress|mtu|netmask|network)_"],
["~", "name", "^(ipaddress|macaddress|netmask|network|scope)6_"],
["~", "name", "^sp_"],
["~", "name", "^zone_.+_(brand|iptype|name|uuid|id|path|status)"]
]
]
Jira (PDB-5092) Investigate streaming response errors hanging clients
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5092 Investigate streaming response errors hanging clients Change By: Zachary Kent 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.393597.1617309451000.180261.1617316320034%40Atlassian.JIRA.
Jira (PDB-5092) Investigate streaming response errors hanging clients
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-5092 Investigate streaming response errors hanging clients Issue Type: Bug Assignee: Unassigned Created: 2021/04/01 1:37 PM Priority: Normal Reporter: Zachary Kent Testing the new explain analyze query param being added in PDB-5055 I noticed that validation errors were occurring when the param was included when querying routes under the query/v4. Top level queries against the v4 endpoint didn't cause an issue but queries against query/v4/resources would produce validation errors and cause the client making the request to hang. It also appeared that the database connection used for the query was stuck and not released after the error. We should investigate both the cause of the validation errors and why we didn't return an error response to the client. Add Comment
Jira (PDB-5092) Investigate streaming response errors hanging clients
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-5092 Investigate streaming response errors hanging clients Change By: Zachary Kent Assignee: Zachary Kent 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.393597.1617309451000.180169.1617309480108%40Atlassian.JIRA.
Jira (FACT-2983) Facter 4 outputs ldom facts differently on Solaris SPARC
Title: Message Title Josh Cooper commented on FACT-2983 Re: Facter 4 outputs ldom facts differently on Solaris SPARC Merged to main in d5433dcbd8f56852b90fc561276d937d4491ee90 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.179983.1617300480078%40Atlassian.JIRA.
Jira (FACT-2999) Facter cannot autoload provider from stdlib inside puppetserver repl
Title: Message Title Josh Cooper commented on FACT-2999 Re: Facter cannot autoload provider from stdlib inside puppetserver repl Passed in 24e47716d 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.392980.161677209.179981.1617300420853%40Atlassian.JIRA.
Jira (PUP-11000) Race condition with agent_disabled_lockfile
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11000 Race condition with agent_disabled_lockfile Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Fixes a race condition that could cause an agent to become disabled and no longer enforce desired state. 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.393433.1617190078000.179930.1617298920149%40Atlassian.JIRA.
Jira (FACT-3003) Don't split keys for already structured json/yaml external facts
Title: Message Title
Reid Vandewiele commented on FACT-3003
Re: Don't split keys for already structured json/yaml external facts
I did a think-through of this and came up with the following framing, which I think describes how we have implemented this functionality today. Adding a Fact There are three primary ways to add facts to Facter.
Via the Ruby API's Facter.add() method
Via a text-emitting external fact
Via a structured-object emitting external fact
For all three methods, the definition spec is the same. Input: A dot-notation insertion spec indicating where in the Fact tree the new value should appear. Output: The value which should appear at the designated insertion point. Examples Each of the following examples results in the following Fact tree.
{
"tier": "production",
"cmdb" {
"owner": "Jaime",
"raci": {
"responsible": "Jaime",
"informed": "Logan"
}
}
}
Jira (PUP-11000) Race condition with agent_disabled_lockfile
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11000 Race condition with agent_disabled_lockfile Change By: Josh Cooper Fix Version/s: PUP 7.6.0 Fix Version/s: PUP 6.22.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.393433.1617190078000.179913.1617298620077%40Atlassian.JIRA.
Jira (FACT-2985) Facter 4 outputs os.distro.description differently on Debian 9
Title: Message Title Josh Cooper commented on FACT-2985 Re: Facter 4 outputs os.distro.description differently on Debian 9 Facter 3 executes lsb_release -a, while Facter 4 parses /etc/os-release: root@smooth-pear:~# lsb_release -d Description: Debian GNU/Linux 9.0 (stretch) root@smooth-pear:~# grep PRETTY_NAME /etc/os-release PRETTY_NAME="Debian GNU/Linux 9 (stretch)" We should add a known limitation as this will affect puppet facts diff Claire Cadman Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2980) Facter 4 outputs the processors.speed fact differently on Linux
Title: Message Title
Josh Cooper commented on FACT-2980
Re: Facter 4 outputs the processors.speed fact differently on Linux
I think the intent is to report on the maximum speed, especially given the comment in https://github.com/puppetlabs/facter/blob/ce1f2bb4a91a1ac4ae5852091c96ae6ee3712e23/lib/src/facts/linux/processor_resolver.cc#L190. Interestingly Windows processor speed is omitted, but is included in the model description:
C:\> facter processors
{
count => 2,
isa => "x64",
models => [
"Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz",
"Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz"
],
physicalcount => 2
}
Jira (FACT-2964) Facter 4 outputs mountpoints facts differently on AIX
Title: Message Title Josh Cooper commented on FACT-2964 Re: Facter 4 outputs mountpoints facts differently on AIX It sounds like this is an bug in Facter 3? Can we add a known issue for this for users running puppet facts diff when upgrading to Facter 4/Puppet 7? Claire Cadman 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.390832.161555895.179838.1617295440240%40Atlassian.JIRA.
Jira (FACT-2963) Facter 4 outputs networking facts differently on AIX
Title: Message Title Josh Cooper commented on FACT-2963 Re: Facter 4 outputs networking facts differently on AIX Since AIX users will see this as a difference when running puppet facts diff, can we add this to as a known issue? Claire Cadman Are there plans to fix Facter 3.x so the difference goes away? 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.390824.1615557133000.179832.1617295260027%40Atlassian.JIRA.
Jira (FACT-3003) Don't split keys for already structured json/yaml external facts
Title: Message Title
Nick Walker commented on FACT-3003
Re: Don't split keys for already structured json/yaml external facts
If the users intent is to make a structured fact with a dot in the name of the fact there are 2 ways 1. ruby custom fact
Facter.add( "a.b" ) do
setcode do
{ c = true }
end
end
2. an external fact ( either a script of a json/yaml file )
{ "a.b": { "c": true } } Given these two examples it does not make sense to treat a json/yaml file on disk differently than the Facter.add example. If the users intent is to have a structured fact with dots in the name we have no way of knowing that from either of these examples. Both examples appear the same and both will result in the fact a = { b => { c => true } } } in Facter 4 which is new behavior compared to Facter 3 which would have made a.b = { c => true } . This ticket is closed as won't fix because we're assuming we want to keep the behavior of Facter 4 treating dots specially. If we want to revert that behavior it's a different request altogether.
Jira (FACT-3003) Don't split keys for already structured json/yaml external facts
Title: Message Title Nick Walker assigned an issue to Nick Walker Facter / FACT-3003 Don't split keys for already structured json/yaml external facts Change By: Nick Walker Assignee: Nick Walker 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.393500.1617226466000.179711.1617293640138%40Atlassian.JIRA.
Jira (PUP-11002) Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-11002
Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Change By:
Sean McDonald
Sprint:
Skeletor Ready to groom
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.393513.161723397.179526.1617288240613%40Atlassian.JIRA.
Jira (PDB-5043) Collect common PDB queries used in PE console pages
Title: Message Title Mihai Buzgau updated an issue PuppetDB / PDB-5043 Collect common PDB queries used in PE console pages Change By: Mihai Buzgau Labels: 2021-o1-kr2 c1 c3 c4 tsr-pdb-backlog 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.388381.1614031085000.179480.1617285840039%40Atlassian.JIRA.
Jira (PUP-11001) puppet module install shows invalid message if existing modules are broken
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11001 puppet module install shows invalid message if existing modules are broken Change By: Mihai Buzgau Issue Type: Bug Improvement 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.393444.1617202944000.179304.1617264006312%40Atlassian.JIRA.
Jira (FACT-2984) Facter 4 outputs mountpoints facts differently on macOS
Title: Message Title Luchian Nemes updated an issue Facter / FACT-2984 Facter 4 outputs mountpoints facts differently on macOS Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Certain mountpoints.options facts on macOSX were found to be differently represented in Facter 4 than Facter 3. This fix aligns them accordingly. 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.179303.1617261480061%40Atlassian.JIRA.
