Jira (PUP-10653) Remove the Dir monkey-patch from Puppet if not used
Title: Message Title Josh Cooper commented on PUP-10653 Re: Remove the Dir monkey-patch from Puppet if not used Passed CI in e2a883df7e 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.370869.1598950845000.36007.1600133520024%40Atlassian.JIRA.
Jira (PUP-10509) Drop support for ruby < 2.5
Title: Message Title Josh Cooper commented on PUP-10509 Re: Drop support for ruby < 2.5 Passed CI in e2a883df7e 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.358867.1589476926000.36006.1600133460022%40Atlassian.JIRA.
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting when using server_list
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10648 puppet 6 agent doesn't honor usecacheonfailure setting when using server_list 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.370505.1598545662000.36004.1600133340043%40Atlassian.JIRA.
Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting when using server_list
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10648 puppet 6 agent doesn't honor usecacheonfailure setting when using server_list 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.370505.1598545662000.36005.1600133340061%40Atlassian.JIRA.
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10664 Puppet 6 should log connection error details when a functional puppet master cannot be located Change By: Josh Cooper Fix Version/s: PUP 6.19.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.371698.1599857641000.36003.1600133220100%40Atlassian.JIRA.
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10664 Puppet 6 should log connection error details when a functional puppet master cannot be located 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.371698.1599857641000.35997.1600130760031%40Atlassian.JIRA.
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title Josh Cooper commented on PUP-10664 Re: Puppet 6 should log connection error details when a functional puppet master cannot be located There are two parts to this: 1. The current intended behavior is to not log errors if we eventually find a server to connect to. In other words, only log the exceptions at the error level if we exhaust the server list: $ bx puppet agent -t --server_list localhost:8141,localhost:8140 Info: Using configured environment 'production' Info: Retrieving pluginfacts .. But if you run with debugging you'll see the first failure followed by the second success: $ bx puppet agent -td --server_list localhost:8141,localhost:8140 ... Debug: Resolving service 'puppet' using Puppet::HTTP::Resolver::ServerList Debug: Creating new connection for https://localhost:8141 Debug: Starting connection for https://localhost:8141 Debug: Unable to connect to server from server_list setting: Request to https://localhost:8141/status/v1/simple/master failed after 0.002 seconds: Failed to open TCP connection to
Jira (PDB-4892) Summary query for catalog_inputs unecessarily slow
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4892 Summary query for catalog_inputs unecessarily slow Issue Type: Improvement Affects Versions: PDB 6.9.1 Assignee: Unassigned Created: 2020/09/14 4:34 PM Priority: Normal Reporter: Austin Blatt The summary query for catalog_inputs unecessarily queries the catalog_inputs table when all of its data is in the certnames table. This results in a summary query that is much more slow than the other groups. 2020-09-11T06:22:53.500Z INFO [sync] --> transferred catalogs (0) from https://uklvasapp715.gdc.standardchartered.com:8081/pdb/query/v4/catalogs in 2,960 ms 2020-09-11T06:23:02.803Z INFO [sync] --> transferred factsets (2) from https://uklvasapp715.gdc.standardchartered.com:8081/pdb/query/v4/factsets in 9,303 ms 2020-09-11T06:23:06.081Z INFO [sync] --> transferred reports (0) from https://uklvasapp715.gdc.standardchartered.com:8081/pdb/query/v4/reports in 3,277 ms 2020-09-11T06:24:09.596Z INFO [sync] --> transferred catalog-inputs (0)
Jira (PDB-4872) Provide certificate-allowlist and facts-blocklist as config aliases
Title: Message Title Zachary Kent commented on PDB-4872 Re: Provide certificate-allowlist and facts-blocklist as config aliases Thanks Nick Burgan, We need to expose another setting in p-e-m we added recently, so I can make the harmful language switch at the same time. Should get a PR up tomorrow or Wednesday. 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.370301.1598463666000.35632.1600114380088%40Atlassian.JIRA.
Jira (PUP-9971) Add ETag support to the source attribute of the file resource type for http
Title: Message Title
Josh Cooper commented on PUP-9971
Re: Add ETag support to the source attribute of the file resource type for http
file { '/tmp/file.txt':
ensure => file,
source => 'http://httpstat.us/200',
checksum => 'sha256',
checksum_value => 'f9bafc82ba5f8fb02b25020d66f396860604f496ca919480147fa525cb505d88',
}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4881) Add primary key to catalog_inputs
Title: Message Title Austin Blatt commented on PDB-4881 Re: Add primary key to catalog_inputs We can add a pkey to the table on-the-fly with this CREATE UNIQUE INDEX CONCURRENTLY catalog_inputs_type_name_certnameid_idx ON catalog_inputs (type, name, certname_id); ALTER TABLE catalog_inputs ADD CONSTRAINT catalog_inputs_pkey PRIMARY KEY USING INDEX catalog_inputs_type_name_certnameid_idx; 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.371421.1599665914000.35490.1600108620120%40Atlassian.JIRA.
Jira (PDB-4881) Add primary key to catalog_inputs
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4881
Add primary key to catalog_inputs
Change By:
Austin Blatt
When scoping this feature we specifically omitted any work to optimize storage/queries in order to limit the first round work. By doing this we also omitted a primary key, which means the table cannot be cleaned up by {{pg_repack}}. We should add a primary key to the table.I believe this would work as a primary key.{code}ALTER TABLE catalog_inputs ADD CONSTRAINT catalog_inputs_pkey PRIMARY KEY ( certname_id, type, name , certname_id );{code}If we allow customers to add it ahead of time as a workaround, we'll need to preface the {{ADD CONSTRAINT}} command in the migration with the below command to drop the primary key because {{ADD CONSTRAINT}} doesn't support {{IF NOT EXISTS}}.{code}ALTER TABLE catalog_inputs DROP CONSTRAINT IF EXISTS catalog_inputs_pkey;{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you
Jira (PDB-4872) Provide certificate-allowlist and facts-blocklist as config aliases
Title: Message Title Nick Burgan commented on PDB-4872 Re: Provide certificate-allowlist and facts-blocklist as config aliases Things in the modules that will need changes when this is implemented (double check I didn't miss any, though): https://github.com/puppetlabs/puppet-enterprise-modules/blob/master/modules/puppet_enterprise/manifests/puppetdb/database_ini.pp#L112 https://github.com/puppetlabs/puppet-enterprise-modules/blob/master/modules/puppet_enterprise/manifests/puppetdb/database_ini.pp#L117 https://github.com/puppetlabs/puppet-enterprise-modules/blob/d63b11863f7c3b016e0c78cb5709cc5c841da042/modules/puppet_enterprise/manifests/profile/puppetdb.pp#L82 https://github.com/puppetlabs/puppet-enterprise-modules/blob/07a1ba6d5bd88c39fd4c3e8700737ac57c372eff/modules/puppet_enterprise/manifests/puppetdb/jetty_ini.pp#L130 https://github.com/puppetlabs/puppet-enterprise-modules/blob/master/modules/puppet_enterprise/manifests/certs/puppetdb_allowlist.pp#L24 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-9971) Add ETag support to the source attribute of the file resource type for http
Title: Message Title beliys commented on PUP-9971 Re: Add ETag support to the source attribute of the file resource type for http Can you show an example of how I can do without ETag in the example above? 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.321721.1566385045000.35277.1600101660021%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Zachary Kent commented on PDB-4876 Re: Metrics endpoint broken great, thank you for testing that! 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.370980.1599053609000.35272.1600101540029%40Atlassian.JIRA.
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10664 Puppet 6 should log connection error details when a functional puppet master cannot be located 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.371698.1599857641000.35198.1600095540033%40Atlassian.JIRA.
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title Henrik Lindberg commented on PUP-10665 Re: Add weak dependencies to puppet resources Is the case "resource must be there, but don't propagate errors" valid? Seems like optionally_requires and do_not_propagate are separate things. Maybe these concepts are: optionally_before, optionaly_after (since optionally_require is a bit of an oxymoron) - this is a soft dependency, no error if missing isolated_before, isolated_after - this does not propagate errors (isolated == isolated from errors) and implies optionality unless resource is also listed as required. Just a thought. 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.371714.1599956556000.35178.1600094280037%40Atlassian.JIRA.
Jira (PUP-10666) puppet-agent config option require message for disable
Title: Message Title Pat Riehecky created an issue Puppet / PUP-10666 puppet-agent config option require message for disable Issue Type: New Feature Assignee: Unassigned Created: 2020/09/14 7:14 AM Priority: Normal Reporter: Pat Riehecky Hello, Could a config option be added for the puppet agent to require a message when running `puppet agent --disable`? For larger sites with multiple admins, it would be helpful to have a way to force this best practice. I don't expect it to stop `puppet agent --disable ' '` but in that instance the admin knows they are leaving a useless message against the policy. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2327) Extend Facter 4.x API with list
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2327 Extend Facter 4.x API with list Change By: Andrei Filipovici Assignee: Andrei Filipovici 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.344093.1580306326000.35131.1600087980029%40Atlassian.JIRA.
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title
Trevor Vaughan updated an issue
Puppet / PUP-10665
Add weak dependencies to puppet resources
Change By:
Trevor Vaughan
After [a long discussion in Slack|https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1599682853112600], I was asked to create a ticket around adding 'weak dependencies' to puppet resources. Weak dependencies work like the {{wants}} keyword in {{systemd}} in that resources will be ordered after other resources that they {{want}} but failures in earlier resources will not cause cascading errors into resources that {{want}} them.This would be useful in cases like the {{yumrepo}} resource which may cascade down to packages that do not actually reside in that repository.Per the Slack discussion, it looks like implementing this in the compiler is going to be the best case for backwards compatibility and could constitute a non-breaking feature enhancement. An example of what this might look like is:{code}file { '/tmp/foo': owner => 'root', mode => '0640', requires => [ File['/tmp'], Exec['foo'] ] wants => [ File['/etc/bar'], Exec['baz'] ]}{code}In this case, {{requires}} would work as usual and {{wants}} would use the resource if present, ignore it if not, and not cascade resource failures.If something exists in both {{requires}} and {{wants}} then the stronger dependency ({{requires}}) should win.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2319) Extend Facter 4.x API with debugonce
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2319 Extend Facter 4.x API with debugonce Change By: Andrei Filipovici Assignee: Andrei Filipovici 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.344085.1580306094000.35109.1600083960045%40Atlassian.JIRA.
Jira (PUP-10642) Uppercase Default value in conditional documentation a typo?
Title: Message Title Claire Cadman assigned an issue to Claire Cadman Puppet / PUP-10642 Uppercase Default value in conditional documentation a typo? Change By: Claire Cadman Assignee: 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.370111.159834180.35073.1600076520075%40Atlassian.JIRA.
Jira (PUP-10642) Uppercase Default value in conditional documentation a typo?
Title: Message Title Claire Cadman commented on PUP-10642 Re: Uppercase Default value in conditional documentation a typo? Thanks Henrik Lindberg! 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.370111.159834180.35071.1600076460035%40Atlassian.JIRA.
Jira (PDB-4876) Metrics endpoint broken
Title: Message Title Elof Ofel commented on PDB-4876 Re: Metrics endpoint broken Confirmed in the open-source version (in this case, puppetdb 5.2.15-1stretch). #grep ^CONFIG /etc/default/puppetdb CONFIG="/etc/puppetlabs/puppetdb/conf.d" I created the metrics.conf file above in this dir and ran 'systemctl restart puppetdb'. Now the v1 endpoint respond to queries again. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2320) Extend Facter 4.x API with warnonce
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2320 Extend Facter 4.x API with warnonce Change By: Andrei Filipovici Assignee: Andrei Filipovici 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.344086.1580306119000.35064.1600074300039%40Atlassian.JIRA.
