Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Kris Bosland commented on PUP-2958 Re: Rapid-fire puppet runs cause race condition with SSL data Verified manual tests listed in https://github.com/puppetlabs/puppet/pull/7555. 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.42950.1405977404000.37980.1559868003887%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1269) Prompt for sensitive data from inventory.
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1269 Prompt for sensitive data from inventory. Change By: Cas Donoghue Release Notes Summary: A new plugin in inventory v2 allows setting configuration values via a prompt. 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.306225.1556137227000.37933.1559863920394%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1343) Bolt docs: Add info on location of Bolt directory
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1343 Bolt docs: Add info on location of Bolt directory Change By: Cas Donoghue 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.310124.1558720885000.37929.1559863680374%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1343) Bolt docs: Add info on location of Bolt directory
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1343 Bolt docs: Add info on location of Bolt directory 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.310124.1558720885000.37925.1559863620265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1375) Send release announcements (Bolt 1.22.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1375 Send release announcements (Bolt 1.22.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/06/06 4:18 PM Due Date: 2019/06/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-06-07) 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
Jira (BOLT-1374) Docs for bolt release (Bolt 1.22.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1374 Docs for bolt release (Bolt 1.22.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/06/06 4:18 PM Due Date: 2019/06/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-06-07) Release notes and docs changes for bolt 1.22.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1370) Kick off release pipeline (Bolt 1.22.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1370 Kick off release pipeline (Bolt 1.22.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/06/06 4:17 PM Due Date: 2019/06/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-06-07) 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-1373) Update homebrew-puppet (Bolt 1.22.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1373 Update homebrew-puppet (Bolt 1.22.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/06/06 4:17 PM Due Date: 2019/06/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-06-07) 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-1372) Update the release spreadsheet (Bolt 1.22.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1372 Update the release spreadsheet (Bolt 1.22.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/06/06 4:17 PM Due Date: 2019/06/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-06-07) Update the release google spreadsheet for Bolt 1.22.0. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1371) Publish release artifacts (Bolt 1.22.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1371 Publish release artifacts (Bolt 1.22.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/06/06 4:17 PM Due Date: 2019/06/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-06-07) Run the Bolt shipping pipeline. Set REF to 1.22.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-1369) Reconcile git commits, JIRA tickets, and versions (Bolt 1.22.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1369 Reconcile git commits, JIRA tickets, and versions (Bolt 1.22.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/06/06 4:17 PM Due Date: 2019/06/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-06-07) 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-1368) Bolt 1.22.0 2019-06-07 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1368 Bolt 1.22.0 2019-06-07 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/06/06 4:17 PM Priority: Normal Reporter: Cas Donoghue Bolt 1.22.0 2019-06-07 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Kris Bosland commented on PUP-2958 Re: Rapid-fire puppet runs cause race condition with SSL data Passed CI in 51f852185979d748fdaf3079d96e3b7e3614cbee. 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.42950.1405977404000.37844.1559862361954%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1269) Prompt for sensitive data from inventory.
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1269 Prompt for sensitive data from inventory. 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.306225.1556137227000.37803.1559861160197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1269) Prompt for sensitive data from inventory.
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1269 Prompt for sensitive data from inventory. Change By: Cas Donoghue Labels: docs 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.306225.1556137227000.37801.1559861101357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9362) Identical test content with different descriptions
Title: Message Title Kris Bosland commented on PUP-9362 Re: Identical test content with different descriptions Passed CI in 51f852185979d748fdaf3079d96e3b7e3614cbee. 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.288698.1544725859000.37790.1559861040510%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 Kris Bosland commented on PUP-3905 Re: Disable ruby 2.1.5 automatically retrying idempotent http methods Passed CI in d942eb1. 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.37741.1559859602226%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1341) Support version 4 terraform state files in terraform inventory plugin
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1341 Support version 4 terraform state files in terraform inventory plugin Change By: Melissa Amos Labels: docs docs_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.310025.155865782.37733.1559859060474%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option Change By: Melissa Amos Labels: docs docs_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.309580.1558449511000.37723.1559858880705%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option Change By: Melissa Amos Labels: docs 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.309580.1558449511000.37617.1559854920721%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option Change By: Melissa Amos Component/s: DOCS 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.309580.1558449511000.37622.1559854920967%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1261) Common debugging and best practices documents
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1261 Common debugging and best practices documents Change By: Nick Lewis Assignee: Nick Lewis 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.305719.1555863895000.37345.1559846760288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4360) pdbbox to support configuring IPv6
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4360 pdbbox to support configuring IPv6 Change By: Robert Roland Assignee: Robert Roland 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.306368.1556211615000.37339.1559846701144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4385) Update ezbake to 2.0.3 to add redhat-7-fips support
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4385 Update ezbake to 2.0.3 to add redhat-7-fips support Change By: Robert Roland Assignee: Robert Roland 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.310791.1559240847000.37296.1559845380532%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option 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.309580.1558449511000.37223.1559843160519%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1366) Allow plans to return uniform Type, including on error
Title: Message Title
Reid Vandewiele updated an issue
Puppet Task Runner / BOLT-1366
Allow plans to return uniform Type, including on error
Change By:
Reid Vandewiele
It isn't possible today for a plan author to formally signal to callers that the plan failed (surfacing an error without requiring the caller to provide distinct (and not bound by convention) code paths for "ok" vs. "error". E.g.{code}$results = case ($plan_result = run_plan('mymodule::myplan', '_catch_errors' => true,)) { Error: { $plan_result.details['result_set'] } default: { $plan_result }}{code}Ideally, a caller should be able to expect a consistent return type regardless of whether or not the plan failed; just like a caller can always expect an object of type ResultSet to be returned from {{run_task}}.Allow for a moment that a plan _always_ returns an object of type PlanResult. If this is true, we can generalize success/failure based on {{$pr.ok}}, just as ResultSet handling can be based on {{$rs.ok}}. If a PlanResult is not ok (it failed), we can generalize access to the error raised via e.g. {{$pr.error}}. The PlanResult object can define a standard interface to data returned by a plan, such as defining a {{.value}} method, and the index method ({{.[]}}) for easy access to returned data keys.A caller could then simplify their code to e.g.{code}$result = run_plan('mymodule::myplan', _catch_errors => true,)run_task('mymodule::next_step, $result.value.ok_set){code}OR{code}$result['summary']{code}OR{code}if !$result.ok { # handle it}{code}...etc., depending on what the plan author chooses to return.Being able to rely on the datatype returned by {{run_plan}} greatly simplifies how plan authors can call and deal with the results from running other plans. One way of doing this might be to create a new type, PlanResult, which akin to ResultSet would come with a standard set of methods to interact with it. We could additionally define PlanResult::Error, which is still a PlanResult, but adds a {{.error}} method to access an included Error object, and would be compatible with code like {{case $result \{ Error: \{ ... \} \}}}.We could extend {{fail_plan}} to return a PlanResult::Error, if given a PlanResult return value and an Error. Plan authors could then choose to create well-formed plans in an opt-in way.If we didn't have to deal with existing plans I'd say just always return a PlanResult, with a little more automation around it and less effort from the plan author. Maybe it's a better enough experience to make a change in 2.0.
Jira (BOLT-1366) Allow plans to return uniform Type, including on error
Title: Message Title Reid Vandewiele updated an issue Puppet Task Runner / BOLT-1366 Allow plans to return uniform Type, including on error Change By: Reid Vandewiele Summary: Overhaul user experience handling plan errors Allow plans to return uniform Type, including on error 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.311455.155977910.37100.1559840700328%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver Change By: Josh Cooper Assignee: Josh Cooper 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.309697.1558538932000.37045.1559839380419%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver Change By: Josh Cooper Sprint: Coremunity Hopper Platform Core KANBAN 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.309697.1558538932000.37042.1559839320293%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 Josh Cooper updated an issue Puppet / PUP-3905 Disable ruby 2.1.5 automatically retrying idempotent http methods Change By: Josh Cooper Fix Version/s: PUP 6.4.3 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.36976.1559838120584%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver Change By: Josh Cooper Fix Version/s: PUP 6.4.3 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.309697.1558538932000.36973.1559838060392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9720) puppet agent --fingerprint is broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9720 puppet agent --fingerprint is broken Change By: Josh Cooper Affects Version/s: PUP 6.4.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.310230.1558735767000.36971.1559838060286%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9720) puppet agent --fingerprint is broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9720 puppet agent --fingerprint is broken Change By: Josh Cooper Fix Version/s: PUP 6.4.3 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.310230.1558735767000.36970.1559838060224%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 Josh Cooper updated an issue Puppet / PUP-9564 Puppet upgrades debian packages with pending updates when setting them on hold Change By: Josh Cooper Fix Version/s: PUP 6.4.3 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.36965.1559838000812%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 Josh Cooper updated an issue Puppet / PUP-9564 Puppet upgrades debian packages with pending updates when setting them on hold Change By: Josh Cooper Fix Version/s: PUP 6.5.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.300439.1552654564000.36958.1559837881270%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 Josh Cooper commented on PUP-9564 Re: Puppet upgrades debian packages with pending updates when setting them on hold Passed CI in b89f3ce7f5 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.36952.1559837881015%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9430) Decide tagging/label system to distinguish platform specific/platform agnostic tests
Title: Message Title John Duarte commented on PUP-9430 Re: Decide tagging/label system to distinguish platform specific/platform agnostic tests If a test is completely platform agnostic, can it be moved to the integration test layer? If the answer is 'yes', then I would advocate for such a move and a tag/label at the acceptance test layer would not be 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.291629.1547234694000.36849.1559830020823%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9726) Refactor long running acceptance tests to exectute in less than 45 seconds
Title: Message Title
John Duarte updated an issue
Puppet / PUP-9726
Refactor long running acceptance tests to exectute in less than 45 seconds
Change By:
John Duarte
*As a* puppet tester *I want* to keep the execution time of individual acceptance tests under 45 seconds *So that* I can get test feedback fasterAcceptance tests are expensive.The following acceptance tests take longer than 45 seconds to execute on the reference RHEL 7 platform. These tests should be refactored to reduce there execution time below 45 seconds (preferably below 30 seconds). Total execution time for the tests in the sample below was 3506.51 seconds. If all of these tests were successfully executed in 30 secs each, then the overall test suite execution time would be reduced by about 30% (on RHEL 7 as of 2019.05.31). Tests that take longer than 45 seconds to run on RHEL7 along with there execution time:{noformat}acceptance/tests/direct_puppet/cached_catalog_remediate_local_drift.rb 52.35acceptance/tests/direct_puppet/catalog_uuid_correlates_catalogs_with_reports.rb 55.81acceptance/tests/direct_puppet/static_catalog_env_control.rb 114.42acceptance/tests/environment/agent_runs_pluginsync_with_proper_environment.rb 55.61acceptance/tests/environment/custom_type_provider_from_same_environment.rb 47.64acceptance/tests/environment/enc_nonexistent_directory_environment.rb 58.88acceptance/tests/environment/environment_scenario-bad.rb 106.58acceptance/tests/environment/use_agent_environment_when_enc_doesnt_specify.rb 88.39acceptance/tests/environment/use_agent_environment_when_no_enc.rb 81.42acceptance/tests/environment/use_enc_environment.rb 76.63acceptance/tests/environment/use_enc_environment_for_files.rb 46.97acceptance/tests/environment/use_enc_environment_for_pluginsync.rb 67.49acceptance/tests/environment/use_environment_from_environmentpath.rb 71.33acceptance/tests/language/exported_resources.rb 48.25acceptance/tests/language/pcore_generate_env_isolation.rb 63.53acceptance/tests/loader/autoload_from_resource_type_decl.rb 64.57acceptance/tests/lookup/lookup.rb 57.79acceptance/tests/lookup/lookup_rich_values.rb 56.28acceptance/tests/lookup/merge_strategies.rb 78.82acceptance/tests/lookup/v3_config_and_data.rb 68.38acceptance/tests/ordering/master_agent_application.rb 53.52acceptance/tests/parser_functions/puppet_lookup_cmd.rb 171.06acceptance/tests/pluginsync/4420_pluginfacts_should_be_resolvable_on_agent.rb 81.22acceptance/tests/reports/cached_catalog_status_in_report.rb 66.33acceptance/tests/reports/corrective_change_outside_puppet.rb 82.52acceptance/tests/reports/corrective_change_via_puppet.rb 81.63acceptance/tests/reports/failover_master.rb 118.09acceptance/tests/reports/submission.rb 79.67acceptance/tests/security/cve-2013-4761_injection_of_class_names_loading_code.rb 54.48acceptance/tests/ssl/autosign_command.rb 116.72acceptance/tests/ssl/certificate_extensions.rb 178.28acceptance/tests/utf8/utf8-in-catalog.rb 158.18acceptance/tests/utf8/utf8-in-function-args.rb 54.22acceptance/tests/i18n/modules/puppet_agent.rb
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9719 Can't run puppet agent after installing the MSI using the SYSTEM account Change By: Mihai Buzgau Sprint: PR - Triage 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.310162.1558726819000.36683.1559815320378%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9719 Can't run puppet agent after installing the MSI using the SYSTEM account Change By: Mihai Buzgau 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.310162.1558726819000.36681.1559815320309%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9719 Can't run puppet agent after installing the MSI using the SYSTEM account Change By: Mihai Buzgau Team: Windows 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.310162.1558726819000.36679.1559815200464%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9566) Allow to send extra headers when requesting a catalog compilation
Title: Message Title Nacho Barrientos commented on PUP-9566 Re: Allow to send extra headers when requesting a catalog compilation Hi Rob, Thanks for coming back to us. In our case actually, as explained by David, we only need to add custom headers to the requests sent by the agents when they chat to the Puppet servers. It'd be perhaps interesting to configure the HTTP client to restrict what type of requests will be modified (by path, for instance) but indeed it's not worth to spend time on this due to how the client is implemented. This is totally an agent-oriented change proposal. In our case our agents only talk to the Puppet servers so to make use of this new feature the only thing that we had to do configuration-wise was to add the new setting to the [agent] section of the puppet.conf available on the agents and that was it. Puppet servers were left untouched as we don't need them to send any extra headers to any endpoint. I personally don't see a risk if the default behavior is to not to send anything extra so nothing changes, that indeed combined with a good description in the documentation. Obviously administrators could send anything they wanted but that's their choice. On top of that, there's nothing harmful that you could naively do (like when using a switch), users must explicitly configure what data to send in those arbitrary headers. Overloading the User-Agent could be a solution but I think it's far from being elegant. Actually we're already using that header for something else and adding non-standard data there could be painful as it'd require doing some post-processing on our monitoring pipelines to remove undesired stuff. We cannot provide much more information than what has been described in previous posts, not because we can't share more details but because there isn't much more really. We want to send metadata from the agent side that will be consumed by the ingress layer to make routing decisions. As Puppet talks HTTP we think that HTTP headers is a good fit for this. Using extended attributes in the client's certificate is unfortunately not an option for us at the moment. This new feature was born in the context of deploying our masters on Kubernetes clusters, however it could be useful in many more situations outside of the containers world. Add Comment
Jira (BOLT-1367) CLI options don't override inventory settings
Title: Message Title
Christoph Jähnigen updated an issue
Puppet Task Runner / BOLT-1367
CLI options don't override inventory settings
Change By:
Christoph Jähnigen
I have configured the SSH transport options in my inventory.yaml:{code :java }version: 2groups: - name: testtargets: - name: testconfig: transport: ssh ssh:user: userprivate-key: some_key{code} If I try to use the --private-key CLI option still the private key as configured in the inventory file get's used. I need to remove the private-key from the inventory file to have the command line option being used. My expectation would be that command line options generally override config file settings.
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
Jira (BOLT-1367) CLI options don't override inventory settings
Title: Message Title Christoph Jähnigen created an issue Puppet Task Runner / BOLT-1367 CLI options don't override inventory settings Issue Type: Bug Affects Versions: BOLT 1.21.0 Assignee: Unassigned Components: CLI Created: 2019/06/06 12:36 AM Priority: Normal Reporter: Christoph Jähnigen I have configured the SSH transport options in my inventory.yaml: version: 2 groups: - name: test targets: - name: test
