Jira (PUP-10648) puppet 6 agent doesn't honor usecacheonfailure setting when using server_list
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10648 puppet 6 agent doesn't honor usecacheonfailure setting when using server_list Change By: Mihai Buzgau Sprint: NW - 2020-09-30 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.36944.1600235640032%40Atlassian.JIRA.
Jira (PUP-7791) No useful debug output for yum/rpm provider success/failure/version information
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-7791 No useful debug output for yum/rpm provider success/failure/version information Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-09-30 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.201571.150057424.36940.1600235400034%40Atlassian.JIRA.
Jira (FACT-2198) Facts for AIX
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2198 Facts for AIX Change By: Mihai Buzgau Epic Status: To Do Done 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.338903.1576052676000.36933.1600235220134%40Atlassian.JIRA.
Jira (FACT-2067) Implement facts for Fedora OS
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2067 Implement facts for Fedora OS Change By: Mihai Buzgau Epic Status: To Do Done 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.329125.1571037743000.36934.1600235220175%40Atlassian.JIRA.
Jira (FACT-2197) Facts for OSx
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2197 Facts for OSx Change By: Mihai Buzgau Epic Status: To Do Done 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.338902.1576052637000.36932.1600235160026%40Atlassian.JIRA.
Jira (PUP-10651) Update Public-facing Puppet docs to include redhat8-aarch64
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10651 Update Public-facing Puppet docs to include redhat8-aarch64 Change By: Mihai Buzgau Sprint: NW - 2020-09-30 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.370632.1598625854000.36931.1600235100109%40Atlassian.JIRA.
Jira (PUP-10651) Update Public-facing Puppet docs to include redhat8-aarch64
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10651 Update Public-facing Puppet docs to include redhat8-aarch64 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.370632.1598625854000.36930.1600235100047%40Atlassian.JIRA.
Jira (PUP-8682) Allow disabling settings catalog
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-8682 Allow disabling settings catalog Change By: Mihai Buzgau Team: Froyo 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.248061.1525111785000.36928.1600234320062%40Atlassian.JIRA.
Jira (PUP-8682) Allow disabling settings catalog
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-8682 Allow disabling settings catalog Change By: Mihai Buzgau Sprint: NW - 2020-09-30 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.248061.1525111785000.36929.1600234320074%40Atlassian.JIRA.
Jira (PUP-10674) Rename master branch to 6.x
Title: Message Title Josh Cooper created an issue Puppet / PUP-10674 Rename master branch to 6.x Issue Type: Task Assignee: Unassigned Created: 2020/09/15 4:40 PM Priority: Normal Reporter: Josh Cooper Rename branch in github. Make sure branch protection rules are correct. Update ci-job-configs. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10668) Puppet Main Terminology
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10668 Puppet Main Terminology Change By: Josh Cooper This epic contains tickets relating to terminology changes for the puppet repo which should land in the 6 . y series. 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.372039.1600212217000.36844.1600212960083%40Atlassian.JIRA.
Jira (PUP-10668) Puppet Main Terminology
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10668 Puppet Main Terminology Change By: Josh Cooper Fix Version/s: PUP 6.y 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.372039.1600212217000.36843.1600212960042%40Atlassian.JIRA.
Jira (PUP-10673) Call simple server status endpoint
Title: Message Title Josh Cooper created an issue Puppet / PUP-10673 Call simple server status endpoint Issue Type: Task Assignee: Unassigned Created: 2020/09/15 4:34 PM Priority: Normal Reporter: Josh Cooper Call the simple server status endpoint when processing the server list. This is blocked on the server REST API changes. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10672) Add "server_used" report entry
Title: Message Title Josh Cooper created an issue Puppet / PUP-10672 Add "server_used" report entry Issue Type: Task Assignee: Unassigned Created: 2020/09/15 4:33 PM Priority: Normal Reporter: Josh Cooper Add a "server_used" parameter in the report which behaves like "master_used" Bump the report version. Update the report schema and docs. Maybe delete "master_used" in puppet 7 (and bump report version again) as a separate ticket? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10671) Add server runmode and alias
Title: Message Title Josh Cooper created an issue Puppet / PUP-10671 Add server runmode and alias Issue Type: Task Assignee: Unassigned Created: 2020/09/15 4:32 PM Priority: Normal Reporter: Josh Cooper Add "server" run mode that behaves like "master" It should be possible to set the run mode (eg in an external application) using the "server" or "master" run mode. Update applications in puppet to use the "server" run mode as neeed, such as "puppet lookup". Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10670) Create "serverport" setting and alias
Title: Message Title Josh Cooper created an issue Puppet / PUP-10670 Create "serverport" setting and alias Issue Type: Task Assignee: Unassigned Created: 2020/09/15 4:30 PM Priority: Normal Reporter: Josh Cooper In lib/puppet/defaults.rb, create "serverport" setting (to replace "masterport") It should be possible to specify either on the command line, puppet.conf or in code. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10669) Create "server" section and add alias
Title: Message Title Josh Cooper created an issue Puppet / PUP-10669 Create "server" section and add alias Issue Type: Task Assignee: Unassigned Created: 2020/09/15 4:27 PM Priority: Normal Reporter: Josh Cooper Update lib/puppet/defaults.rb so settings are added to the "server" section instead of "master". It should be possible to get/set/remove settings based on the "server" section or "master" so as to not break existing applications/code. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10668) Puppet Main Terminology
Title: Message Title Josh Cooper created an issue Puppet / PUP-10668 Puppet Main Terminology Issue Type: Epic Assignee: Unassigned Created: 2020/09/15 4:23 PM Priority: Normal Reporter: Josh Cooper This epic contains tickets relating to terminology changes for the puppet repo. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4895) Use top level hash to check catalog inputs submission
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission Change By: Austin Blatt Assignee: Austin Blatt 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.371939.1600194545000.36829.1600212060123%40Atlassian.JIRA.
Jira (PDB-4896) Diff the catalog inputs before storage
Title: Message Title Austin Blatt assigned an issue to Rob Browning PuppetDB / PDB-4896 Diff the catalog inputs before storage Change By: Austin Blatt Assignee: Rob Browning 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.371940.1600194591000.36826.160021236%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 Team: Coremunity 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.370505.1598545662000.36770.1600208460087%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.36771.1600208460131%40Atlassian.JIRA.
Jira (PDB-4892) Summary query for catalog_inputs unecessarily slow
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4892
Summary query for catalog_inputs unecessarily slow
Change By:
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.{code}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 ms2020-09-11T06:23:02.803Z INFO [sync] --> transferred factsets (2) from https:// uklvasapp715.gdc.standardchartered.com :8081/pdb/query/v4/factsets in 9,303 ms2020-09-11T06:23:06.081Z INFO [sync] --> transferred reports (0) from https:// uklvasapp715.gdc.standardchartered.com :8081/pdb/query/v4/reports in 3,277 ms2020-09-11T06:24:09.596Z INFO [sync] --> transferred catalog-inputs (0) from https:// uklvasapp715.gdc.standardchartered.com :8081/pdb/query/v4/catalog-inputs in 63,515 ms2020-09-11T06:24:11.400Z INFO [sync] --> transferred nodes (0) from https:// uklvasapp715.gdc.standardchartered.com :8081/pdb/query/v4/nodes in 1,803 ms{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4880) PSQL performance issue - Autovacuum unable to clean up "pe-puppetdb.public.catalog_inputs"
Title: Message Title Austin Blatt assigned an issue to Austin Blatt Closing this as a duplicate of PE-30055. Since the official support escalation (PE-30055) was made on Sept 10th the PuppetDB team has been working with Support on that ticket so that it gets to proper internal visibility. PuppetDB / PDB-4880 PSQL performance issue - Autovacuum unable to clean up "pe-puppetdb.public.catalog_inputs" Change By: Austin Blatt Assignee: Austin Blatt Resolution: Duplicate Status: Open Closed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4893) Migration User check fails for Azure based postgresql servers
Title: Message Title Zachary Kent commented on PDB-4893 Re: Migration User check fails for Azure based postgresql servers Hey Jonathan Law, Thanks for raising this issue. We looked into it a bit this morning and read a little about the Azure PostgreSQL username requirements. We're thinking we might add a config option which allows people to disable the migration checks as a possible work around. We still want to look into the possibility of making the username configurable to handle Azure's Postgres username format, but aren't exactly sure what we want there yet. Our next scheduled FOSS release is at the end of October so any solution we come up with will likely be released then. I'll update this ticket when we start work on the issue. Thanks again! 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.371865.1600180249000.36614.1600198740141%40Atlassian.JIRA.
Jira (PDB-4893) Migration User check fails for Azure based postgresql servers
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4893 Migration User check fails for Azure based postgresql servers Change By: Zachary Kent Fix Version/s: PDB 6.12.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.371865.1600180249000.36613.1600198680117%40Atlassian.JIRA.
Jira (PDB-4897) Double-check catalog-inputs query structures
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4897 Double-check catalog-inputs query structures Change By: Rob Browning 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.371951.1600196831000.36583.1600197360076%40Atlassian.JIRA.
Jira (PDB-4897) Double-check catalog-inputs query structures
Title: Message Title Rob Browning moved an issue PuppetDB / PDB-4897 Double-check catalog-inputs query structures Change By: Rob Browning Key: PE PDB - 30064 4897 Project: Puppet Enterprise [Internal] PuppetDB 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.371951.1600196831000.36571.1600196940109%40Atlassian.JIRA.
Jira (PDB-4896) Diff the catalog inputs before storage
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4896
Diff the catalog inputs before storage
Change By:
Austin Blatt
Once we've identified that the inputs have changed, they've most likely deleted or added a single hiera key. So we should pull the existing set of hiera inputs and diff them in PuppetDB to decide what {{DELETE}} and {{INSERT}} commands to issue.
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.371940.1600194591000.36555.1600195800030%40Atlassian.JIRA.
Jira (PUP-10473) Remove legacy auth.conf support
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10473 Remove legacy auth.conf support Change By: Josh Cooper Release Notes: Deprecation Release Notes Summary: Note this is a removal not a deprecation.Puppet's legacy auth.conf has been deprecated for several major releases, and puppet 7 removes support for legacy auth.conf entirely. As a result, all authorization to puppet REST APIs is controlled by puppetserver's auth.conf. In addition, "allow" and "deny" rules in puppet's fileserver.conf used for custom file mounts will be ignored and puppet will log an error for each entry. Finally, the `rest_authconfig` setting has been removed. 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
Jira (PDB-4895) Use top level hash to check catalog inputs submission
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4895
Use top level hash to check catalog inputs submission
Change By:
Austin Blatt
Most of the time, the hiera inputs of a catalog won't have changed because it requires a user to commit a change to the control repo. We should hash the entire set, store that hash in the {{certnames}} table and check that to identify _if_ there's anything that has changed before we go through the expense of storing a new set of inputs.
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.371939.1600194545000.36551.1600195560127%40Atlassian.JIRA.
Jira (PDB-4895) Use top level hash to check catalog inputs submission
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission Change By: Austin Blatt Acceptance Criteria: - database migration to add column to certname- hash & check that the content of catalog inputs has changed before storing the new set Release Notes: New Feature 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.371939.1600194545000.36552.1600195620039%40Atlassian.JIRA.
Jira (PDB-4892) Summary query for catalog_inputs unecessarily slow
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4892
Summary query for catalog_inputs unecessarily slow
Change By:
Austin Blatt
Acceptance Criteria:
- Summary query for catalog inputs uses drop joins to only query the {{certnames}} table
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.371815.1600126491000.36553.1600195620083%40Atlassian.JIRA.
Jira (PUP-10473) Remove legacy auth.conf support
Title: Message Title Josh Cooper commented on PUP-10473 Re: Remove legacy auth.conf support Merged to main in https://github.com/puppetlabs/puppet/commit/715ac6903a498f4618a5d716c3fd557a1477babf 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.356946.1588032295000.36542.1600195380032%40Atlassian.JIRA.
Jira (PDB-4894) Improve performance of catalog inputs for CD4PE Hiera mpact analysis
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4894 Improve performance of catalog inputs for CD4PE Hiera mpact analysis Change By: Austin Blatt Summary: Improve performance of catalog inputs for cd4pe hiera impact CD4PE Hiera mpact analysis 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.371927.1600194155000.36539.1600195320096%40Atlassian.JIRA.
Jira (PDB-4894) Improve performance of catalog inputs for CD4PE Hiera Impact Analysis
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4894 Improve performance of catalog inputs for CD4PE Hiera Impact Analysis Change By: Austin Blatt Summary: Improve performance of catalog inputs for CD4PE Hiera mpact analysis Impact Analysis 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.371927.1600194155000.36540.1600195320139%40Atlassian.JIRA.
Jira (PDB-4881) Add primary key to catalog_inputs
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4881 Add primary key to catalog_inputs Change By: Austin Blatt Assignee: Austin Blatt 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.36538.1600195320050%40Atlassian.JIRA.
Jira (PDB-4894) Improve performance of catalog inputs for cd4pe hiera impact analysis
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4894 Improve performance of catalog inputs for cd4pe hiera impact analysis Change By: Austin Blatt To simplify and speed the implementation of CD4PE's hiera input analysis in PuppetDB, we omitted many optimizations to both the storage, querying, and HA sync.This encompasses a set of work that should improve the performance of each of those three operations for CD4PE's catalog inputs. 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.371927.1600194155000.36537.1600195260133%40Atlassian.JIRA.
Jira (PDB-4896) Diff the catalog inputs before storage
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4896 Diff the catalog inputs before storage Issue Type: New Feature Assignee: Unassigned Created: 2020/09/15 11:29 AM Priority: Normal Reporter: Austin Blatt 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
Jira (PDB-4895) Use top level hash to check catalog inputs submission
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4895 Use top level hash to check catalog inputs submission Issue Type: New Feature Assignee: Unassigned Created: 2020/09/15 11:29 AM Priority: Normal Reporter: Austin Blatt 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
Jira (PDB-4892) Summary query for catalog_inputs unecessarily slow
Title: Message Title Austin Blatt assigned an issue to Zachary Kent PuppetDB / PDB-4892 Summary query for catalog_inputs unecessarily slow Change By: Austin Blatt Assignee: Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371815.1600126491000.36525.1600194360123%40Atlassian.JIRA.
Jira (PDB-4892) Summary query for catalog_inputs unecessarily slow
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4892 Summary query for catalog_inputs unecessarily slow Change By: Austin Blatt Epic Link: PDB-4894 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.371815.1600126491000.36521.1600194300037%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 Epic Link: PDB-4894 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.36522.1600194300080%40Atlassian.JIRA.
Jira (PDB-4894) Improve performance of catalog inputs for cd4pe hiera impact analysis
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4894 Improve performance of catalog inputs for cd4pe hiera impact analysis Change By: Austin Blatt Team/s: HA,PuppetDB 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.371927.1600194155000.36520.1600194240026%40Atlassian.JIRA.
Jira (PDB-4894) Improve performance of catalog inputs for cd4pe hiera impact analysis
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4894 Improve performance of catalog inputs for cd4pe hiera impact analysis Issue Type: Epic Assignee: Unassigned Created: 2020/09/15 11:22 AM Priority: Normal Reporter: Austin Blatt 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
Jira (PUP-10664) Puppet 6 should log connection error details when a functional puppet master cannot be located
Title: Message Title Charlie Sharpsteen commented on PUP-10664 Re: Puppet 6 should log connection error details when a functional puppet master cannot be located Yes, I think we should log all errors that result in the agent failing over to the next server in the list even if the run is ultimately successful. The error messages have important context that may be needed to restore the first server in the list to a healthy state. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371698.1599857641000.36494.1600193220093%40Atlassian.JIRA.
Jira (PUP-8969) Support interpolation of sensitive values in EPP templates
Title: Message Title Josh Cooper commented on PUP-8969 Re: Support interpolation of sensitive values in EPP templates I updated the title and submitted a PR with those changes (it still needs tests). Allowing `epp` and `inline_epp` to return `Sensitive` seems backwards compatible, as the caller can wrap the return value with `Sensitive` and the result doesn't get double wrapped. But there may be other cases to consider? 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.262922.1530114614000.36485.1600192380041%40Atlassian.JIRA.
Jira (PUP-8969) Support interpolation of sensitive values in EPP templates
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8969 Support interpolation of sensitive values in EPP templates Change By: Josh Cooper Summary: Sensitive parameters are not redacted from reports / agent output when used Support interpolation of sensitive values in EPP templates 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.262922.1530114614000.36434.1600190880027%40Atlassian.JIRA.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates 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.262922.1530114614000.36432.1600190760032%40Atlassian.JIRA.
Jira (PUP-10667) if pluginsync fails puppet should apply cached catalog
Title: Message Title Josh Cooper commented on PUP-10667 Re: if pluginsync fails puppet should apply cached catalog About https://github.com/puppetlabs/puppet/blob/84bf2d8607a6ac9ffde4a061d25016afc06165b5/lib/puppet/configurer.rb#L74, the issue is we can't differentiate between the user wanted to used a cached catalog puppet agent --use_cached_catalog vs we're falling back to using the cached catalog. Can we modify the configurer so it uses Puppet[:use_cached_catalog] to determine what the initial intent was, while it uses a local variable to determine which mode we're currently in. And then if pluginsync fails, we change the local variable, but not Puppet[:use_cached_catalog]? About the inconsistencies when ignore_plugin_errors==false due to partial downloads, yeah, we have that issue now (prior to the ignore_plugin_errors when falling back to cached catalog). For example, normal daemonized agent does pluginsync, fails and the failure is ignored, agent requests catalog, which fails and falls back to cached catalog, but plugins may not match. I think to fix this plugins need to be downloaded in an atomic way. One option is to create a secure directory with the same parent as Puppet[:libdir] and use it to pluginsync. To avoid downloading files we already have, you'd have to copy everything from Puppet[:libdir] to libnew. So maybe something like: 1. create lib.new using ruby equivalent of mktemp -d lib.new and restrict permissions so only the current user can write 2. Pluginsync to lib.new 3. Rename Puppet[:libdir] to lib.old 4. Rename lib.new to Puppet[:libdir] 5. Delete lib.old recursively It's possible for puppet to crash/ctrl-c between any of those points. If it occurs between 3 and 4, then puppet will have lost all of its plugins. To account for that, if puppet starts and lib.old exists, but Puppet[:libdir] doesn't, then have recover its plugins by renaming lib.old to Puppet[:libdir]. If the crash occurs between 4 and 5, then the new plugins have been committed. So when puppet starts, if Puppet[:libdir] exists, have it delete the stale lib.old. That said, I'm thinking we should file a separate ticket to ensure pluginsync is atomic (since there's always been an opportunity for inconsistent plugins when falling back to a cached catalog). Thoughts? Add Comment
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
Luchian Nemes
*Puppet Version: 7.0.0* *Puppet Server Version: 7.0.0* *OS Name/Version: Ubuntu 16.04* The first *'puppet agent -t'* run seems to not show any signs of custom facts being resolved. This only happens if: - this is the run when they are synced from server - *Facter 4.x* is being used (Facter 3 works as expected) - agent node has *Ubuntu 16.04* as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those) h2. How to set the environmenth4. Install Puppet Agent >= 7 (since it comes with Facter 4):{color:#57d9a3}➜{color} wget [http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb]{color:#57d9a3}➜{color} dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.debh4. Make the new binaries easily accessible:{color:#57d9a3}➜{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc{color:#57d9a3}➜{color} source ~/.bashrch4. Check Puppet version : {color:#57d9a3}➜{color} puppet --version{panel}7.0.0{panel}h4. Check Facter version:{color:#57d9a3}➜{color} facter --version{panel}4.0.37{panel}h4. Install Puppet Server:{color:#57d9a3}➜{color} wget [http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb]{color:#57d9a3}➜{color} dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -yh4. Check if it installed correctly (make sure you've run above commands correctly) : {color:#57d9a3}➜{color} puppetserver --version{panel}puppetserver version: 7.0.0.SNAPSHOT.2020.09.11T0333{panel}h4. Start the Puppet Server service : {color:#57d9a3}➜{color} service puppetserver starth4. Configure Puppet Server address : {color:#57d9a3}➜{color} puppet config set server $(facter fqdn)h4. Make sure Puppet Agent and Puppet Server communicate accordingly : {color:#57d9a3}➜{color} puppet agent -th4. Install this module that contains a custom fact : {color:#57d9a3}➜{color} puppet module install eputnam-i18ndemoh4. You can see the content of this custom fact : {color:#57d9a3}➜{color} cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb{panel}Facter.add('i18ndemo_fact') do setcode do {color:#de350b} raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') {color} end end{panel} h2. How to reproduce the issueh4. With the module above/custom fact in place, do the first 'puppet agent -t' run:{color:#57d9a3}➜{color} puppet agent -t{panel}*{color:#00875a}Info: Using configured environment 'production'{color}* *{color:#00875a}Info: Retrieving pluginfacts{color}* *{color:#00875a}Info: Retrieving plugin{color}* Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created ...
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
Luchian Nemes
*Puppet Version: 7.0.0* *Puppet Server Version: 7.0.0* *OS Name/Version: Ubuntu 16.04* The first *'puppet agent -t'* run seems to not show any signs of custom facts being resolved. This only happens if: - this is the run when they are synced from server - *Facter 4.x* is being used (Facter 3 works as expected) - agent node has *Ubuntu 16.04* as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those) h2. h2. How to set the environmenth4. Install Puppet Agent >= 7 (since it comes with Facter 4) : {color:# c1c7d0 57d9a3 } > ➜ {color} wget [http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb] {color:# c1c7d0 57d9a3 } > ➜ {color} dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.debh4. Make the new binaries easily accesible accessible: {color:# c1c7d0 57d9a3 } > ➜ {color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc {color:# c1c7d0 57d9a3 } > ➜ {color} source ~/.bashrch4. Check Puppet version{color:# c1c7d0 57d9a3 } > ➜ {color} puppet --version{panel}7.0.0{panel}h4. Check Facter version : {color:# c1c7d0 57d9a3 } > ➜ {color} facter --version{panel}4.0.37{panel}h4. Install Puppet Server : {color:# c1c7d0 57d9a3 } > ➜ {color} wget [http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb] {color:# c1c7d0 57d9a3 } > ➜ {color} dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -yh4. Check if it installed correctly (make sure you've run above commands correctly){color:# c1c7d0 57d9a3 } > ➜ {color} puppetserver --version{panel}puppetserver version: 7.0.0.SNAPSHOT.2020.09.11T0333{panel}h4. Start the Puppet Server service{color:# c1c7d0 57d9a3 } > ➜ {color} service puppetserver starth4. Configure Puppet Server address{color:# c1c7d0 57d9a3 } > ➜ {color} puppet config set server $(facter fqdn)h4. Make sure Puppet Agent and Puppet Server communicate accordingly{color:# c1c7d0 57d9a3 } > ➜ {color} puppet agent -th4. Install this module that contains a custom fact{color:# c1c7d0 57d9a3 } > ➜ {color} puppet module install eputnam-i18ndemoh4. You can see the content of this custom fact{color:# c1c7d0 57d9a3 } > ➜ {color} cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb{panel}Facter.add('i18ndemo_fact') do setcode do raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') end end{panel} h2. h2. How to reproduce the issueh4. With the module above/custom fact in place, do the first 'puppet agent -t' run:{color:# c1c7d0 57d9a3 } > ➜ {color} puppet agent -t{panel}*{color:#00875a}Info: Using configured environment 'production'{color}*
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
Luchian Nemes
*Puppet Version: 7.0.0* *Puppet Server Version: 7.0.0* *OS Name/Version: Ubuntu 16.04* The first *'puppet agent -t'* run seems to not show any signs of custom facts being resolved. This only happens if: - this is the run when they are synced from server - *Facter 4.x* is being used (Facter 3 works as expected) - agent node has *Ubuntu 16.04* as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those)h2. h2. How to set the environmenth4. Install Puppet Agent >= 7 (since it comes with Facter 4){color:#c1c7d0}>{color} wget [http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb] {color:#c1c7d0}>{color} dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.debh4. Make the new binaries easily accesible{color:#c1c7d0}>{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc {color:#c1c7d0}>{color} source ~/.bashrch4. Check Puppet version{color:#c1c7d0}>{color} puppet --version{panel}7.0.0{panel}h4. Check Facter version{color:#c1c7d0}>{color} facter --version{panel}4.0.37{panel}h4. Install Puppet Server{color:#c1c7d0}>{color} wget [http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb] {color:#c1c7d0}>{color} dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -yh4. Check if it installed correctly (make sure you've run above commands correctly){color:#c1c7d0}>{color} puppetserver --version{panel}puppetserver version: 7.0.0.SNAPSHOT.2020.09.11T0333{panel}h4. Start the Puppet Server service{color:#c1c7d0}>{color} service puppetserver starth4. Configure Puppet Server address{color:#c1c7d0}>{color} puppet config set server $(facter fqdn)h4. Make sure Puppet Agent and Puppet Server communicate accordingly{color:#c1c7d0}>{color} puppet agent -th4. Install this module that contains a custom fact{color:#c1c7d0}>{color} puppet module install eputnam-i18ndemoh4. You can see the content of this custom fact{color:#c1c7d0}>{color} cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb{panel}Facter.add('i18ndemo_fact') do setcode do raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') end end{panel}h2. h2. How to reproduce the issueh4. With the module above/custom fact in place, do the first 'puppet agent -t' run:{color:#c1c7d0}>{color} puppet agent -t{panel}*{color:#00875a}Info: Using configured environment 'production'{color}* *{color:#00875a}Info: Retrieving pluginfacts{color}* *{color:#00875a}Info: Retrieving plugin{color}* Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created ... Notice:
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
Luchian Nemes
*Puppet Version: 7.0.0* *Puppet Server Version: 7.0.0* *OS Name/Version: Ubuntu 16.04*The first *'puppet agent -t'* run seems to not show any signs of custom facts being resolved. This only happens if: - this is the run when they are synced from server - *Facter 4.x* is being used (Facter 3 works as expected) - agent node has *Ubuntu 16.04* as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those)h2. h2. How to set the environmenth4. Install Puppet Agent >= 7 (since it comes with Facter 4){color:#c1c7d0}>{color} wget [http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb] {color:#c1c7d0}>{color} dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.debh4. Make the new binaries easily accesible{color:#c1c7d0}>{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc {color:#c1c7d0}>{color} source ~/.bashrch4. Check Puppet version{color:#c1c7d0}>{color} puppet --version {panel}7.0.0{panel} h4. Check Facter version{color:#c1c7d0}>{color} facter --version {panel}4.0.37{panel} h4. Install Puppet Server{color:#c1c7d0}>{color} wget [http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb] {color:#c1c7d0}>{color} dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -yh4. Check if it installed correctly (make sure you've run above commands correctly){color:#c1c7d0}>{color} puppetserver --version {panel}puppetserver version: 7.0.0.SNAPSHOT.2020.09.11T0333{panel} h4. Start the Puppet Server service{color:#c1c7d0}>{color} service puppetserver starth4. Configure Puppet Server address{color:#c1c7d0}>{color} puppet config set server $(facter fqdn)h4. Make sure Puppet Agent and Puppet Server communicate accordingly{color:#c1c7d0}>{color} puppet agent -th4. Install this module that contains a custom fact{color:#c1c7d0}>{color} puppet module install eputnam-i18ndemoh4. You can see the content of this custom fact{color:#c1c7d0}>{color} cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb{panel}Facter.add('i18ndemo_fact') do setcode do {color:#de350b} raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') {color} end end{panel}h2. h2. How to reproduce the issueh4. With the module above/custom fact in place, do the first 'puppet agent -t' run:{color:#c1c7d0}>{color} puppet agent -t{panel}*{color:#00875a}Info: Using configured environment 'production'{color}* *{color:#00875a}Info: Retrieving pluginfacts{color}* *{color:#00875a}Info: Retrieving plugin{color}* Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created ...
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
Luchian Nemes
*Puppet Version: 7.0.0* *Puppet Server Version: 7.0.0* *OS Name/Version: Ubuntu 16.04* The first * 'puppet agent -t' * run seems to not show any signs of custom facts being resolved. This only happens if: - this is the run when they are synced from server - * Facter 4.x * is being used (Facter 3 works as expected) - agent node has * Ubuntu 16.04 * as OS (also tested on Windows 2012 and Ubuntu 18.04; it seemed to be working as expected on those) h2. h2. How to set the environment h4. Install Puppet Agent >= 7 (since it comes with Facter 4){color:#c1c7d0}>{color} wget [http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb] {color:#c1c7d0}>{color} dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.debh4. Make the new binaries easily accesible{color:#c1c7d0}>{color} echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc {color:#c1c7d0}>{color} source ~/.bashrch4. Check Puppet version{color:#c1c7d0}>{color} puppet --version {panel}7.0.0{panel} h4. Check Facter version{color:#c1c7d0}>{color} facter --version {panel}4.0.37{panel} h4. Install Puppet Server{color:#c1c7d0}>{color} wget [http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb] {color:#c1c7d0}>{color} dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -yh4. Check if it installed correctly (make sure you've run above commands correctly){color:#c1c7d0}>{color} puppetserver --version {panel}puppetserver version: 7.0.0.SNAPSHOT.2020.09.11T0333{panel} h4. Start the Puppet Server service{color:#c1c7d0}>{color} service puppetserver starth4. Configure Puppet Server address{color:#c1c7d0}>{color} puppet config set server $(facter fqdn)h4. Make sure Puppet Agent and Puppet Server communicate accordingly{color:#c1c7d0}>{color} puppet agent -th4. Install this module that contains a custom fact{color:#c1c7d0}>{color} puppet module install eputnam-i18ndemoh4. You can see the content of this custom fact{color:#c1c7d0}>{color} cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb{panel}Facter.add('i18ndemo_fact') do setcode do {color:#de350b} raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo'){color} end end{panel}h2. h2. How to reproduce the issueh4. With the module above/custom fact in place, do the first 'puppet agent -t' run:{color:#c1c7d0}>{color} puppet agent -t{panel}*{color:#00875a}Info: Using configured environment 'production'{color}* *{color:#00875a}Info: Retrieving pluginfacts{color}* *{color:#00875a}Info: Retrieving plugin{color}* Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created ...
Jira (HI-620) Hiera mapped_paths should permit glob expansion
Title: Message Title
Pat Riehecky created an issue
Hiera / HI-620
Hiera mapped_paths should permit glob expansion
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2020/09/15 8:57 AM
Priority:
Normal
Reporter:
Pat Riehecky
It would be helpful for breaking out files into more manageable chunks, if hiera's mapped_paths option would permit use of globs for expansion. For example: {{- name: Example mapped_paths: [services, tmp, "service/%{tmp}/*.yaml"}}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
Luchian Nemes
Environment:
How to set the environment:Install Puppet Agent >= 7 (since it comes with Facter 4)wget http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.debdpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.debMake the new binaries easily accesibleecho 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrcsource ~/.bashrcCheck Puppet versionpuppet --versionCheck Facter versionfacter --versionInstall Puppet Serverwget http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.debdpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -yCheck if it installed correctly (make sure you've run above commands correctly)puppetserver --versionStart the Puppet Server serviceservice puppetserver startConfigure Puppet Server addresspuppet config set server $(facter fqdn)Make sure Puppet Agent and Puppet Server communicate accordinglypuppet agent -tInstall this module that contains a custom factpuppet module install eputnam-i18ndemoYou can see the content of this custom factcat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rbFacter.add('i18ndemo_fact') do setcode do raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') endendHow to reproduce the issue:With the module above/custom fact in place, do the first 'puppet agent -t' run:puppet agent -tDo the second run and now observe the expected raise:puppet agent -tHow to reset environment to reproduce the issue again:rm -rf /opt/puppetlabs/puppet/cache/lib/facter/
Add Comment
Jira (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Change By:
Luchian Nemes
Acceptance Criteria:
Here is a barebones Puppet acceptance test. Behaviour on other operating systems, with Facter3/Facter4 and the possible fix can be quickly checked using this.{code:ruby} test_name 'Untitled' do tag 'audit:high', 'audit:acceptance' require 'puppet/acceptance/i18ndemo_utils' extend Puppet::Acceptance::I18nDemoUtils step 'Install the i18ndemo module on master' doinstall_i18n_demo_module(master) end agents.each do |agent|teardown do vardir = on(agent, puppet('config print vardir')).stdout.chomp agent.rm_rf("#{vardir}/lib/facter")endstep "Run 'puppet agent -t' and expect greatness" do on(agent, puppet("agent -t")) do |result|assert_match(/i18ndemo_fact\: this is a raise from a custom fact from eputnam-i18ndemo/, result.stderr) endend endend{code}
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 (FACT-2799) Missing output when resolving custom facts with Facter 4
Title: Message Title
Luchian Nemes created an issue
Facter / FACT-2799
Missing output when resolving custom facts with Facter 4
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/09/15 8:55 AM
Environment:
How to set the environment: Install Puppet Agent >= 7 (since it comes with Facter 4) wget http://builds.delivery.puppetlabs.net/puppet-agent/8a2819dd5b23cb30263ac6ae0f35dadd21cac28c/repos/deb/xenial/puppet7/puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb dpkg -i puppet-agent_7.0.0.317.g8a2819dd-1xenial_amd64.deb Make the new binaries easily accesible echo 'export PATH=/opt/puppetlabs/bin/:$PATH' >> ~/.bashrc source ~/.bashrc Check Puppet version puppet --version Check Facter version facter --version Install Puppet Server wget http://builds.delivery.puppetlabs.net/puppetserver/7.0.0.SNAPSHOT.2020.09.11T0333/artifacts/deb/xenial/puppet6/puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb dpkg -i puppetserver_7.0.0-0.1SNAPSHOT.2020.09.11T0333xenial_all.deb; apt-get update; apt-get -f install -y Check if it installed correctly (make sure you've run above commands correctly) puppetserver --version Start the Puppet Server service service puppetserver start Configure Puppet Server address puppet config set server $(facter fqdn) Make sure Puppet Agent and Puppet Server communicate accordingly puppet agent -t Install this module that contains a custom fact puppet module install eputnam-i18ndemo You can see the content of this custom fact cat /etc/puppetlabs/code/environments/production/modules/i18ndemo/lib/facter/i18ndemo_fact.rb Facter.add('i18ndemo_fact') do setcode do raise _('i18ndemo_fact: this is a raise from a custom fact from eputnam-i18ndemo') end end How to reproduce the issue: With the module above/custom fact in place, do the first 'puppet agent -t' run: puppet agent -t Do the second run and now observe the expected raise: puppet agent -t How to reset environment to reproduce the issue again: rm -rf /opt/puppetlabs/puppet/cache/lib/facter/
Priority:
Normal
Reporter:
Luchian Nemes
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title Trevor Vaughan commented on PUP-10665 Re: Add weak dependencies to puppet resources Changed optionally to optional because it's easier to type 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.36286.1600184400027%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: (updated from comments below) {code} exec { 'ping host': command => 'ping 1.2.3.4'}exec { 'ping other host': command => 'ping 2.3.4.5'}file { '/tmp/foo': owner => 'root', mode => '0640', requires => [ File['/tmp'], Exec['ping host'] ], # Add these items to the autorequires list optionally_requires optional_requires => [File['/dev/shm']], # Do not fail if these resources fail wants => [ Exec['ping other host'] ]}{code} The pairings would be: * {{ optionally_requires optional_requires }} => {{ optionally_notifies optional_notifies }}* {{wants}} => {{wanted_by}}Potential symbols (Stretch Goal) : * {{ optionally_requires optional_requires }} => {{*>}}** Denotes the 'match anything' regex marker* {{wants}} => {{+>}}** Denotes a broken line == broken dependencyIn 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
Jira (PDB-4893) Migration User check fails for Azure based postgresql servers
Title: Message Title Jonathan Law created an issue PuppetDB / PDB-4893 Migration User check fails for Azure based postgresql servers Issue Type: Bug Affects Versions: PDB 6.12.0 Assignee: Unassigned Components: PuppetDB Created: 2020/09/15 7:30 AM Priority: Normal Reporter: Jonathan Law Due to the way the Azure Postgresql server usernames work the migration user check always fails. user in config file is of the format "username@hostname" the actual user in postgresql is "username", therefore the jdbc user and the config user will never match. clojure.lang.ExceptionInfo: Connected to database as "puppetdb", not migrator "puppetdb@servername" at puppetlabs.puppetdb.cli.services$require_db_connection_as.invokeStatic(services.clj:532) at puppetlabs.puppetdb.cli.services$require_db_connection_as.invoke(services.clj:527) at puppetlabs.puppetdb.cli.services$init_with_db$fn__37137.invoke(services.clj:577)
Jira (FACT-2713) Facter fact 'disks' doesn`t display serial_number because of missed libudev-dev dependency
Title: Message Title Valentyna updated an issue Facter / FACT-2713 Facter fact 'disks' doesn`t display serial_number because of missed libudev-dev dependency Change By: Valentyna Priority: Normal Medium 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.365791.1594732505000.36193.1600177800027%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: (updated from comments below) {code} exec { 'ping host': command => 'ping 1.2.3.4'}exec { 'ping other host': command => 'ping 2.3.4.5'} file { '/tmp/foo': owner => 'root', mode => '0640', requires => [ File['/tmp'], Exec[' foo ping host '] ] , wants # Add these items to the autorequires list optionally_requires => [ File['/ etc dev / bar shm '] ] , # Do not fail if these resources fail wants => [ Exec[' baz ping other host '] ]}{code} The pairings would be:* {{optionally_requires}} => {{optionally_notifies}}* {{wants}} => {{wanted_by}}Potential symbols:* {{optionally_requires}} => {{*>}}** Denotes the 'match anything' regex marker* {{wants}} => {{+>}}** Denotes a broken line == broken dependency 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
Jira (PUP-10665) Add weak dependencies to puppet resources
Title: Message Title Trevor Vaughan commented on PUP-10665 Re: Add weak dependencies to puppet resources I like the idea above from Henrik Lindberg. It is true that optionally_requires is not the same as isolated_before. (I warned people that I was bad at naming things). Technically, optionally_before is what I expected the regular before to be when I started using the language but I think that ship has sailed. Even though it's a bit more wordy, I think that this is probably better than my original idea. The optionally_ stuff is actually easy to implement because it's identical to the auto (autorequires, etc...) portions of custom types that already exist. I think may be borrowing from systemd and using wants and wanted_by would be a bit easier to wrap our heads around than the isolated_* naming scheme. I'll update the description with these ideas. 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.36162.1600171980061%40Atlassian.JIRA.
Jira (PUP-7791) No useful debug output for yum/rpm provider success/failure/version information
Title: Message Title Austin Boyd updated an issue Puppet / PUP-7791 No useful debug output for yum/rpm provider success/failure/version information Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 26640 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.201571.150057424.36118.1600166220033%40Atlassian.JIRA.
Jira (FACT-2798) Check Facter.info, Facter.log_exception and set color option default to true
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2798 Check Facter.info, Facter.log_exception and set color option default to true Change By: Andrei Filipovici Sprint: ready for triage 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.371835.1600163096000.36103.1600163160032%40Atlassian.JIRA.
Jira (FACT-2798) Check Facter.info, Facter.log_exception and set color option default to true
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2798 Check Facter.info, Facter.log_exception and set color option default to true Issue Type: Task Assignee: Unassigned Created: 2020/09/15 2:44 AM Labels: platform7 Priority: Normal Reporter: Andrei Filipovici Check if Facter.info and Facter.log_exception on Facter 3 prints empty and nil messages. If it does then remove the first message checks in logger for this methods. Facter 3 prints by default colorised log messages. Change de color option default in Facter 4 to true. Add Comment
Jira (PUP-10667) if pluginsync fails puppet should apply cached catalog
Title: Message Title Ciprian Badescu commented on PUP-10667 Re: if pluginsync fails puppet should apply cached catalog Josh Cooper, while digging in the code to properly implement this (since basic implementation from https://github.com/puppetlabs/puppet/pull/8328/files will show to the user that the use of cached catalog was requested, due to https://github.com/puppetlabs/puppet/blob/84bf2d8607a6ac9ffde4a061d25016afc06165b5/lib/puppet/configurer.rb#L74), I think we open the door to problems similar to the initial ticket. 1. ignore_plugin_errors==true could lead to inconsistencies between modules and catalog, since we might have new catalog and old modules on the agent - problem solved with ignore_plugin_errors==false 2. ignore_plugin_errors==false and using cached catalog could lead to similar inconsistencies, since modules could be partly updated (downloaded failed on latest file) and cached catalog will be run. 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.371830.1600161104000.36101.1600162020179%40Atlassian.JIRA.
Jira (PUP-10667) if pluginsync fails puppet should apply cached catalog
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-10667 if pluginsync fails puppet should apply cached catalog Issue Type: Bug Assignee: Unassigned Created: 2020/09/15 2:11 AM Priority: Normal Reporter: Ciprian Badescu This ticket relates to https://tickets.puppetlabs.com/browse/PUP-1763 and https://tickets.puppetlabs.com/browse/PUP-10598 In the case we have ignore_plugin_errors==false and usecacheonfailure==true, puppet should apply cached catalog when pluginsync fails Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10658) Puppet service ps parsing using too loose regex
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10658 Puppet service ps parsing using too loose regex Change By: Dorin Pleava Assignee: Dorin Pleava 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.371182.1599213891000.36086.1600160340032%40Atlassian.JIRA.
Jira (FACT-2794) Release Facter 4.0.38
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2794 Release Facter 4.0.38 Change By: Mihai Buzgau Priority: Blocker Normal 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.371415.1599661332000.36085.1600159980033%40Atlassian.JIRA.
Jira (FACT-2794) Release Facter 4.0.38
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2794 Release Facter 4.0.38 Change By: Mihai Buzgau Priority: Normal Blocker 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.371415.1599661332000.36082.1600159740033%40Atlassian.JIRA.
Jira (FACT-2797) Facter -v has to print the version and the commit SHA of that version
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2797 Facter -v has to print the version and the commit SHA of that version Change By: Andrei Filipovici Sprint: ready for triage 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.371823.1600157075000.36051.1600157100104%40Atlassian.JIRA.
Jira (FACT-2797) Facter -v has to print the version and the commit SHA of that version
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2797 Facter -v has to print the version and the commit SHA of that version Issue Type: Task Assignee: Unassigned Created: 2020/09/15 1:04 AM Labels: platform7 Priority: Normal Reporter: 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
