Jira (PDB-4390) Don't produce duplicate certname entries for certnames with special characters
Title: Message Title Maheswaran Shanmugam commented on PDB-4390 Re: Don't produce duplicate certname entries for certnames with special characters My query is related to customer ticket "https://puppetlabs.zendesk.com/agent/tickets/35203" Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311094.1559593774000.47106.1560482700401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9749) puppet generate types should be run when the puppetserver is upgraded
Title: Message Title Trevor Vaughan commented on PUP-9749 Re: puppet generate types should be run when the puppetserver is upgraded Josh Cooper I didn't either but it definitely was. It was with a stack of SIMP modules, didn't debug past the fact that rerunning puppet generate types fixed everything. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312214.1560355314000.47075.1560473520172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4347) Don't use a static temp table name for fact path gc
Title: Message Title Heston Hoffman updated an issue PuppetDB / PDB-4347 Don't use a static temp table name for fact path gc Change By: Heston Hoffman Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305777.1555967633000.47044.1560470521219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4390) Don't produce duplicate certname entries for certnames with special characters
Title: Message Title Heston Hoffman updated an issue PuppetDB / PDB-4390 Don't produce duplicate certname entries for certnames with special characters Change By: Heston Hoffman Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311094.1559593774000.47014.1560469800680%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9749) puppet generate types should be run when the puppetserver is upgraded
Title: Message Title Josh Cooper commented on PUP-9749 Re: puppet generate types should be run when the puppetserver is upgraded I wouldn't expect that to be necessary. Is there a specific module that fails when the server is updated? /cc Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312214.1560355314000.46990.1560469320246%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title Tom Beech updated an issue Puppet Task Runner / BOLT-1316 The plan language should have a catch_errors functions Change By: Tom Beech Release Notes Summary: A new plan function catch_errors was added that accepts a list of types of errors to catch and a block of code to run where if it errors the plan will continue executing. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309066.155804176.46976.1560468960363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3687) ordering on fact value
Title: Message Title Heston Hoffman updated an issue PuppetDB / PDB-3687 ordering on fact value Change By: Heston Hoffman Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.212719.1506114212000.46955.1560468540500%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1393) Update homebrew-puppet (Bolt 1.23.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1393 Update homebrew-puppet (Bolt 1.23.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/13 4:25 PM Due Date: 2019/06/13 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-13) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-1395) Send release announcements (Bolt 1.23.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1395 Send release announcements (Bolt 1.23.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/06/13 4:25 PM Due Date: 2019/06/13 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-13) When docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt now available". In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com In the body, include a summary of the release and links to the release notes and installation instructions. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. (Optional) Set up a canned response in Gmail so that you don't have to recreate this email every time: Subject: Bolt X.Y.Z now available Body: Greetings! We're happy to announce the release of Bolt X.Y.Z. Highlights in this release include: Gerund phrase Gerund phrase For more information, check out the
Jira (BOLT-1394) Docs for bolt release (Bolt 1.23.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1394 Docs for bolt release (Bolt 1.23.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/06/13 4:25 PM Due Date: 2019/06/13 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-13) Release notes and docs changes for bolt 1.23.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1388) Bolt 1.23.0 2019-06-13 Release
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1388 Bolt 1.23.0 2019-06-13 Release Issue Type: Task Assignee: Tom Beech Created: 2019/06/13 4:24 PM Priority: Normal Reporter: Tom Beech Bolt 1.23.0 2019-06-13 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1391) Publish release artifacts (Bolt 1.23.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1391 Publish release artifacts (Bolt 1.23.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/13 4:24 PM Due Date: 2019/06/13 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-13) Run the Bolt shipping pipeline. Set REF to 1.23.0. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1392) Update the release spreadsheet (Bolt 1.23.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1392 Update the release spreadsheet (Bolt 1.23.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/13 4:25 PM Due Date: 2019/06/13 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-13) Update the release google spreadsheet for Bolt 1.23.0. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1390) Kick off release pipeline (Bolt 1.23.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1390 Kick off release pipeline (Bolt 1.23.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/13 4:24 PM Due Date: 2019/06/13 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-13) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-1389) Reconcile git commits, JIRA tickets, and versions (Bolt 1.23.0)
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1389 Reconcile git commits, JIRA tickets, and versions (Bolt 1.23.0) Issue Type: Sub-task Assignee: Tom Beech Created: 2019/06/13 4:24 PM Due Date: 2019/06/13 Priority: Normal Reporter: Tom Beech (Initial planned release date: 2019-06-13) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-1382) wait_until_available() incorrect results using Orchestrator
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1382 wait_until_available() incorrect results using Orchestrator Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312114.1560285784000.46915.1560467940796%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1382) wait_until_available() incorrect results using Orchestrator
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-1382
wait_until_available() incorrect results using Orchestrator
Change By:
Cas Donoghue
Release Notes Summary:
The plan function {{wait_until_available}} has been updated such that only targets which cannot be reached are returned as an error result when using the {{PCP}} transport.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312114.1560285784000.46911.1560467940676%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9698) Backport PUP-8967 to 5.5.x
Title: Message Title Kris Bosland commented on PUP-9698 Re: Backport PUP-8967 to 5.5.x Merged to master at a2363e5. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308037.1557423516000.46888.1560467340183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4305 "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300026.1552508578000.46881.1560467280568%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4402) Fix GIT_REF handling in ci-job-configs
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4402 Fix GIT_REF handling in ci-job-configs Issue Type: Bug Assignee: Austin Blatt Created: 2019/06/13 2:39 PM Priority: Normal Reporter: Austin Blatt PE's Manual Promotion Kickoff currently passes its git build info to the FOSS Lein Voom Deploy job, and it should not because the git SHA's are different on FOSS vs PE. FOSS lein voom deploy currently passes neither its build params nor its git build data to PE's ezbake build job, but it should pass its build params (like GIT_REF) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1382) wait_until_available() incorrect results using Orchestrator
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1382 wait_until_available() incorrect results using Orchestrator Change By: Cas Donoghue Assignee: Lucy Wyman Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312114.1560285784000.46815.1560461761490%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9555) Update FFI dependency for Ruby 2.6 compatibility
Title: Message Title Josh Cooper commented on PUP-9555 Re: Update FFI dependency for Ruby 2.6 compatibility We're blocked until we release a new ruby facter gem. Filed as FACT-1930. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299570.1552334903000.46755.1560461160433%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1930) Relax ruby facter ffi constraint for ruby 2.6
Title: Message Title Josh Cooper updated an issue Facter / FACT-1930 Relax ruby facter ffi constraint for ruby 2.6 Change By: Josh Cooper Team: Puppet Romania Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312360.1560460629000.46733.1560460800363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1930) Relax ruby facter ffi constraint for ruby 2.6
Title: Message Title Josh Cooper updated an issue Facter / FACT-1930 Relax ruby facter ffi constraint for ruby 2.6 Change By: Josh Cooper Fix Version/s: FACT 2.5.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312360.1560460629000.46732.1560460800221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1930) Relax ruby facter ffi constraint for ruby 2.6
Title: Message Title Josh Cooper created an issue Facter / FACT-1930 Relax ruby facter ffi constraint for ruby 2.6 Issue Type: Improvement Assignee: Unassigned Created: 2019/06/13 2:17 PM Priority: Normal Reporter: Josh Cooper If you try to bundle install puppet on ruby 2.6 on Windows, it will fail because the windows facter gem is constrained to: if RUBY_VERSION < '2.0.0' gem 'ffi', '<= 1.9.14', :require => false else gem 'ffi', '~> 1.9.18', :require => false end But ffi 1.9.x doesn't support ruby 2.6, as it was added in 1.10.0. We should relax facter's ffi dependency. The safest thing is to only relax the ffi dependency when running on ruby 2.6 or greater:
Jira (PUP-9750) optionally add pe_version to server_facts
Title: Message Title
Thomas Kishel commented on PUP-9750
Re: optionally add pe_version to server_facts
This sets server_facts['pe_version'] which sets/overrides the pe_version fact ... but only in the catalog compiled by the server:
[root@pe-201818-master ~]# cat /etc/puppetlabs/code/environments/production/manifests/site.pp
node default {
$gpev = get_pe_version()
if $gpev { notify { "PE Version ${gpev} | ${server_facts['pe_version']} | ${pe_version}": } }
}
[root@pe-201818-agent ~]# puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Loading facts
Jira (BOLT-1358) Powershell tasks on localhost do not use correct default PS_ARGS
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-1358
Powershell tasks on localhost do not use correct default PS_ARGS
Change By:
Cas Donoghue
Release Notes Summary:
Powershell scripts and tasks run over the local transport on windows hosts will no longer load profiles and are run with the {{Bypass}} execution policy to maintain parity with the winrm transport.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310878.1559318878000.46659.1560458400331%40Atlassian.JIRA.
For more options, visit
Jira (BOLT-1358) Powershell tasks on localhost do not use correct default PS_ARGS
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1358 Powershell tasks on localhost do not use correct default PS_ARGS Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310878.1559318878000.46653.1560458040108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3905) Disable ruby 2.1.5 automatically retrying idempotent http methods
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-3905 Disable ruby 2.1.5 automatically retrying idempotent http methods Change By: Heston Hoffman Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.65130.1422037228000.46630.1560456901443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9564) Puppet upgrades debian packages with pending updates when setting them on hold
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-9564 Puppet upgrades debian packages with pending updates when setting them on hold Change By: Heston Hoffman Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300439.1552654564000.46611.1560456480365%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8984) Add JSON output option to `puppet parser validate`
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-8984 Add JSON output option to `puppet parser validate` Change By: Heston Hoffman Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.189813.149427962.46505.1560451140768%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9495) Implement `print` method for `server_list_settings`
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-9495 Implement `print` method for `server_list_settings` Change By: Heston Hoffman Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295966.1550015035000.46475.1560450300448%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9697 Solaris Crontabs -> puppet resource cron only returns root account Change By: Josh Cooper Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.46432.1560449460782%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account
Title: Message Title Josh Cooper commented on PUP-9697 Re: Solaris Crontabs -> puppet resource cron only returns root account Merged to puppet#5.5.x in https://github.com/puppetlabs/puppet/commit/6e60fbe0ca6a2314e2d9863295a350a85986cd3d Merged to cron_core in https://github.com/puppetlabs/puppetlabs-cron_core/commit/c87086c52c75d2ebe21bb8082979b2127a8690d7 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.46428.1560449400538%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9746) Puppet ssl submit_request does not translate custom oids correctly
Title: Message Title Josh Cooper commented on PUP-9746 Re: Puppet ssl submit_request does not translate custom oids correctly Backported to 6.0.x in https://github.com/puppetlabs/puppet/commit/0e2f179c3b13de39306363705e12f6f9ccc6ac6c Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311950.1560208202000.46413.1560449040251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9746) Puppet ssl submit_request does not translate custom oids correctly
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9746 Puppet ssl submit_request does not translate custom oids correctly Change By: Josh Cooper Fix Version/s: PUP 6.6.0 Fix Version/s: PUP 6.0.10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311950.1560208202000.46400.1560448500538%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9698) Backport PUP-8967 to 5.5.x
Title: Message Title Charlie Sharpsteen commented on PUP-9698 Re: Backport PUP-8967 to 5.5.x Jorie Tappa Will this make it into the 5.5.15 release? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308037.1557423516000.46372.1560447360262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4345) Add name field to resource_events to avoid further duplication errors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4345 Add name field to resource_events to avoid further duplication errors Change By: Austin Blatt Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304800.1555358173000.46355.1560446460567%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4367) Make sure jackson databind is not excluded in any relevant pdb or pdbext branches
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4367 Make sure jackson databind is not excluded in any relevant pdb or pdbext branches Change By: Austin Blatt Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308133.1557439306000.46359.1560446460766%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1222
Support an "apply" step.
Change By:
Lucy Wyman
We should be able to handle simple apply actions in simple plans.* ` {{ apply_prep ` }} should be implicitly called on targets at least once in the plan.* It should support a data format of resource declaration.Observations:* must be an array so we can have manifest ordering* having type and title together on one line is preferable* Test that a type called type works{noformat}---steps: # Allows resources to be easily scannable. # Similar to step syntax where the step type or resource type is stored by the presence of a key. # Won't work with "parameters" type if one exists. - resources:- package: nginx- package: ssh- file: /tmp/foo parameters:content: "hello world" - description: "single resource in array"resources: - type: classtitle: "foo::bar"parameters: param1: foo noop: true{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1222
Support an "apply" step.
Change By:
Lucy Wyman
We should be able to handle simple apply actions in simple plans.* `apply_prep` should be implicitly called on targets at least once in the plan.* It should support a data format of resource declaration.Observations:* must be an array so we can have manifest ordering* having type and title together on one line is preferable * Test that a type called type works {noformat}---steps: # Can there be a parameter called "type" . - description: "single resource in array"resources: - type: classtitle: "foo::bar"param1: foonoop: true # Allows resources to be easily scannable. # Similar to step syntax where the step type or resource type is stored by the presence of a key. # Won't work with with "parameters" type if one exists. - resources:- package: nginx- package: ssh- file: /tmp/foo parameters:content: "hello world" - description: "single resource in array"resources: - type: classtitle: "foo::bar"parameters: param1: foo noop: true # Using refs may be confusing when people move to puppet code# Using refs forces users to understand some weird capitalization rules - description: "Use ref's as the key"Package['nginx']:File['/var/...']: content: $foo - description: "Use ref's as the key"- ref: Package['nginx']- ref: File['/var/...']content: $foo# No ordering is unacceptable - description: "single resource in hash by name"resources: foo::bar:_type: classparam1: foobefore: "File['/etc/fop']"noop: true# No ordering is unacceptable - description: "single resource in nested hash"resources: class:foo::bar: param1: class noop: true {noformat}
Add Comment
Jira (PDB-4347) Don't use a static temp table name for fact path gc
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4347 Don't use a static temp table name for fact path gc Change By: Rob Browning Release Notes Summary: PuppetDB should no longer log errors like this after if a previous garbage collection had failed in a particular way: "Error during garbage collection" "ERROR: relation "tmp_live_paths" already exists". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305777.1555967633000.46240.1560443280426%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4347) Don't use a static temp table name for fact path gc
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4347 Don't use a static temp table name for fact path gc Change By: Rob Browning Release Notes Summary: PuppetDB should no longer log errors like this after if a previous garbage collection had failed in a particular way: "Error during garbage collection" "ERROR: relation "tmp_live_paths" already exists". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305777.1555967633000.46231.1560443220372%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4389) Query for deactivated nodes
Title: Message Title Austin Blatt commented on PDB-4389 Re: Query for deactivated nodes Maheswaran Shanmugam Unfortunately, there's no easy way to fix that bug. Every time a node that is triggering that bug submits a catalog the node will be re-created and you'll see it in the console again. Currently, you'll have to downgrade to 2018.1.7 (or lower), or wait for 2018.1.9 to be released. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310994.155953334.46217.1560442740375%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1386) I need a workspace for files during the duration of a plan
Title: Message Title Alex Dreyer commented on BOLT-1386 Re: I need a workspace for files during the duration of a plan Henrik Lindberg That makes sense for reading files and accessing them from file resources/file_upload. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312278.1560378682000.46151.1560439740159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1386) I need a workspace for files during the duration of a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1386 I need a workspace for files during the duration of a plan Change By: Alex Dreyer Some plans build and distribute artifacts. These plans are hard to write because bolt does not have a `file_download` function or any natural space to store such artifacts. The project dir should provide a workspace that allows plans a central location to write and read data from.questions:1. Should this workspace persist between plans run in the same project?2. How can we ensure that files in the workspace are addressable in a way that doesn't conflict with modules. 3. How can Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit
Jira (BOLT-1360) Evaluate including upgrades for bolt gem dependencies in bolt packages
Title: Message Title Cas Donoghue commented on BOLT-1360 Re: Evaluate including upgrades for bolt gem dependencies in bolt packages The bundled modules could probably be evaluated to. At least package module https://forge.puppet.com/puppetlabs/package Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311108.1559598816000.46082.1560435840054%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4401) puppetdb : Error while attempting to create connection pool
Title: Message Title
zoen updated an issue
PuppetDB / PDB-4401
puppetdb : Error while attempting to create connection pool
Change By:
zoen
working with the version that I uploaded from forge https://github.com/puppetlabs/puppetlabs-puppetdb/tree/7.2.0puppet-agent 5.5.8 - working on Ubuntu 18.04.puppet-server version: 5.3.6 - working on Ubuntu 18.04.my puppet-run seems completely stuck applying the puppetdb recipes.someone could guide me for next steps. I am stuck. here the message log on puppetdb: The connection is not available - Caused by: org.postgresql.util.PSQLException: Connection to puppetdb.internet.net:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.- here my puppetdb definition on manifest:{noformat}class profile::puppetdb { class { '::puppetdb::database::postgresql' :listen_addresses=> $::fqdn,manage_package_repo => false,postgres_version=> '9.6', } class { '::puppetdb::server' :database_host => $::fqdn,automatic_dlo_cleanup => false,manage_firewall => false,listen_address=> '0.0.0.0',ssl_deploy_certs => true,ssl_set_cert_paths=> true,java_args => { '-Xmx' => '2g', '-Xms' => '512m',}, }}{noformat}- here the last puppet-run (without errrors...){noformat}Notice: /Stage[main]/Postgresql::Server::Install/Package[postgresql-server]/ensure: createdNotice: /Stage[main]/Puppetdb::Server/Package[puppetdb]/ensure: createdInfo: /Stage[main]/Puppetdb::Server/Package[puppetdb]: Scheduling refresh of Service[puppetdb]Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/owner: owner changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/group: group changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/mode: mode changed '0644' to '0600'Info: Class[Puppetdb::Server::Global]: Scheduling refresh of Service[puppetdb]Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/owner: owner changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/group: group changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/mode: mode changed '0644' to '0600'Notice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_psdatabase_username]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_psdatabase_password]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_classname]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_subprotocol]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_pgs]/ensure: createdNotice:
Jira (PDB-4401) puppetdb : Error while attempting to create connection pool
Title: Message Title
zoen updated an issue
PuppetDB / PDB-4401
puppetdb : Error while attempting to create connection pool
Change By:
zoen
working with the version that I uploaded from forge https://github.com/puppetlabs/puppetlabs-puppetdb/tree/7.2.0puppet-agent 5.5.8 - working on Ubuntu 18.04.puppet-server version: 5.3.6 - working on Ubuntu 18.04.my puppet-run seems completely stuck applying the puppetdb recipes.someone could guide me for next steps. I am stuck. here the message log on puppetdb: The connection is not available - Caused by: org.postgresql.util.PSQLException: Connection to puppetdb.internet.net:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.- here my puppetdb definition on manifest:{noformat}class profile::puppetdb { class { '::puppetdb::database::postgresql' :listen_addresses=> $::fqdn,manage_package_repo => false,postgres_version=> '9.6', } class { '::puppetdb::server' :database_host => $::fqdn,automatic_dlo_cleanup => false,manage_firewall => false,listen_address=> '0.0.0.0',ssl_deploy_certs => true,ssl_set_cert_paths=> true,java_args => { '-Xmx' => '2g', '-Xms' => '512m',}, }}{noformat}- here the last puppet-run (without errrors...){noformat}Notice: /Stage[main]/Postgresql::Server::Install/Package[postgresql-server]/ensure: createdNotice: /Stage[main]/Puppetdb::Server/Package[puppetdb]/ensure: createdInfo: /Stage[main]/Puppetdb::Server/Package[puppetdb]: Scheduling refresh of Service[puppetdb]Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/owner: owner changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/group: group changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/mode: mode changed '0644' to '0600'Info: Class[Puppetdb::Server::Global]: Scheduling refresh of Service[puppetdb]Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/owner: owner changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/group: group changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/mode: mode changed '0644' to '0600'Notice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_psdatabase_username]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_psdatabase_password]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_classname]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_subprotocol]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_pgs]/ensure: createdNotice:
Jira (PDB-4401) puppetdb : Error while attempting to create connection pool
Title: Message Title zoen updated an issue PuppetDB / PDB-4401 puppetdb : Error while attempting to create connection pool Change By: zoen Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312301.1560420511000.46013.1560429660434%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1387) bolt package in the puppet fedora/RH repository in conflict with system package
Title: Message Title Antenore Gatta created an issue Puppet Task Runner / BOLT-1387 bolt package in the puppet fedora/RH repository in conflict with system package Issue Type: Bug Assignee: Unassigned Components: bolt Created: 2019/06/13 4:56 AM Labels: packaging-repo packaging Priority: Normal Reporter: Antenore Gatta ON Fedora 30 there is a bolt package that is: Name : bolt Version : 0.7 Release : 2.fc30 Architecture : x86_64 Size : 533 k Source : bolt-0.7-2.fc30.src.rpm Repository : @System From repo : fedora Summary : Thunderbolt device manager URL : https://gitlab.freedesktop.org/bolt/bolt License : LGPLv2+ That is in conflict with: Name : bolt Version : 0.19.1 Release : 1.el7 Architecture : x86_64 Size : 16 M Source : bolt-0.19.1-1.el7.src.rpm Repository : puppet5 Summary : Stand alone task runner URL : https://www.puppet.com License : See components Description : Stand alone task runner I'm not sure who should change the name, if needed I can open a bug to Fedora. For now the workaround is to black-list the bolt package in the puppet repository [puppet5] name=Puppet 5 Repository el 7 - $basearch baseurl=http://yum.puppetlabs.com/puppet5/el/7/$basearch gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet5-release enabled=1 gpgcheck=1 exclude=bolt [puppet5-source] name=Puppet 5 Repository el 7 - Source baseurl=http://yum.puppetlabs.com/puppet5-nightly/el/7/SRPMS gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet5-release failovermethod=priority enabled=0 gpgcheck=1 exclude=bolt
Jira (PDB-4401) puppetdb : Error while attempting to create connection pool
Title: Message Title
zoen created an issue
PuppetDB / PDB-4401
puppetdb : Error while attempting to create connection pool
Issue Type:
Bug
Assignee:
Unassigned
Components:
PuppetDB
Created:
2019/06/13 3:08 AM
Priority:
Normal
Reporter:
zoen
working with the version that I uploaded from forge https://github.com/puppetlabs/puppetlabs-puppetdb/tree/7.2.0 puppet-agent 5.5.8 - working on Ubuntu 18.04. puppet-server version: 5.3.6 - working on Ubuntu 18.04. my puppet-run seems completely stuck applying the puppetdb recipes. someone could guide me for next steps. I am stuck. here the message log on puppetdb: The connection is not available - Caused by: org.postgresql.util.PSQLException: Connection to puppetdb.internet.net:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
here my puppetdb definition on manifest:
class profile::puppetdb {
class { '::puppetdb::database::postgresql' :
Jira (PDB-4401) puppetdb : Error while attempting to create connection pool
Title: Message Title
zoen updated an issue
PuppetDB / PDB-4401
puppetdb : Error while attempting to create connection pool
Change By:
zoen
working with the version that I uploaded from forge https://github.com/puppetlabs/puppetlabs-puppetdb/tree/7.2.0puppet-agent 5.5.8 - working on Ubuntu 18.04.puppet-server version: 5.3.6 - working on Ubuntu 18.04.my puppet-run seems completely stuck applying the puppetdb recipes.someone could guide me for next steps. I am stuck. here the message log on puppetdb: The connection is not available - Caused by: org.postgresql.util.PSQLException: Connection to puppetdb.internet.net:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.- here my puppetdb definition on manifest:{noformat}class profile::puppetdb { class { '::puppetdb::database::postgresql' :listen_addresses=> $::fqdn,manage_package_repo => false,postgres_version=> '9.6', } class { '::puppetdb::server' :database_host => $::fqdn,automatic_dlo_cleanup => false,manage_firewall => false,listen_address=> '0.0.0.0',ssl_deploy_certs => true,ssl_set_cert_paths=> true,java_args => { '-Xmx' => '2g', '-Xms' => '512m',}, }}{noformat}- here the last puppet-run (without errrors...){noformat}Notice: /Stage[main]/Postgresql::Server::Install/Package[postgresql-server]/ensure: createdNotice: /Stage[main]/Puppetdb::Server/Package[puppetdb]/ensure: createdInfo: /Stage[main]/Puppetdb::Server/Package[puppetdb]: Scheduling refresh of Service[puppetdb]Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/owner: owner changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/group: group changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Global/File[/etc/puppetlabs/puppetdb/conf.d/config.ini]/mode: mode changed '0644' to '0600'Info: Class[Puppetdb::Server::Global]: Scheduling refresh of Service[puppetdb]Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/owner: owner changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/group: group changed 'root' to 'puppetdb'Notice: /Stage[main]/Puppetdb::Server::Database/File[/etc/puppetlabs/puppetdb/conf.d/database.ini]/mode: mode changed '0644' to '0600'Notice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_psdatabase_username]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_psdatabase_password]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_classname]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_subprotocol]/ensure: createdNotice: /Stage[main]/Puppetdb::Server::Database/Ini_setting[puppetdb_pgs]/ensure: createdNotice:
Jira (PDB-4072) HA out-of-sync after restart
Title: Message Title Maheswaran Shanmugam commented on PDB-4072 Re: HA out-of-sync after restart Customer "DBS" is getting this issue again. "https://puppetlabs.zendesk.com/agent/tickets/35069" Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.274953.1536550707000.45873.1560413160519%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9746) Puppet ssl submit_request does not translate custom oids correctly
Title: Message Title Oana Tanasoiu updated an issue Puppet / PUP-9746 Puppet ssl submit_request does not translate custom oids correctly Change By: Oana Tanasoiu Fix Version/s: PUP 6.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311950.1560208202000.45852.1560409920435%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9691) Puppet pidlock incorrectly clears lock when running under bundler
Title: Message Title Oana Tanasoiu updated an issue Puppet / PUP-9691 Puppet pidlock incorrectly clears lock when running under bundler Change By: Oana Tanasoiu Fix Version/s: PUP 6.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307420.1556926648000.45849.1560409680292%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Henrik Lindberg commented on PUP-8969 Re: Sensitive parameters are not redacted from reports / agent output when used in templates A much simpler thing to do would be to make EPP wrap the result in a Sensitive if it interpolates something Sensitive. Doing the same for ERB means providing a different ERB or figuring out if it is possible to monkey patch Ruby's. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.262922.1530114614000.45833.1560407640410%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1386) I need a workspace for files during the duration of a plan
Title: Message Title Henrik Lindberg commented on BOLT-1386 Re: I need a workspace for files during the duration of a plan A similar thing in puppet was solved by reserving the module name environment. Could be solved for bolt in a better way by having an actual module named say workspace it contains the workspace management features. Just a thought... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312278.1560378682000.45831.1560407160162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
