Jira (PUP-9748) Puppet Device doesn't honor ENC-set Environment in 5.5.10 or later
Title: Message Title Adam Gardner updated an issue Puppet / PUP-9748 Puppet Device doesn't honor ENC-set Environment in 5.5.10 or later Change By: Adam Gardner *Puppet Version: 5.5.10 - 5.5.14 (5.5.8 works correctly)* *Puppet Server Version: 5.3.6* *OS Name/Version: Centos 7* ** Note that this probably affects at least some versions of Puppet 6.x, though I don't have the setup to verify that personally.*Steps to reproduce:* # Install Puppet Agent 5.5.10 or later # Configure a Device node in devices.conf and set up a certificate for it # Configure the ENC on the Master to supply an environment other than production for the device node # Run `puppet device --target --verbose`*Desired Behavior:*The application switches to the ENC-supplied environment before performing a plugin sync. This behavior can be observed under 5.5.8; the logs show "Notice: Local environment 'production' doesn't match server specified node environment 'foo', switching agent to 'foo'." prior to "Retrieving pluginfacts".*Actual Behavior:*The application remains in the production environment during pluginsync (and possibly after) unless a `–environment` flag is explicitly passed. No environment-switching occurs. If the module containing the device transport code is not present in the production environment, then the device transport files will be removed and the subsequent run will fail.*Notes* This seems likely to be related to PUP-8766, which changed the way that the puppet device application handles environments, and was incorporated into 5.5.10 as well as 6.0.5. Prior to PUP-8766, _only_ ENC-supplied environments were honored by the Puppet Device application, and the --environment flag did not function; now, the reverse situation is true. Add Comment
Jira (PUP-9748) Puppet Device doesn't honor ENC-set Environment in 5.5.10 or later
Title: Message Title Adam Gardner created an issue Puppet / PUP-9748 Puppet Device doesn't honor ENC-set Environment in 5.5.10 or later Issue Type: Bug Affects Versions: PUP 5.5.14, PUP 5.5.13, PUP 5.5.12, PUP 5.5.10 Assignee: Unassigned Created: 2019/06/11 7:46 PM Environment: Centos 7 Puppetserver 5.3.6 Puppet Agent 5.5.x (5.5.8 and earlier works, 5.5.10 through 5.5.14 does not). Priority: Normal Reporter: Adam Gardner Puppet Version: 5.5.10 - 5.5.14 (5.5.8 works correctly) Puppet Server Version: 5.3.6 OS Name/Version: Centos 7 **Note that this probably affects at least some versions of Puppet 6.x, though I don't have the setup to verify that personally. Steps to reproduce: Install Puppet Agent 5.5.10 or later Configure a Device node in devices.conf and set up a certificate for it Configure the ENC on the Master to supply an environment other than production for the device node Run `puppet device --target --verbose` Desired Behavior: The application switches to the ENC-supplied environment before performing a plugin sync. This behavior can be observed under 5.5.8; the logs show "Notice: Local environment 'production' doesn't match server specified node environment 'foo', switching agent to 'foo'." prior to "Retrieving pluginfacts". Actual Behavior: The application remains in the production environment during pluginsync (and possibly after) unless a `–environment` flag is explicitly passed. No environment-switch
Jira (PUP-8983) validate_cmd creates tmp file with inconsistent permissions
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-8983 validate_cmd creates tmp file with inconsistent permissions 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.263871.1530809754000.43336.1560298740546%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-271) unicode space causes oddly formatted output / missing text
Title: Message Title Jesse Scott commented on PDOC-271 Re: unicode space causes oddly formatted output / missing text Sorry for the delayed response, but this appears to be an issue in the underlying YARD gem's ability to detect documentation tags that include non-standard whitespace characters. I would suggest following up with https://github.com/lsegal/yard if this continues to be an issue for you. Please feel free to re-open this issue if you are sure it is a problem specific to puppet-strings. Thanks! 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.287706.1544123145000.43312.1560297600644%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9055) Compile catalogs on demand with user-specified facts
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-9055 Compile catalogs on demand with user-specified facts 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.102767.1445629515000.43303.1560297241613%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-269) Support documenting required modules
Title: Message Title Jesse Scott commented on PDOC-269 Re: Support documenting required modules This is an interesting idea, can you give us some examples of what type of code you are documenting where this would be useful? Is it that you just want more granularity than is expressed in the metadata.json dependencies of a module or are you using this to document role and profile code? 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.281168.153985289.43281.1560297060403%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-268) Colliding internal anchors on autogenerated pages
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-268 Colliding internal anchors on autogenerated pages Looks like we need to make the Table of Contents anchors use the same disambiguation algorithm as the Forge does for multiple headings with the same text value. We should also investigate if there is a standard for this so we can safely predict what the anchor values will be ahead of time. 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.280893.1539770862000.43278.1560296760242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1384) Inventory command
Title: Message Title
Corey Osman created an issue
Puppet Task Runner / BOLT-1384
Inventory command
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2019/06/11 4:33 PM
Priority:
Normal
Reporter:
Corey Osman
I would like to have an inventory command to interact with the inventory file, puppetdb or other place bolt retrieves the list of nodes from. This would allow me to see what is in the inventory before running and also write bootstrap scripts outside of bolt This command would prevent me from having to always parse out the inventory file to accomplish the same thing. Example:
#!/usr/bin/env bash
nodes=$(bolt inventory --nodes ubuntu)
for node in $nodes; do
ssh-copy-id ethos@${nodes}
done
Jira (BOLT-1383) Command to copy ssh identity to authorized keys
Title: Message Title Corey Osman created an issue Puppet Task Runner / BOLT-1383 Command to copy ssh identity to authorized keys Issue Type: New Feature Assignee: Unassigned Created: 2019/06/11 4:25 PM Priority: Normal Reporter: Corey Osman The first step when running bolt is to setup an ssh identity in the remote system's authorized_keys file, otherwise the user is burdened with typing passwords. We need a bolt command to perform this step automatically instead of create a bash for loop. This would look something like: bolt ssh-copy-id --nodes ubuntu Bolt would gather the nodes and use the default ssh identity or the one provided in the inventory file and use ssh-copy-id utility to copy over the identity and place in authorized keys file on the remote system. Add Comment
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9570 Catalog failure on first run due to pluginsync and environment switch Change By: Josh Cooper Fix Version/s: PUP 6.5.0 Fix Version/s: PUP 6.6.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.300842.1553021716000.43234.1560295500603%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9513) Deprecate SSL host, validators, indirected types and termini
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9513 Deprecate SSL host, validators, indirected types and termini Change By: Josh Cooper Fix Version/s: PUP 6.5.0 Fix Version/s: PUP 6.6.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.297867.1551401113000.43230.1560295440216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9650) Run rspec tests against ruby 2.6 or latest
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9650 Run rspec tests against ruby 2.6 or latest Change By: Josh Cooper Fix Version/s: PUP 6.y Fix Version/s: PUP 6.6.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.305737.155595275.43229.1560295440171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9638) Add an option to verify the CA bundle download against a fingerprint
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9638 Add an option to verify the CA bundle download against a fingerprint Change By: Josh Cooper Fix Version/s: PUP 6.y Fix Version/s: PUP 6.6.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.304299.1554918771000.43226.1560295380397%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9650) Run rspec tests against ruby 2.6 or latest
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9650 Run rspec tests against ruby 2.6 or latest Change By: Josh Cooper Fix Version/s: PUP 6.5.0 Fix Version/s: PUP 6.y 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.305737.155595275.43225.1560295380390%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9638) Add an option to verify the CA bundle download against a fingerprint
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9638 Add an option to verify the CA bundle download against a fingerprint Change By: Josh Cooper Fix Version/s: PUP 6.5.0 Fix Version/s: PUP 6.y 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.304299.1554918771000.43224.1560295380340%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 Nick Burgan commented on PUP-9746 Re: Puppet ssl submit_request does not translate custom oids correctly Can this go into 6.0.x as well, since `puppet ssl` is present there too? 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.43199.1560295080459%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9466) Readd password protected private key support
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-9466 Readd password protected private key support 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.293409.1548380786000.43181.1560294600501%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 Manually merged to master in bb48440828 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.43153.1560294008117%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 Merged to 6.4.x in https://github.com/puppetlabs/puppet/commit/7d556caf655140a03f16c6ff5495ce0eb337 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.43147.1560293880638%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4392) Merge-up, branch, and create pipelines (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4392 Merge-up, branch, and create pipelines (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Merge-up, branch, and create pipelines (PuppetDB 6. 4 3 . 0 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.311753.155994676.43136.1560293460870%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4393) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4393 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Reconcile git commits, JIRA tickets, and versions (PuppetDB 6. 4 3 . 0 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.311754.1559946766000.43131.1560293460635%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4396) Update winston (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4396 Update winston (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Update winston (PuppetDB 6. 4 3 . 0 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.311758.1559946798000.43120.1560293400781%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4394) Bump versions, push directly, and tag (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4394 Bump versions, push directly, and tag (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Bump versions, push directly, and tag (PuppetDB 6. 4 3 . 0 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.311755.1559946773000.43128.1560293401158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4395) Check builds, promote to PE (PuppetDB 6.3.3)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-4395 Check builds, promote to PE (PuppetDB 6.3.3) Change By: Nirupama Mantha Summary: Check builds, promote to PE (PuppetDB 6. 4 3 . 0 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.311756.1559946782000.43124.1560293400970%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
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Lucy Wyman
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. {{catch_errors}} functions accept a list of types of errors to catch and then a block of code to run where if it errors the plan will continue executing. You cannot specify what to do when an error is raised. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.* If an error is raised in the block it will be returned from the block, otherwise the result will be returned.* A {{return}} or {{break}} statement in a catch_errors block should break/return from the block not from the plan. Note: We should have a consistent way of catching returns in lambdas in Puppet behave 'normally' - Alex will talk to Henrik about it. with no special handling * We should document using this with {{case}} to create more reasonable error-handling, where case looks at the result and acts on different types of errors. {noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query()}{noformat}
Add Comment
This message was sent by Atlassian
Jira (PUP-9643) protection against illegal methods in legacy functions hides syntax error
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-9643 protection against illegal methods in legacy functions hides syntax error 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.304723.1555336207000.43100.1560292980433%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9688) User resource sets password on every puppet agent run (Windows)
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-9688 User resource sets password on every puppet agent run (Windows) 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.306584.1556533521000.43075.1560292500503%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
Prior to 6.4, {{puppet agent --fingerprint}} would print the hash of the client cert or client's CSR. In the process it would generate a private key, submit download the CSR CA cert and CRL , attempt to download the client cert (which might be signed due to autosigning) , and print the cert 's fingerprint (if we got one) . If that failed it would attempt to load the client's CSR locally or fallback retrieve the CSR from the server, and print its fingerprint.Note {{puppet agent --fingerprint}} never submitted the CSR, but it might seem to work if a previous agent run had already submitted the CSR , and either due to manual intervention or autosigning, the CSR is signed before {{puppet agent -- fingerprint }} is run .In 6.4 the option doesn't work, because it's trying to pass {{onetime: true}} keyword arguments, which the state machine doesn't accept. It also doesn't print the hash of the CSR, which is important for things like PUP-9715.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
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
Prior to 6.4, {{puppet agent --fingerprint}} would print the hash of the client cert or client's CSR. It In the process it would generate a private key, submit the CSR, as part of that process attempt to download the client cert (which might be signed due to autosigning) and print the cert fingerprint (if we got one) or fallback to the CSR fingerprint .In 6.4 the option doesn't work, because it's trying to pass {{onetime: true}} keyword arguments, which the state machine doesn't accept. It also doesn't print the hash of the CSR, which is important for things like PUP-9715.
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
Jira (PUP-9389) Add new parameter to File for tempfile staging location
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-9389 Add new parameter to File for tempfile staging location 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.289892.1545419608000.43045.1560291360390%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 Reid Vandewiele commented on BOLT-1382 Re: wait_until_available() incorrect results using Orchestrator Filed a starter PR at https://github.com/puppetlabs/bolt/pull/1031. 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.42975.1560290280518%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 Reid Vandewiele commented on BOLT-1382 Re: wait_until_available() incorrect results using Orchestrator It kinda looks like we operate in batches, and don't have any concept of some targets in a batch being unavailable while others in the same batch are. https://github.com/puppetlabs/bolt/blob/377350ecf2a9e193b1013fb05554cd12e7418245/lib/bolt/executor.rb#L284-L300 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.42927.1560287940220%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
Reid Vandewiele created an issue
Puppet Task Runner / BOLT-1382
wait_until_available() incorrect results using Orchestrator
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/06/11 1:43 PM
Priority:
Normal
Reporter:
Reid Vandewiele
The wait_until_available() function seems to all-or-nothing succeed/fail when using --transport pcp. See below for an example. The same test plan will return the expected results when run over ssh.
[root@pe-xl-core-0 bolt-project]# cat site-modules/util/plans/test.pp
plan util::test (
TargetSpec $nodes,
) {
$connection_results = wait_until_available(get_targets($nodes),
wait_time => 0,
Jira (PUP-9566) Allow to send extra headers when requesting a catalog compilation
Title: Message Title Josh Cooper commented on PUP-9566 Re: Allow to send extra headers when requesting a catalog compilation One of our main concerns is people assuming puppet uses HTTPS to connect to puppetservers, and thinking it's ok to add sensitive headers, such as session ids. However, if puppet sends headers everywhere, then it could leak sensitive info when retrieving file content from insecure HTTP file servers. I think restricting the extra headers to puppet-y requests is possible, it's just unfortunately not as clean as it could be due to the various ways the agent makes http requests. 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.300606.1552923936000.42713.1560280260305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1379) Document that "upload file" is able to handle directories as well as files
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1379 Document that "upload file" is able to handle directories as well as files 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.311900.1560188799000.42705.1560279960302%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1379) Document that "upload file" is able to handle directories as well as files
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1379 Document that "upload file" is able to handle directories as well as files 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.311900.1560188799000.42703.1560279900352%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 Josh Cooper updated an issue Puppet / PUP-9691 Puppet pidlock incorrectly clears lock when running under bundler Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.5.0 Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 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
Jira (PUP-9691) Puppet pidlock incorrectly clears lock when running under bundler
Title: Message Title Josh Cooper commented on PUP-9691 Re: Puppet pidlock incorrectly clears lock when running under bundler Merged to 5.5.x in https://github.com/puppetlabs/puppet/commi/3eda57c2d5a51de86e8eac387f9f57835cdd6211 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.42688.1560279420611%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 assigned an issue to Kris Bosland Puppet / PUP-9746 Puppet ssl submit_request does not translate custom oids correctly Change By: Josh Cooper Assignee: Kris Bosland 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.42676.1560279240681%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 Sprint: 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.311950.1560208202000.42679.1560279240822%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1381) Audit the Hands on Lab
Title: Message Title Tom Beech assigned an issue to Tom Beech Puppet Task Runner / BOLT-1381 Audit the Hands on Lab Change By: Tom Beech Assignee: Tom Beech 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.312071.1560271869000.42644.1560279000436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1376 Support puppetfile -> forge -> baseurl setting in bolt.yaml 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.311712.1559939792000.42614.1560278040446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4398) Adjust "configure expiration" command to accept an optional list of certnames
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4398 Adjust "configure expiration" command to accept an optional list of certnames Change By: Zachary Kent Assignee: Zachary Kent 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.312075.1560273282000.42359.1560273301369%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4398) Adjust "configure expiration" command to accept an optional list of certnames
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4398 Adjust "configure expiration" command to accept an optional list of certnames Issue Type: Improvement Assignee: Unassigned Created: 2019/06/11 10:14 AM Priority: Normal Reporter: Zachary Kent Allow the configure expiration to take an optional list of certnames to allow bulk updates in one command. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1316 The plan language should have a catch_errors functions Change By: Lucy Wyman 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.309066.155804176.42305.1560272220517%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1381) Audit the Hands on Lab
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1381 Audit the Hands on Lab Change By: Lucy Wyman The Bolt hands on lab hasn't been reviewed / updated in a while. We should review it to make sure it isClear up Up to dateDemonstrates bolt featuresEasy to understandAccurate / works Updates:- Install Bolt + setup VMs- Start with a Boltdir- Build each lesson in a common directory- Lessons should not conflict, and should be able to have everything in the same directory- Lessons should be modular - one should not depend on completing a previous one 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 di
Jira (BOLT-1381) Audit the Hands on Lab
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1381 Audit the Hands on Lab Issue Type: Task Assignee: Unassigned Created: 2019/06/11 9:51 AM Priority: Normal Reporter: Lucy Wyman The Bolt hands on lab hasn't been reviewed / updated in a while. We should review it to make sure it is Clear up to date Demonstrates bolt features Easy to understand Accurate / works Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1380) OSCON Demo
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1380 OSCON Demo Change By: Lucy Wyman The demo should be 'scripted', and allow users to interact with a Bolt environment.3-4 laptops would be ideal, dedicated to Bolt.Demo system requirements:1. Being able to display text and have users acknowledge text to 'move on' in the demo2. Demo should have retry logic and validation of commands before moving on3. Need readline to work4. Demos should be modular and separate from each other.5. It'd be nice if you can tab complete the demo expected inputPossible ideas:- Quiz / game show format for learning Bolt- Just a running demo that folks can watch - more of a 'video' formatTech possibilities:- Puppet learning quest- Generic repl building software?- Learning / lesson building software?- Something else?To do:- Find demo system solution that meets above requirements- Port existing demo from https://github.com/puppetlabs/bolt_demo_env to new techModify the existing demo:- Remove the network example- Add Example of apply- Example of embedding Bolt into an existing non-Puppet project?- Vagrant plugin? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1380) OSCON Demo
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1380 OSCON Demo Change By: Lucy Wyman The demo should be 'scripted', and allow users to interact with a Bolt environment.3-4 laptops would be ideal, dedicated to Bolt.Demo system requirements:1. Being able to display text and have users acknowledge text to 'move on' in the demo2. Demo should have retry logic and validation of commands before moving on3. Need readline to work4. Demos should be modular and separate from each other.5. It'd be nice if you can tab complete the demo expected input Possible ideas: - Quiz / game show format for learning Bolt - Just a running demo that folks can watch - more of a 'video' formatTech possibilities:- Puppet learning quest- Something else?- Port existing demo from https://github.com/puppetlabs/bolt_demo_env to new techModify the existing demo:- Remove the network example- Add Example of apply- Example of embedding Bolt into an existing non-Puppet project?- Vagrant plugin? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1380) OSCON Demo
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1380 OSCON Demo Change By: Lucy Wyman The demo should be 'scripted', and allow users to interact with a Bolt environment.3-4 laptops would be ideal, dedicated to Bolt.Demo system requirements:1. Being able to display text and have users acknowledge text to 'move on' in the demo2. Demo should have retry logic and validation of commands before moving on3. Need readline to work4. Demos should be modular and separate from each other.5. It'd be nice if you can tab complete the demo expected inputPossible ideas:- Quiz / game show format for learning Bolt- Just a running demo that folks can watch - more of a 'video' formatTech possibilities:- Puppet learning quest- Something else? To do: - Find demo system solution that meets above requirements- Port existing demo from https://github.com/puppetlabs/bolt_demo_env to new techModify the existing demo:- Remove the network example- Add Example of apply- Example of embedding Bolt into an existing non-Puppet project?- Vagrant plugin? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1380) OSCON Demo
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1380 OSCON Demo Change By: Lucy Wyman The demo should be 'scripted', and allow users to interact with a Bolt environment.3-4 laptops would be ideal, dedicated to Bolt.Demo system requirements:1. Being able to display text and have users acknowledge text to 'move on' in the demo2. Demo should have retry logic and validation of commands before moving on3. Need readline to work4. Demos should be modular and separate from each other.5. It'd be nice if you can tab complete the demo expected input 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 discuss
Jira (BOLT-1302) Build packages for Fedora 30
Title: Message Title Cas Donoghue commented on BOLT-1302 Re: Build packages for Fedora 30 Note making fedora packages public will require fedora 30 to be added to https://github.com/puppetlabs/build-data/blob/release/builder_data.yaml#L124 which is gated by TSR work on general enablement. 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.308420.1557771933000.42207.1560270600221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1380) OSCON Demo
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1380 OSCON Demo Issue Type: Task Assignee: Unassigned Created: 2019/06/11 9:17 AM Priority: Normal Reporter: Lucy Wyman 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.
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 Sprint: Bolt Ready for Grooming 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.302484.1554141988000.42126.1560269580590%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1376 Support puppetfile -> forge -> baseurl setting in bolt.yaml Change By: Alex Dreyer 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.311712.1559939792000.42066.1560268920154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9747) Bolt provides too many attributes to remote transports
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-9747 Bolt provides too many attributes to remote transports Change By: Alex Dreyer From https://groups.google.com/a/puppet.com/forum/#!topic/team-network-automation/bEiFEudGyrc and private slack convo with [~alex]Bolt provides a lot of attributes to remote transports that the Resource API is not prepared to handle. Change the resource api transport layer to silently discard any attributes passed in as connection_info from the list of "default" attributes bolt provides if they do not match up the transport is not prepared to receive them.The following keys come from uri parsing in bolt and are likely to be used in transport schema 's schema but may not always . * For each discarded attribute that matches the list they should be filtered out when not present in the schema(from https://github.com/puppetlabs/puppet-resource_api#usable-within-the-schema emit with password added.):uri - Use when you need to specify a info message specific URL to connect to . All of the following keys will be computed from the uri if possible. In the future more url parts may be computed from the URI as well. * For each discarded attribute that matches host - Use to specify and IP or address to connect to.port - The port the list in transport should connect to.protocol - Use to specify which protocol the transport should use for example http, https ://github , ssh or tcpuser - The user the transport should connect as . com/puppetlabs/puppet password - resource_api#non the password to use when connectingThe following keys are meta keys bolt uses and should not be included in transport schemasrun - usable on - within This is used by bolt to determine which target to proxy to. Transports should not rely on this key.remote - the transport - schema emit a debug message This is used to determine which transport to load . It should always be the transport class name "declassified". remote- * For every other discarded attribute emit a warning message Any key starting with remote- is reserved for future use . These keys are reserved for future URI parsing use but not currenlty exposed.path - reserved as a uri partquery - reserved as a uri part Add Comment
Jira (PDB-4397) Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer]
Title: Message Title Austin Blatt commented on PDB-4397 Re: Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer] This may be a problem with the module dependency metadata. You can try disabling the automatic dlo cleanup with automatic_dlo_cleanup => false or forcing the systemd module to a version greater than or equal to 2.0.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.312001.1560267294000.42031.1560267780733%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9747) Bolt provides too many attributes to remote transports
Title: Message Title David Schmitt updated an issue Puppet / PUP-9747 Bolt provides too many attributes to remote transports Change By: David Schmitt From https://groups.google.com/a/puppet.com/forum/#!topic/team-network-automation/bEiFEudGyrc and private slack convo with [~alex]Bolt provides a lot of attributes to remote transports that the Resource API is not prepared to handle. Change the resource api transport layer to silently discard any attributes from the list of "default" attributes bolt provides passed in as connection_info if they do not match up the transport is not prepared to receive them 's schema .* For each discarded attribute that matches the list in https://github.com/puppetlabs/puppet-resource_api#usable-within-the-schema emit a info message. * For each discarded attribute that matches the list in https://github.com/puppetlabs/puppet-resource_api#non-usable-within-the-schema emit a debug message.* For every other discarded attribute emit a warning message. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4397) Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer]
Title: Message Title
Renzoren updated an issue
PuppetDB / PDB-4397
Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer]
Change By:
Renzoren
- 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.the puppet catalog seems not working well. I don't know if the issue is the Bionic: Any idea about the issue?{noformat}Info: Using configured environment 'puppetv5'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Retrieving localesInfo: Loading factsError: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer]: has no parameter named 'enable' has no parameter named 'active' (file: /etc/puppetlabs/puppet/r10k/puppetv5/modules/legacy/modules/puppetdb/manifests/server.pp, line: 302) on node 01. puppet5db puppetdb . nym2. internet.netWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4397) Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer]
Title: Message Title Renzoren created an issue PuppetDB / PDB-4397 Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer] Issue Type: Bug Assignee: Unassigned Components: PuppetDB Created: 2019/06/11 8:34 AM Priority: Blocker Reporter: Renzoren 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. the puppet catalog seems not working well. I don't know if the issue is the Bionic: Any idea about the issue? Info: Using configured environment 'puppetv5' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving local
Jira (PUP-9747) Bolt provides too many attributes to remote transports
Title: Message Title David Schmitt created an issue Puppet / PUP-9747 Bolt provides too many attributes to remote transports Issue Type: Bug Affects Versions: PUP 6.4.2 Assignee: David Schmitt Created: 2019/06/11 8:25 AM Priority: Critical Reporter: David Schmitt From https://groups.google.com/a/puppet.com/forum/#!topic/team-network-automation/bEiFEudGyrc and private slack convo with Alex Dreyer Bolt provides a lot of attributes to remote transports that the Resource API is not prepared to handle. Change the resource api transport layer to silently discard any attributes from the list of "default" attributes bolt provides if the transport is not prepared to receive them. Add Comment
Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5
Title: Message Title Athanasios Douitsis commented on FACT-1926 Re: ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5 Many thanks then. I'll let the port maintainer know, in case he wants to include your patch with the present version. 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.309683.1558519845000.41884.1560261121057%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9744) Create acceptance test for PUP-9047
Title: Message Title David Schmitt commented on PUP-9744 Re: Create acceptance test for PUP-9047 good point. 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.311833.1560175214000.41876.1560261060350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5
Title: Message Title Gabriel Nagy commented on FACT-1926 Re: ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5 Great! We'll proceed with merging and closing this then. The fix will get into the next release of facter/puppet-agent. 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.309683.1558519845000.41863.1560260640330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5
Title: Message Title Athanasios Douitsis commented on FACT-1926 Re: ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5 Okay, I just run a quick test with your patch. With --debug, I get: 2019-06-11 16:37:01.358477 DEBUG leatherman.execution:93 - executing command: /sbin/route -n get default 2019-06-11 16:37:01.359456 DEBUG | - route to: 0.0.0.0 2019-06-11 16:37:01.359518 DEBUG | - destination: 0.0.0.0 2019-06-11 16:37:01.359575 DEBUG | - mask: 0.0.0.0 2019-06-11 16:37:01.359624 DEBUG | - gateway: 147.102.222.200 2019-06-11 16:37:01.359678 DEBUG | - fib: 0 2019-06-11 16:37:01.359780 DEBUG | - interface: vmx0 2019-06-11 16:37:01.359872 DEBUG leatherman.execution:469 - completed processing output: closing child pipes. 2019-06-11 16:37:01.359976 DEBUG leatherman.execution:563 - process exited with status code 0. 2019-06-11 16:37:01.360030 DEBUG puppetlabs.facter - got primary interface: "vmx0" And the final primary interface is changed to vmx0, as it should. How may I be of further assistance? 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.309683.1558519845000.41856.1560260400367%40Atlassian.JIRA. For more options, visit https://groups.google
Jira (PUP-9729) Solaris zone acceptance tests are failing
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9729 Solaris zone acceptance tests are failing 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.311200.1559667095000.41840.1560259860950%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1929) Report disks serial numbers
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1929 Report disks serial numbers 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.310677.1559162327000.41825.1560259740646%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1929) Report disks serial numbers
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1929 Report disks serial numbers 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.310677.1559162327000.41822.1560259740548%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5
Title: Message Title Athanasios Douitsis commented on FACT-1926 Re: ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5 Hello, I'll have to rebuild the port with the patch applied. Let me get back to you about that within the week. Athanasios 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.309683.1558519845000.41794.1560258300172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1910) Mountpoint fact only shows tmpfs and physical mounts
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-1910 Mountpoint fact only shows tmpfs and physical mounts Change By: Oana Tanasoiu Assignee: Oana Tanasoiu 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.299364.1552075723000.41696.1560248340456%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 Sebastian Miclea assigned an issue to Sebastian Miclea Puppet / PUP-9697 Solaris Crontabs -> puppet resource cron only returns root account Change By: Sebastian Miclea Assignee: Henrik Lindberg Sebastian Miclea 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.41646.1560244260520%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
