Jira (PDB-3159) I'd like to access the performance dashboard over https
Title: Message Title Bogdan Irimie assigned an issue to Florin Dragos PuppetDB / PDB-3159 I'd like to access the performance dashboard over https Change By: Bogdan Irimie Assignee: Florin Dragos 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.159265.1478038793000.120737.1611214500027%40Atlassian.JIRA.
Jira (PDB-5001) PuppetDB Cli pupept-query command not respecting https_proxy environment variable
Title: Message Title zendesk.jira updated an issue PuppetDB / PDB-5001 PuppetDB Cli pupept-query command not respecting https_proxy environment variable Change By: zendesk.jira Zendesk Ticket Count: 1 Zendesk Ticket IDs: 42799 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.384070.1611213926000.120735.1611214260037%40Atlassian.JIRA.
Jira (PDB-5001) PuppetDB Cli pupept-query command not respecting https_proxy environment variable
Title: Message Title zendesk.jira updated an issue PuppetDB / PDB-5001 PuppetDB Cli pupept-query command not respecting https_proxy environment variable Change By: zendesk.jira Labels: jira_escalated 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.384070.1611213926000.120736.1611214260091%40Atlassian.JIRA.
Jira (PDB-5001) PuppetDB Cli pupept-query command not respecting https_proxy environment variable
Title: Message Title
Henry Wang updated an issue
PuppetDB / PDB-5001
PuppetDB Cli pupept-query command not respecting https_proxy environment variable
Change By:
Henry Wang
puppet-query doesn't respect environmental https_proxy settings like the other CLI commands. also we didn't find a way to configure it through CLI conf file. This will stop users who have to run this query behind a proxy. Way to reproduce: **{code:java} [root@puppetmom ~]# puppet-job show ID STATUS JOB TYPE TIMESTAMP TARGET - 537 finished puppet_agent::version 01/20/21 09:26:25 windowsagent.platform9.pupp... 536 finished puppet_agent::version 01/20/21 09:25:26 windowsagent.platform9.pupp... 535 finished puppet_agent::version 01/20/21 08:21:17 windowsagent.platform9.pupp...[root@puppetmom ~]# puppet-query "nodes[certname] { }" [ { "certname": "centosagentfor75.platform9.puppet.net" }, { "certname": " cm-lb01 cd4pemom75 .platform9.puppet.net"...{code}Once a dummy https_proxy is set, puppet-job will fail but puppet-query is not impacted:{code:java} [root@puppetmom ~]# export https_proxy=socks5h://localhost:12345[root@puppetmom ~]# puppet-job showRequest to 'https://puppetmom.platform9.puppet.net:8143/orchestrator/v1/jobs' failed: Couldn't connect to server[root@puppetmom ~]# puppet-query "nodes[certname] { }"[ {"certname": "centosagentfor75.platform9.puppet.net" }, {"certname": "puppetmom.platform9.puppet.net"{code}
Add Comment
Jira (PDB-5001) PuppetDB Cli pupept-query command not respecting https_proxy environment variable
Title: Message Title
Henry Wang created an issue
PuppetDB / PDB-5001
PuppetDB Cli pupept-query command not respecting https_proxy environment variable
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/01/20 11:25 PM
Priority:
Normal
Reporter:
Henry Wang
puppet-query doesn't respect environmental https_proxy settings like the other CLI commands. also we didn't find a way to configure it through CLI conf file. This will stop users who have to run this query behind a proxy. Way to reproduce:
[root@puppetmom ~]# puppet-job show ID STATUS JOB TYPE TIMESTAMP TARGET - 537 finished puppet_agent::version 01/20/21 09:26:25 windowsagent.platform9.pupp... 536 finished puppet_agent::version 01/20/21 09:25:26 windowsagent.platform9.pupp... 535 finished puppet_agent::version 01/20/21 08:21:17 windowsagent.platform9.pupp...
[root@puppetmom ~]# puppet-query "nodes[certname] { }" [ { "certname": "centosagentfor75.platform9.puppet.net" }, { "certname": "cm-lb01.platform9.puppet.net"
...
Jira (PUP-10766) Prepare release announcement (Puppet Platform 6.20.0)
Title: Message Title
Nirupama Mantha commented on PUP-10766
Re: Prepare release announcement (Puppet Platform 6.20.0)
The next release in the Puppet 6 series, Puppet 6.20.0, is now available! The release contains bug fixes and minor improvements, including: New features JSON terminus for node and report This release implements JSON termini for node and report indirection. The format of the last_run_report.yaml report can be affected by the cache setting key of the report terminus in the routes.yaml file. To ensure the file extension matches the content, update the lastrunreport configuration to reflect the terminus changes (lastrunreport = $statedir/last_run_report.json). PUP-10712 JSON terminus for facts This release adds a new JSON terminus for facts, allowing them to be stored and loaded as JSON. Puppet agents continue to default to YAML, but you can use JSON by configuring the agent application in routes.yaml. Puppet Server 7 also caches facts as JSON instead of YAML by default. You can re-enable the old YAML terminus in routes.yaml. PUP-10656 Multiple logdest locations in puppet.conf accepted You can set multiple logdest locations using a comma separated list. For example: /path/file1,console,/path/file2. PUP-10795 New serverport setting type The serverport setting is an alias for masterport. PUP-10725 The puppet module install command lists unsatisfiable dependencies If the puppet module install command fails, Puppet returns a more detailed error, including the unsatisfiable module(s) and its ranges. PUP-9176 Interpolation of sensitive values in EPP templates Previously, if you interpolated a sensitive value in a template, you were required to unwrap the sensitive value and rewrap the result. Now the epp and inline_epp functions automatically return a Sensitive value if any interpolated variables are sensitive. For example: inline_epp("Password is <%= Sensitive('opensesame') %>"). Note that these changes just apply to EPP templates, not ERB templates. PUP-8969 OpenSSL bumped to 1.1.1i This release bumps OpenSSL to 1.1.1i. PA-3513 Curl bumped to 7.74.0 This release bumps Curl to 7.74.0. PA-3512 (Experimental feature) puppet facts diff action This release adds a new action called puppet facts diff to check if there are differences between Facter 3 and Facter 4 outputs. Facts that change over time like memory and uptime are ignored. PUP-10815 Deprecations func3x_check setting removed The func3x_check setting has been removed. PUP-10724 Resolved issues The puppet apply command creates warnings This release eliminates Ruby 2.7.x warnings when running puppet apply with node statements. PUP-10845 Remove Pathname#cleanpath workaround This release removes an unnecessary workaround when cleaning file paths, as Ruby 1.9 is no longer supported. PUP-10840 Cached catalog contains the result of deferred evaluation instead of the deferred function Puppet 6.12.0 introduced a regression that caused the result of a deferred function to be stored in the cached catalog. As a result, an agent running with a cached catalog would not re-evaluate the deferred function. This is now fixed. PUP-10818 Calling scope#tags results in undefined method Previously, calling the tags method within an ERB template resulted in a confusing error message. The error message now makes it clear that this method is not supported. PUP-10779 Puppet agent installation fails when msgpack is enabled on puppetserver Previously, the agent failed to deserialize the catalog and fail the run if the msgpack gem was enabled but not installed. Now the agent only supports that format when the msgpack gem is installed in the agents vendored Ruby. PUP-10772 Setting facterng twi
Jira (PDB-4941) Evaluate current table-specific parameters (autovacuum, etc.)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4941 Evaluate current table-specific parameters (autovacuum, etc.) Change By: Zachary Kent Fix Version/s: PDB n/a 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.375746.160339316.120401.1611181740027%40Atlassian.JIRA.
Jira (PDB-4941) Evaluate current table-specific parameters (autovacuum, etc.)
Title: Message Title Zachary Kent commented on PDB-4941 Re: Evaluate current table-specific parameters (autovacuum, etc.) We currently set a table specific autovacuum_vacuum_scale_factor setting on the factset, catalog, and certnames tables. It is set to 0.75 on the catalog and certnames tables and 0.80 on the factset table. This setting controls the threshold of dead rows that must be hit before an autovacuum of the table will be scheduled. See Thresholds and Scale Factors section of the linked article for background info on this setting. This setting is toggled in two places depending on whether it is a FOSS or PE install. In FOSS the table settings are added in a migration here. In PE the settings are duplicated in the pe_databases::postgresql_settings::table_settings class. I believe setting the scale factor to 0.80 means that in a steady state assuming a 30 min agent run interval the table will get vacuumed every 24 mins and will bloat up to 44% dead space before being vacuumed. It was found, sometime in the past, that spacing out autovacuums in this way helped reduce CPU use for customers. See comments in this PR-2393 for related details. Setting the scale_factor this high seems to go against what's generally recommended in the PostgreSQL docs but given what was observed in the field it may be the right choice in our case. Another observation is that our update pattern being throttled by the agent run interval means there should usually be only ~ 1 dead row per certname in the tables mentioned above before they are vacuumed. We recently had issues with some customers related to table bloat and autovacuum not keeping up which lead to the creation of this ticket. See comments in PE-27630 for more detailed background on what was done to resolve these issues. To summarize the solution in that case, the autovacuum_vacuum_cost_limit was increased to allow the autovacuum workers to do more work before they were forced to sleep for autovacuum_vacuum_cost_delay. See this ZD-35697 ticket for background on the problem at a specific customer site. Note the excellent write up from Dylan Ratcliffe copied into the ZD ticket linked above about some of the debugging that was done to figure out this issue. One outstanding question that came from some of the recent changes mentioned above was about the impact of setting autovacuum_analyze_scale_factor to 0.04. This change was made when the autovacuum_vacuum_scale_factor was originally decreased from the default of 0.20 to 0.08. Later when the autovacuum_vacuum_scale_factor was increased to 0.80 the autovacuum_analyze_scale_factor remained set at 0.04. See here for where the pe_databases module sets this value. Some of the concerns voiced by Nick W. about this change can be found here in the slack history. It seems possible that we may want to increase the value of this setting back to the default of 0.10. In the steady state with a 30 min agent run interval we will be analyzing tables every ~72 seconds. There are some potential issues with this analyze process keeping a transaction held open and preventing clean up of some rows (see slack message linked above). We similarly decreased the autovacuum_analyze_scale_factor to 0.01 on the catalog_resources table recently see PDB-4640 for details. Regardless of any potential changes to the vacuum/analyze_scale_factors mentioned above, the changes we're making to no longer hold sync summary query transactions open should help to reduce the amount of dead rows which are ineligible for clean up during an autovacuum due to open transactions. Once the change to the sync summary queries is merged we should reach out to Support and see if they kno
Jira (PUP-10850) Puppet facts show doesn't have an option to opt out of legacy facts
Title: Message Title Kenyon Ralph commented on PUP-10850 Re: Puppet facts show doesn't have an option to opt out of legacy facts The release notes should be fixed then. "By default, puppet facts show displays all facts, including legacy facts. This release adds a --no-legacy option to disable legacy facts when querying all facts. PUP-10850" – https://puppet.com/docs/puppet/7.3/release_notes_puppet.html#release_notes_puppet 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.382858.1610379246000.120125.1611173280031%40Atlassian.JIRA.
Jira (FACT-2918) FACTER_ environmental facts overrides don't work with external facts
Title: Message Title Nick Walker commented on FACT-2918 Re: FACTER_ environmental facts overrides don't work with external facts Kenneth Pepiton thanks for the response. It wasn't clear from the description that this used to work and it is a regression. During triage we thought it never worked in Puppet. I was able to reproduce that it worked in PE 2018.1.10 and does not work in PE 2019.8.4. [root@master-masterbranch-centos ~]# puppet --version 6.20.0 [root@master-masterbranch-centos ~]# cat /opt/puppetlabs/server/pe_build 2019.8.5-rc2-160-g4af732b [root@master-masterbranch-centos ~]# FACTER_test_fact=blah puppet facts show | grep test "test_fact": "blah", [root@master-masterbranch-centos ~]# mkdir /etc/puppetlabs/facter [root@master-masterbranch-centos ~]# mkdir /etc/puppetlabs/facter/facts.d [root@master-masterbranch-centos ~]# vim /etc/puppetlabs/facter/facts.d/test_fact.txt [root@master-masterbranch-centos ~]# FACTER_test_fact=blah puppet facts show | grep test "test_fact": "foo",
Jira (PDB-5000) Triage SEC-274 for PuppetDB and PE-PuppetDB
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-5000
Triage SEC-274 for PuppetDB and PE-PuppetDB
Change By:
Austin Blatt
Triage and provide a response to the CVE's in SEC-274 for pupetdb and pe-puppetdb clojure dependencies{noformat}Determining actual impact to the application based on how the packages are being used is useful in applying the appropriate risk score therefore some assistance is needed in determining actual impact to the application ( ie, is the package utilizing the vulnerable paths). Please review the ticket (SEC-274) for details and comment responses regarding use of packages by 29 January 2021.{noformat}
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.
Jira (PDB-5000) Triage SEC-274 for PuppetDB and PE-PuppetDB
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-5000
Triage SEC-274 for PuppetDB and PE-PuppetDB
Change By:
Austin Blatt
Triage and provide a response to the CVE's in SEC-274 for pupetdb and pe-puppetdb clojure dependencies {noformat}Determining actual impact to the application based on how the packages are being used is useful in applying the appropriate risk score therefore some assistance is needed in determining actual impact to the application (ie, is the package utilizing the vulnerable paths). Please review the ticket (SEC-274) for details and comment responses regarding use of packages by 29 January 2021.{noformat}
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
Jira (PDB-5000) Triage SEC-274 for PuppetDB and PE-PuppetDB
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5000 Triage SEC-274 for PuppetDB and PE-PuppetDB Issue Type: Task Assignee: Austin Blatt Created: 2021/01/20 10:08 AM Priority: Normal Reporter: Austin Blatt Triage and provide a response to the CVE's in SEC-274 for pupetdb and pe-puppetdb clojure dependencies Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4934) PuppetDB does not support username@hostname auth for Azure PostgreSQL
Title: Message Title Rob Browning commented on PDB-4934 Re: PuppetDB does not support username@hostname auth for Azure PostgreSQL After a bit of investigation (and reading some of the chef-server discussion) , I think I might lean toward just adding a new database config option like connection-username that when set, overrides the username that's specified when connecting (i.e. for the hikaricp connection pool), but doesn't affect other uses of the username (i.e. when we're issuing various sql commands that include a username). While I haven't thought it through yet, I suppose that might mean we'd actually need two options e.g. connection-username and connection-migrator-username. 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.375238.1603127441000.119486.1611160260032%40Atlassian.JIRA.
Jira (PUP-10371) Add metric for Puppet Agent run
Title: Message Title Adam Winberg commented on PUP-10371 Re: Add metric for Puppet Agent run This new `startup_time` metric also includes splaytime which really makes the total run time metric quite useless. Is that a bug or a conscious decision? 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.349708.1584344056000.119393.1611156900027%40Atlassian.JIRA.
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-10856 Slower puppet agent run after agent upgrade to version 6 Change By: Gheorghe Popescu 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.383327.1610697413000.119349.1611152460025%40Atlassian.JIRA.
Jira (FACT-2921) LinuxMint Tessa not recognized, destroys services
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2921 LinuxMint Tessa not recognized, destroys services 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.383388.1610724788000.119325.1611151080026%40Atlassian.JIRA.
Jira (FACT-2923) Domain on Windows should be retrieved priority from registry
Title: Message Title Valters Jansons commented on FACT-2923 Re: Domain on Windows should be retrieved priority from registry Oana Tanasoiu, sounds good! Will have to try out a build of the Gem locally until then. 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.383584.1611067536000.119320.1611149640022%40Atlassian.JIRA.
Jira (FACT-2923) Domain on Windows should be retrieved priority from registry
Title: Message Title Oana Tanasoiu commented on FACT-2923 Re: Domain on Windows should be retrieved priority from registry Hi Valters Jansons, A new release of both Facter and Puppet 7 is scheduled for February. Thank you for filling the details of this ticket and for reporting this bug! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383584.1611067536000.119317.1611148500031%40Atlassian.JIRA.
Jira (PUP-10858) Add --timing to puppet facts show
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-10858 Add --timing to puppet facts show Change By: Gheorghe Popescu 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.383413.1610735312000.119314.1611147780133%40Atlassian.JIRA.
Jira (FACT-2923) Domain on Windows should be retrieved priority from registry
Title: Message Title Valters Jansons commented on FACT-2923 Re: Domain on Windows should be retrieved priority from registry Thank you Oana Tanasoiu for the fast work on Pull Request 2260! Trying to understand the timeline for aligning our upgrade process, so I have to ask: Assuming it merges quickly.. would you know when the next upcoming releases are expected for Facter itself to include the commit? And would you know when the next Puppet 7 release may be tagged including this Facter change? Would that be at the end of the linked sprint (February 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.383584.1611067536000.119309.1611147420027%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid 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.383703.1611082995000.119305.1611146880040%40Atlassian.JIRA.
Jira (PUP-10829) Prepare release announcement (Puppet Platform 7.2.0)
Title: Message Title Claire Cadman commented on PUP-10829 Re: Prepare release announcement (Puppet Platform 7.2.0) Nirupama Mantha Below is a copy of all the release notes, re. Mihai Buzgau's request for them to be in the email: https://docs.google.com/document/d/1jttwqo-uQwIt3yFQYsa7hs_SwFp-SZls_tSATgD9AvM/edit# Copying docs from our editor to a Google doc doesn't work very well, so the format isn't great. 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.381185.1608148366000.119292.1611141780166%40Atlassian.JIRA.
Jira (PUP-10766) Prepare release announcement (Puppet Platform 6.20.0)
Title: Message Title Claire Cadman commented on PUP-10766 Re: Prepare release announcement (Puppet Platform 6.20.0) Below is a copy of all the release notes, re. Mihai Buzgau's request for them to be in the email: https://docs.google.com/document/d/1jttwqo-uQwIt3yFQYsa7hs_SwFp-SZls_tSATgD9AvM/edit# Copying docs from our editor to a Google doc doesn't work very well, so the format isn't great. 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.376690.1604093629000.119288.1611141720195%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10844 Agent failures with server_list when one puppetserver fails Change By: Mihai Buzgau Sprint: NW - 2021-01-20 , NW - 2021-02-03 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.381638.1608653215000.119242.1611138540145%40Atlassian.JIRA.
Jira (PUP-10842) Issue with puppet creating production folder when multiple environment paths are set
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10842 Issue with puppet creating production folder when multiple environment paths are set Change By: Claire Cadman Labels: doc_reviewed jira_escalated 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.381531.1608552353000.119239.1611138420027%40Atlassian.JIRA.
Jira (PUP-10847) "puppet facts show fact" output differs from "facter fact"
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10847 "puppet facts show fact" output differs from "facter fact" Change By: Claire Cadman Labels: doc_reviewed 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.382201.1609880859000.119237.1611138180042%40Atlassian.JIRA.
Jira (FACT-2906) Dependency to lsb packages is missing
Title: Message Title Mihai Buzgau commented on FACT-2906 Re: Dependency to lsb packages is missing Moving this to PA project 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.381525.1608468982000.119226.1611137400024%40Atlassian.JIRA.
Jira (FACT-2906) Dependency to lsb packages is missing
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2906 Dependency to lsb packages is missing Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.381525.1608468982000.119222.1611137160063%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid 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.383703.1611082995000.119216.1611136860083%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Mihai Buzgau Sprint: NW - 2021-02-03 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.383703.1611082995000.119215.1611136860040%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383703.1611082995000.119214.1611136800134%40Atlassian.JIRA.
Jira (PUP-10857) User resource with forcelocal uses getent for groups
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10857 User resource with forcelocal uses getent for groups Change By: Mihai Buzgau 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.383586.1611070494000.119210.1611136680028%40Atlassian.JIRA.
Jira (FACT-2923) Domain on Windows should be retrieved priority from registry
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2923 Domain on Windows should be retrieved priority from registry Change By: Mihai Buzgau Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383584.1611067536000.119202.1611136320027%40Atlassian.JIRA.
Jira (PUP-10858) Add --timing to puppet facts show
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10858 Add --timing to puppet facts show 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.383413.1610735312000.119201.1611136200028%40Atlassian.JIRA.
Jira (PUP-10858) Add --timing to puppet facts show
Title: Message Title Mihai Buzgau moved an issue Puppet / PUP-10858 Add --timing to puppet facts show Change By: Mihai Buzgau Key: FACT PUP - 2922 10858 Project: Facter Puppet 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.383413.1610735312000.119200.1611136080042%40Atlassian.JIRA.
Jira (FACT-2921) LinuxMint Tessa not recognized, destroys services
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2921 LinuxMint Tessa not recognized, destroys services Change By: Mihai Buzgau 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.383388.1610724788000.119196.1611135960068%40Atlassian.JIRA.
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10856 Slower puppet agent run after agent upgrade to version 6 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.383327.1610697413000.119190.1611135420025%40Atlassian.JIRA.
Jira (PUP-10854) apt provider does not work with local packages
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10854 apt provider does not work with local packages 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.383202.1610630264000.119187.161113554%40Atlassian.JIRA.
Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10853 When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact 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.383136.1610563179000.119183.1611134640054%40Atlassian.JIRA.
