Jira (PDB-5105) Benchmark console query performance and identify slow queries
Title: Message Title Zachary Kent commented on PDB-5105 Re: Benchmark console query performance and identify slow queries Related to this ticket CD4PE has gathered some of the common PDB queries they use in a Google doc linked to CDPE-4097. That should be another source of possible queries we could help improve. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395324.161841225.10608.1618514160178%40Atlassian.JIRA.
Jira (PDB-5108) [SPIKE] Protect pdb against data that will cause it to fall over
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5108 [SPIKE] Protect pdb against data that will cause it to fall over Change By: Zachary Kent Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395635.1618512193000.10602.1618513680167%40Atlassian.JIRA.
Jira (PDB-5108) [SPIKE] Protect pdb against data that will cause it to fall over
Title: Message Title Margaret Lee created an issue PuppetDB / PDB-5108 [SPIKE] Protect pdb against data that will cause it to fall over Issue Type: Improvement Assignee: Unassigned Created: 2021/04/15 11:43 AM Priority: Normal Reporter: Margaret Lee Customers that are implementing CIS benchmarks have long fact names that are causing pdb to fall over. We should limit the length/size of resource names to hopefully prevent this from happening (Margaret to sync with Carl on this), but we should also try to better protect the pdb service from loading submitted data into memory that is too large. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-5094) Add some initial query tests
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5094 Add some initial query tests Change By: Bogdan Irimie Labels: 2021-o1-kr2 c3 c4 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394361.1617754897000.10450.1618508040143%40Atlassian.JIRA.
Jira (PDB-5105) Benchmark console query performance and identify slow queries
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5105 Benchmark console query performance and identify slow queries Change By: Bogdan Irimie Labels: 2021-o1-kr2 c1 c3 c4 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395324.161841225.10449.1618508040136%40Atlassian.JIRA.
Jira (PDB-5105) Benchmark console query performance and identify slow queries
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5105 Benchmark console query performance and identify slow queries Change By: Bogdan Irimie Labels: 2021-o1-kr2 c3 c4 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395324.161841225.10451.1618508040152%40Atlassian.JIRA.
Jira (PDB-5094) Add some initial query tests
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5094 Add some initial query tests Change By: Bogdan Irimie Labels: 2021-o1-kr2 c1 c3 c4 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394361.1617754897000.10448.1618508040076%40Atlassian.JIRA.
Jira (PDB-5107) Investigate PDB work required for PE-31775
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5107 Investigate PDB work required for PE-31775 Change By: Zachary Kent Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395626.1618504388000.10360.1618504440264%40Atlassian.JIRA.
Jira (PDB-5107) Investigate PDB work required for PE-31775
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-5107 Investigate PDB work required for PE-31775 Issue Type: Bug Assignee: Unassigned Created: 2021/04/15 9:33 AM Priority: Normal Reporter: Zachary Kent In the comments of PE-31775 it looks like the PDB terminus is holding duplicate copies of entity data in memory during command submission to PDB. We need to look into this issue and see if there is a way to restructure things to avoid holding multiple copies of the command data in-mem at the same time. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-2590) /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2590 /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini Change By: Rob Browning Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.125421.146001330.10350.1618504200060%40Atlassian.JIRA.
Jira (PDB-2590) /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2590 /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini Change By: Rob Browning Story Points: 2 Team: HA Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.125421.146001330.10349.1618504140089%40Atlassian.JIRA.
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 Release Notes: Bug Fix Release Notes Summary: Some previous versions of The ssl-setup command might insert a duplicate setting into the jetty.ini file like this `client-auth = want = client-auth = want`. The problem can be addressed by removing the duplication, changing that line to `client-auth = want`. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.10341.1618504020029%40Atlassian.JIRA.
Jira (PDB-5084) Fix ssl-setup client-auth insinuation
Title: Message Title Rob Browning commented on PDB-5084 Re: Fix ssl-setup client-auth insinuation Yes, PDB-2590 appears likely to still be a problem. We'll plan to fix it soon too. Thanks. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.10340.1618503660030%40Atlassian.JIRA.
Jira (PUP-11027) Filesync'd Augeas lenses should not overwrite system lenses
Title: Message Title Josh Cooper commented on PUP-11027 Re: Filesync'd Augeas lenses should not overwrite system lenses I'm not aware of anything in the pluginsync logic that could cause lenses to be written to somewhere other than Puppet[:libdir] directory. We recently had some issues with the augeas_core module, relating to updating the load path used to find augeas lenses (MODULES-7397 or MODULES-10950), maybe related? What version of puppet-agent and puppetlabs-augeas_core module are you using? Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395618.1618496225000.10329.1618502100031%40Atlassian.JIRA.
Jira (PUP-11022) Running `bundle exec rake/rspec spec` has failures on main branch
Title: Message Title Josh Cooper commented on PUP-11022 Re: Running `bundle exec rake/rspec spec` has failures on main branch Passed puppet#6a2b997499 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394276.1617737537000.10320.1618501680023%40Atlassian.JIRA.
Jira (PUP-7559) puppet doesn't specify file type to get default selinux context
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7559 puppet doesn't specify file type to get default selinux context Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.191580.1495040547000.10319.1618501620169%40Atlassian.JIRA.
Jira (PUP-7559) puppet doesn't specify file type to get default selinux context
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7559 puppet doesn't specify file type to get default selinux context Change By: Josh Cooper Assignee: Tobias Urdin Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.191580.1495040547000.10317.1618501620063%40Atlassian.JIRA.
Jira (PUP-7559) puppet doesn't specify file type to get default selinux context
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7559 puppet doesn't specify file type to get default selinux context Change By: Josh Cooper Team: Night's Watch Coremunity Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.191580.1495040547000.10318.1618501620124%40Atlassian.JIRA.
Jira (PDB-5021) Investigate factsets getting repeatedly pulled in sync with benchmark data
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-5021 Investigate factsets getting repeatedly pulled in sync with benchmark data Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.386997.1612983565000.10311.1618500540028%40Atlassian.JIRA.
Jira (PDB-5106) Update AST query documentation
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-5106 Update AST query documentation Change By: Zachary Kent Epic Link: PDB-4759 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395610.1618487178000.10271.1618497120163%40Atlassian.JIRA.
Jira (PUP-11027) Filesync'd Augeas lenses should not overwrite system lenses
Title: Message Title Trevor Vaughan created an issue Puppet / PUP-11027 Filesync'd Augeas lenses should not overwrite system lenses Issue Type: Bug Affects Versions: PUP 7.4.1 Assignee: Unassigned Components: Modules Created: 2021/04/15 7:17 AM Priority: Normal Reporter: Trevor Vaughan Puppet Version: All Puppet Server Version: All OS Name/Version: All It looks like augeas lenses that are filesync'd over to target nodes are placed into the default augeas path of /usr/share/augeas/lenses. Unfortunately, it doesn't seem to make them readable by all users which means that regular users may have augtool fail if the lens is not made world readable somehow. Desired Behavior: I would like Puppet sync'd lenses to be placed into a puppet-specific location and have the internal Augeas libraries use that path first so that system libraries are not altered. Add Comment
Jira (FACT-3020) Invalid value for NVMe partitions on Facter 3
Title: Message Title
Mihai Buzgau created an issue
Facter / FACT-3020
Invalid value for NVMe partitions on Facter 3
Issue Type:
Bug
Assignee:
Unassigned
Components:
Facter 3
Created:
2021/04/15 6:39 AM
Labels:
knownissue
Priority:
Normal
Reporter:
Mihai Buzgau
Invalid values for NVMe mountpoints on Facter 3. puppet facts show mountpoints./ { "mountpoints./": { "available": "5.74 GiB", "available_bytes": 6161899520, "capacity": "24.24%", "device": "PARTUUID=4ef7520f-474e-4d3e-a298-fe71ee0e99c5", "filesystem": "ext4", "options": [ "rw", "relatime", "discard" ], "size": "7.59 GiB", "size_bytes": 8150749184, "used": "1.84 GiB", "used_bytes": 1972072448 } device should be "/dev/nvme0n1p1"and mount should be set to "/"
Add Comment
Jira (FACT-3019) Facter 3 does not detect partion fact on RedHat7 AARCH
Title: Message Title Mihai Buzgau created an issue Facter / FACT-3019 Facter 3 does not detect partion fact on RedHat7 AARCH Issue Type: Bug Assignee: Unassigned Created: 2021/04/15 6:31 AM Labels: knownissue Priority: Normal Reporter: Mihai Buzgau Facter 3 does not detect the following facts that are part of the partitions group: partitions./dev/sda1.filesystem partitions./dev/sda1.partlabel partitions./dev/sda1.partuuid partitions./dev/sda1.uuid partitions./dev/sda2.filesystem partitions./dev/sda2.partuuid partitions./dev/sda2.uuid partitions./dev/sda3.filesystem partitions./dev/sda3.partuuid partitions./dev/sda3.uuid partitions./dev/sda4.filesystem partitions./dev/sda4.partuuid partitions./dev/sda4.uuid
Jira (FACT-3018) DHCP server fact is not detected on Facter
Title: Message Title Claire Cadman updated an issue Facter / FACT-3018 DHCP server fact is not detected on Facter Change By: Claire Cadman Labels: doc_reviewed known-issue-added knownissue Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395613.1618492821000.10196.1618493280150%40Atlassian.JIRA.
Jira (FACT-3018) DHCP server fact is not detected on Facter
Title: Message Title Claire Cadman updated an issue Facter / FACT-3018 DHCP server fact is not detected on Facter Change By: Claire Cadman Labels: known-issue-added knownissue Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395613.1618492821000.10195.1618493280105%40Atlassian.JIRA.
Jira (FACT-3018) DHCP server fact is not detected on Facter
Title: Message Title
Mihai Buzgau created an issue
Facter / FACT-3018
DHCP server fact is not detected on Facter
Issue Type:
Bug
Assignee:
Unassigned
Components:
Facter 3, Facter 4
Created:
2021/04/15 6:20 AM
Labels:
knownissue
Priority:
Normal
Reporter:
Mihai Buzgau
The DHCP server fact is not correctly detected by Facter: Facter 3 reports dhcp_servers as:
{
"dhcp_servers": ""
}
while Facter 4 reports this fact as:
{
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Issue Type: Task Assignee: Unassigned Created: 2021/04/15 6:19 AM Priority: Normal Reporter: Ciprian Badescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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
Jira (FACT-3015) Facter 3 cannot detect the VMware version
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3015 Facter 3 cannot detect the VMware version Change By: Mihai Buzgau Summary: Facter 3 cannot detect the VMware version . Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395604.1618474618000.10191.1618491600079%40Atlassian.JIRA.
Jira (FACT-3012) Facter 3 cannot resolve lsb facts if the lsb_release package is not installed
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3012 Facter 3 cannot resolve lsb facts if the lsb_release package is not installed Change By: Mihai Buzgau Facter 3 cannot resolve the following facts if the lsb_release package is not installed on the box : * lsbdistrelease * lsbmajdistrelease * os.distro.codename * os.distro.id * os.distro.release.full" * os.distro.release.majorThis was fixed in Facter 4 as part of this ticket https://tickets.puppetlabs.com/browse/FACT-2931 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395599.1618469827000.10186.1618491420029%40Atlassian.JIRA.
Jira (FACT-3012) Facter 3 cannot resolve lsb facts if the lsb_release package is not installed
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3012 Facter 3 cannot resolve lsb facts if the lsb_release package is not installed Change By: Mihai Buzgau Summary: Facter 3 cannot resolve lsb facts if the lsb_release package is not installed Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395599.1618469827000.10185.1618491360027%40Atlassian.JIRA.
Jira (FACT-3011) Facter 3 does not detect the type of xvda disks on Amazon 6 OSes
Title: Message Title
Mihai Buzgau updated an issue
Facter / FACT-3011
Facter 3 does not detect the type of xvda disks on Amazon 6 OSes
Change By:
Mihai Buzgau
Facter 3 does not detect the type of for xvda type disks on Amazon 6 VMs:Output from Puppet facts diff:{code:java} {"disks.xvda.type": { "new_value": "ssd", "old_value": null} }{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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.395598.1618469484000.10184.1618491300156%40Atlassian.JIRA.
Jira (PDB-5094) Add some initial query tests
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5094 Add some initial query tests Change By: Bogdan Irimie Labels: 2021-o1-kr2 c1 c3 c4 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394361.1617754897000.10173.1618490040028%40Atlassian.JIRA.
Jira (PDB-5094) Add some initial query tests
Title: Message Title Bogdan Irimie updated an issue PuppetDB / PDB-5094 Add some initial query tests Change By: Bogdan Irimie Team: Ghost Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394361.1617754897000.10172.1618489980196%40Atlassian.JIRA.
Jira (PUP-11025) Add OSX11 Big Sur support
Title: Message Title Victor Bobosila created an issue Puppet / PUP-11025 Add OSX11 Big Sur support Issue Type: Task Assignee: Unassigned Created: 2021/04/15 5:07 AM Priority: Normal Reporter: Victor Bobosila Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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
Jira (PDB-5106) Update AST query documentation
Title: Message Title Andrei Filipovici created an issue PuppetDB / PDB-5106 Update AST query documentation Issue Type: Task Assignee: Unassigned Created: 2021/04/15 4:46 AM Labels: query-engine-improvements Priority: Normal Reporter: Andrei Filipovici In the AST query language documentation update the following: ["~>", "path", ["array_fact", ".*"]] example should have 'array_fact' between <> The second implicit subquery example uses 'macaddresses' instead of 'macaddress'. The second explicit subquery has an extra ']' at the end. The fifth and the last explicit subquery example uses 'macaddresses' instead of 'macaddress'. All the order_by examples use the invalid field 'timestamp'. They should use 'receive_time', 'start_time' or 'producer_timestamp' Add Comment
Jira (FACT-3017) Add OSX11 Big Sur support
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3017 Add OSX11 Big Sur support Change By: Ciprian Badescu Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395609.1618486266000.10155.1618486320136%40Atlassian.JIRA.
Jira (FACT-3017) Add OSX11 Big Sur support
Title: Message Title Victor Bobosila created an issue Facter / FACT-3017 Add OSX11 Big Sur support Issue Type: Task Assignee: Unassigned Created: 2021/04/15 4:31 AM Priority: Normal Reporter: Victor Bobosila Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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
Jira (FACT-3017) Add OSX11 Big Sur support
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-3017 Add OSX11 Big Sur support Change By: Ciprian Badescu Sprint: NW-2021-04-28 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395609.1618486266000.10156.1618486320180%40Atlassian.JIRA.
Jira (FACT-3016) Facter 3 does not detect IP v6 facts on Solaris
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3016 Facter 3 does not detect IP v6 facts on Solaris Change By: Mihai Buzgau Summary: Facter 3 does not detect IP v6 facts on Solaris boxes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395605.1618475853000.10122.1618479060185%40Atlassian.JIRA.
Jira (PUP-11024) Cannot ensure dnfmodule with no default profile
Title: Message Title Claire Cadman updated an issue Puppet / PUP-11024 Cannot ensure dnfmodule with no default profile Change By: Claire Cadman Labels: doc_reviewed Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395286.1618384806000.10098.1618476900316%40Atlassian.JIRA.
Jira (PDB-5096) Add some initial command processing tests
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu PuppetDB / PDB-5096 Add some initial command processing tests Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394364.1617756098000.10085.1618476600241%40Atlassian.JIRA.
Jira (FACT-3016) Facter 3 does not detect IP v6 facts on Solaris boxes
Title: Message Title Mihai Buzgau created an issue Facter / FACT-3016 Facter 3 does not detect IP v6 facts on Solaris boxes Issue Type: Bug Assignee: Unassigned Components: Facter 3 Created: 2021/04/15 1:37 AM Labels: knownissue Priority: Normal Reporter: Mihai Buzgau Facter 3 does not provide information on the following facts on Solaris based VMs: ipaddress6_lo0 ipaddress6_net0 netmask6 netmask6_lo0 netmask6_net0 network6 network6_net0 networking.interfaces.lo0.bindings6.0.address networking.interfaces.lo0.bindings6.0.netmask networking.interfaces.lo0.ip6 networking.interfaces.lo0.netmask6 networking.interfaces.lo0.scope6 networking.interfaces.net0.bindings6.0.address networking.interfaces.net0.bindings6.0.netmask networking.interfaces.net0.bindings6.0.network
Jira (FACT-3013) Facter 3 does not detect scope6
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3013 Facter 3 does not detect scope6 Change By: Mihai Buzgau The scope6 fact was implemented in Facter 4 in this the following ticket: https://tickets.puppetlabs.com/browse/FACT-2843This fact is currently missing from Facter 3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395601.1618472604000.10026.1618474800035%40Atlassian.JIRA.
Jira (FACT-3015) Facter 3 cannot detect the VMware version.
Title: Message Title Mihai Buzgau created an issue Facter / FACT-3015 Facter 3 cannot detect the VMware version. Issue Type: Bug Assignee: Unassigned Components: Facter 3 Created: 2021/04/15 1:16 AM Labels: knownissue Priority: Normal Reporter: Mihai Buzgau For boxes running on ESXi, Facter 3 cannot detect the hypervisors.vmware.version fact Add Comment
Jira (PDB-5095) Add a tool to timeshift archive exports
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici PuppetDB / PDB-5095 Add a tool to timeshift archive exports Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394363.1617755355000.10012.1618473300043%40Atlassian.JIRA.
Jira (FACT-3014) Facter 3 does not detect hypervisor.kvm.amazon fact on Amazon VMs
Title: Message Title Mihai Buzgau created an issue Facter / FACT-3014 Facter 3 does not detect hypervisor.kvm.amazon fact on Amazon VMs Issue Type: Bug Assignee: Unassigned Components: Facter 3 Created: 2021/04/15 12:46 AM Labels: knownissue Priority: Normal Reporter: Mihai Buzgau The hypervisors.kvm.amazon is not detected by Facter 3 on Amazon 7 VMs Add Comment
Jira (FACT-3013) Facter 3 does not detect scope6
Title: Message Title Mihai Buzgau created an issue Facter / FACT-3013 Facter 3 does not detect scope6 Issue Type: Bug Assignee: Unassigned Components: Facter 3 Created: 2021/04/15 12:43 AM Labels: knownissue Priority: Normal Reporter: Mihai Buzgau The scope6 fact was implemented in Facter 4 in this ticket: https://tickets.puppetlabs.com/browse/FACT-2843 This fact is currently missing from Facter 3 Add Comment
Jira (PDB-5098) Data demo
Title: Message Title Bogdan Irimie assigned an issue to Florin Dragos PuppetDB / PDB-5098 Data demo Change By: Bogdan Irimie Assignee: Florin Dragos Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394472.1617807772000.10008.1618471620030%40Atlassian.JIRA.
Jira (FACT-3012) Facter 3 cannot resolve lsb facts if lsb_release is not installed
Title: Message Title Mihai Buzgau created an issue Facter / FACT-3012 Facter 3 cannot resolve lsb facts if lsb_release is not installed Issue Type: Bug Assignee: Unassigned Created: 2021/04/14 11:57 PM Labels: knownissue Priority: Normal Reporter: Mihai Buzgau Facter 3 cannot resolve the following facts if the lsb_release is not installed: lsbdistrelease lsbmajdistrelease os.distro.codename os.distro.id os.distro.release.full" os.distro.release.major This was fixed in Facter 4 as part of this ticket https://tickets.puppetlabs.com/browse/FACT-2931 Add Comment
Jira (FACT-3011) Facter 3 does not detect the type of xvda disks on Amazon 6 OSes
Title: Message Title
Mihai Buzgau created an issue
Facter / FACT-3011
Facter 3 does not detect the type of xvda disks on Amazon 6 OSes
Issue Type:
Bug
Assignee:
Unassigned
Components:
Facter 3
Created:
2021/04/14 11:51 PM
Labels:
knownissue
Priority:
Normal
Reporter:
Mihai Buzgau
Facter 3 does not detect the type of xvda type disks on Amazon 6 VMs: Output from Puppet facts diff:
{
"disks.xvda.type": {
"new_value": "ssd",
"old_value": null
Jira (FACT-3010) Facter 3 cannot detect some ldom facts
Title: Message Title
Mihai Buzgau created an issue
Facter / FACT-3010
Facter 3 cannot detect some ldom facts
Issue Type:
Bug
Assignee:
Unassigned
Components:
Facter 3
Created:
2021/04/14 11:43 PM
Priority:
Normal
Reporter:
Mihai Buzgau
Based on puppet facts diff, Facter 3 cannot resolve the following facts on Solaris 11-SPARC:
{
"ldom.domainchassis": {
"new_value": "AK00358110",
"old_value": "Unknown"
},
"ldom.domaincontrol": {
Jira (FACT-3004) Do not auto promote dotted facts to structured
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3004 Do not auto promote dotted facts to structured Change By: Gheorghe Popescu Release Notes Summary: Changes the way Facter 4 treats dots in fact names, reverting to the same behaviour as Facter 3. This means that by default, any dot in custom or external fact names will be considered as part of the fact name and not a delimiter for structured facts.This also adds a global setting ` autopromote force - dotted dot - facts resolution ` which can be set to enable the conversion of dotted facts to structured. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.393702.1617359453000.10003.1618467840032%40Atlassian.JIRA.
