Jira (PUP-9103) Build Puppet Agent for Ubuntu 16.04
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9103 Build Puppet Agent for Ubuntu 16.04 Issue Type: Story Assignee: Mihai Buzgau Created: 2018/09/05 12:44 AM Priority: Normal Reporter: Mihai Buzgau 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.co
Jira (PUP-9102) Publish Ubuntu 18.10 to vmpooler
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9102 Publish Ubuntu 18.10 to vmpooler Issue Type: Story Assignee: Sebastian Miclea Created: 2018/09/05 12:43 AM Priority: Normal Reporter: Mihai Buzgau 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.c
Jira (BOLT-791) Support running a task on a proxy node targeting a device or API with run-on
Title: Message Title Thomas Honey commented on BOLT-791 Re: Support running a task on a proxy node targeting a device or API with run-on At the very least if the target information hash is passed to the task/plan. Then the task author can deal with the connection creation there. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7141) Refactor required string dup in 3x runtime converter
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7141 Refactor required string dup in 3x runtime converter Change By: Henrik Lindberg 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title
David Schmitt created an issue
Puppet / PUP-9104
YAML safe_load too strict
Issue Type:
Bug
Affects Versions:
PUP 6.0.0
Assignee:
Unassigned
Created:
2018/09/05 5:35 AM
Priority:
Normal
Reporter:
David Schmitt
Puppet Version: current master Puppet Server Version: n/a OS Name/Version: n/a Actual Behavior: In some cases puppet creates {{transactionstore.yaml}}s that are not able to be read back, causing
Error: Transaction store file /home/david/.puppetlabs/opt/puppet/cache/devices/pavm/state/transactionstore.yaml is corrupt (Unknown alias: 1); replacing
Desired Behavior: No errors or stacktraces on regular puppet use. Reproduction: Thomas Franklin has put together a detailed description and a potential fix in https://github.com/Thomas-Franklin/puppet/commit/49b8e023c6c9bb551bd0ce21648a604042c490ff
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-9104
YAML safe_load too strict
Change By:
David Schmitt
*Puppet Version:* current master , e.g. ddd5610aa9ffb5eb9da13521f1fc68e562a2e0b3 *Puppet Server Version:* n/a*OS Name/Version:* n/a*Actual Behavior:*In some cases puppet creates a {{transactionstore.yaml}} s that are not able to be read back, causing {code}Error: Transaction store file /home/david/.puppetlabs/opt/puppet/cache/devices/pavm/state/transactionstore.yaml is corrupt (Unknown alias: 1); replacing{code}*Desired Behavior:*No errors or stacktraces on regular puppet use.*Reproduction:*[~thomas.franklin] has put together a detailed description and a potential fix in https://github.com/Thomas-Franklin/puppet/commit/49b8e023c6c9bb551bd0ce21648a604042c490ff
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
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-9104
YAML safe_load too strict
Change By:
David Schmitt
*Puppet Version:* current master, e.g. ddd5610aa9ffb5eb9da13521f1fc68e562a2e0b3*Puppet Server Version:* n/a*OS Name/Version:* n/a*Actual Behavior:*In some cases puppet creates a {{transactionstore.yaml}} that are not able to be read back, causing {code}Error: Transaction store file /home/david/.puppetlabs/opt/puppet/cache/devices/pavm/state/transactionstore.yaml is corrupt (Unknown alias: 1); replacing{code}*Desired Behavior:*No errors or stacktraces on regular puppet use.*Reproduction:*[~thomas.franklin] has put together a detailed description and a potential fix in https://github.com/Thomas-Franklin/puppet/commit/49b8e023c6c9bb551bd0ce21648a604042c490ff The issue is also visible in the panos acceptance pipelines: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/modules/view/networking/view/panos/view/master/job/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/8/
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-829) modulepath argument does not handle paths with spaces
Title: Message Title Thomas Honey created an issue Puppet Task Runner / BOLT-829 modulepath argument does not handle paths with spaces Issue Type: CI Blocker Affects Versions: BOLT 0.21.8 Assignee: Unassigned Components: CLI, Windows Created: 2018/09/05 5:50 AM Priority: Normal Reporter: Thomas Honey When trying to run the following. /cygdrive/c/Program\ Files/Puppet\ Labs/Puppet/sys/ruby/bin/bolt.bat task run service --no-ssl --modulepath 'C:/ProgramData/PuppetLabs/code/environments/production/modules;C:/ProgramData/PuppetLabs/code/modules;C:/Program Files/Puppet Labs/Puppet/puppet/modules' --nodes localhost --password root action="" name=W32Time --transport winrm --user Administrator 'C:\Program' is not recognized as an internal or external command, operable program or batch file.
Jira (BOLT-829) modulepath argument does not handle paths with spaces
Title: Message Title
Thomas Honey updated an issue
Puppet Task Runner / BOLT-829
modulepath argument does not handle paths with spaces
Change By:
Thomas Honey
When trying to run the following.{code:java}/cygdrive/c/Program\ Files/Puppet\ Labs/Puppet/sys/ruby/bin/bolt.bat task run service --no-ssl --modulepath 'C:/ProgramData/PuppetLabs/code/environments/production/modules;C:/ProgramData/PuppetLabs/code/modules;C:/Program Files/Puppet Labs/Puppet/puppet/modules' --nodes localhost --password root action="" name=W32Time --transport winrm --user Administrator'C:\Program' is not recognized as an internal or external command,operable program or batch file. {code}I amended the command with escaping and wrapping the argument in quotes.{code}-bash-4.3$ /cygdrive/c/Program\ Files/Puppet\ Labs/Puppet/sys/ruby/bin/bolt.bat task run service --no-ssl -m 'C:/ProgramData/PuppetLabs/code/environments/production/modules;C:/ProgramData/PuppetLabs/code/modules;C:/Program\ Files/Puppet\ Labs/Puppet/puppet/modules;' --nodes localhost --password root action="" name=W32Time --transport winrm --user Administrator'C:\Program' is not recognized as an internal or external command,operable program or batch file.{code}Removing the final path with the spaces, bolt runs fine. (ignore the auth issue) {code}-bash-4.3$ /cygdrive/c/Program\ Files/Puppet\ Labs/Puppet/sys/ruby/bin/bolt.bat task run service --no-ssl -m 'C:/ProgramData/PuppetLabs/code/environments/production/modules;C:/ProgramData/PuppetLabs/code/modules;' --nodes localhost --password root action="" name=W32Time --transport winrm --user AdministratorStarted on localhost...Failed on localhost: Authentication failed for http://localhost:5985/wsmanFailed on 1 node: localhostRan on 1 node in 0.36 seconds-bash-4.3$ -{code}This is currently blocking our puppet 6 nightly testing. Being tracked in https://tickets.puppetlabs.com/browse/FM-7304
Add Comment
Jira (BOLT-745) Apply manifest block cannot use functions from boltlib from module that declares metadata
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-745 Apply manifest block cannot use functions from boltlib from module that declares metadata Change By: Kenn Hussey Team: Bolt 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3490) Get rbac-client version from clj-parent in pdbext
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3490 Get rbac-client version from clj-parent in pdbext Change By: Kenn Hussey Team: PuppetDB 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2700) Migrate to trapperkeeper testutils/logging
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-2700 Migrate to trapperkeeper testutils/logging Change By: Kenn Hussey Team: PuppetDB 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3268) Don't just return nothing from applied-migrations if the query fails
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3268 Don't just return nothing from applied-migrations if the query fails Change By: Kenn Hussey Team: PuppetDB 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2354) agent is confused about cert state
Title: Message Title Noam Davida commented on PUP-2354 Re: agent is confused about cert state Still same issue, guys we can't work like this, can someone fix this please? This feature is useless: allow_duplicate_certs = true I'm using Puppet in lab env, needs to reinstall multiple machines daily, Please either fix above or release an option to not use certification at all. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2354) agent is confused about cert state
Title: Message Title Noam Davida updated an issue Puppet / PUP-2354 agent is confused about cert state Change By: Noam Davida Priority: Normal Critical 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8987) add resource_api gem to puppet gemspec
Title: Message Title David Schmitt commented on PUP-8987 Re: add resource_api gem to puppet gemspec If it is any help to you deciding whether to get this done or not, the PDK already walks folks through adding the gem dependency manually because otherwise nobody would get it yet. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-791) Support running a task on a proxy node targeting a device or API with run-on
Title: Message Title Alex Dreyer commented on BOLT-791 Re: Support running a task on a proxy node targeting a device or API with run-on Yeah it will be 100% up the task author to handle connecting to the device from the target info hash. We can't abstract that in the general case. For tasks in puppet-device modules we can probably provide some helpers. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3993) Add --upgrade-and-quit or similar for unattended multi-version upgrades
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3993 Add --upgrade-and-quit or similar for unattended multi-version upgrades Change By: Rob Browning Release Notes Summary: (Note: this feature was added to 5.2.x and to 6.0.0, so we have two sets of release notes depicted below. The 5.2.x notes should go on the 5.2.x branch, and then we'll merge them up to master (or 6.0.x), and then the 6.0 notes should be added to master (or 6.0.x).)*** For 6.0.0 ***- A `help` subcommand has been added to display usage information to standard output.- If an invalid command is specified, usage information will now be printed to standard error, not standard output.*** For 5.2.x *** [versioning]: ./versioning_policy.html#upgrades[multiple-major-upgrades]: ./upgrade.html#upgrading-across-multiple-major-versions## 5.2.?### New features- An `upgrade` subcommand has been added that should be useful for cases where you want to upgrade across multiple major versions without skipping major versions (as per the [versioning policy][versioning]). See [these notes [multiple-major-upgrades] for additional information.([PDB-3993](https://tickets.puppetlabs.com/browse/PDB-3993)) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9105) puppet node CLI assumes server name
Title: Message Title Wesley Moore created an issue Puppet / PUP-9105 puppet node CLI assumes server name Issue Type: Bug Affects Versions: PUP 5.5.6 Assignee: Unassigned Components: CLI Created: 2018/09/05 9:00 AM Fix Versions: PUP 5.5.6 Priority: Normal Reporter: Wesley Moore Puppet Version: 5.5.6 Puppet Server Version: 5.3.5 OS Name/Version: RHEL7 Running 'puppet node find' doesn't allow for setting the puppet server name. It assumes the hostname is 'puppet'. Desired Behavior: Actual Behavior: Example: $> puppet node find --terminus rest Error: Could not call 'find' on 'node': Failed to open TCP connection to puppet:8140 (No route to host... Add Comment
Jira (PDB-4060) Test merge master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4060 Test merge master Issue Type: Bug Assignee: Unassigned Created: 2018/09/05 9:17 AM Priority: Normal Reporter: gepetto-bot 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. Fo
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title Henrik Lindberg commented on PUP-9104 Re: YAML safe_load too strict Would be great to get that fix as a PR against puppet master. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9050) Beaker 4.0 Compatibility
Title: Message Title Michelle Schuknecht updated an issue Puppet / PUP-9050 Beaker 4.0 Compatibility Change By: Michelle Schuknecht Sprint: QE 2018-08-22, QE 2018-09-05 , QE 2018-09-19 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1043) Remove ability to specify file checksum in `content` property
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-1043 Remove ability to specify file checksum in `content` property Change By: Jacob Helwig Fix Version/s: PUP 6.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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1043) Remove ability to specify file checksum in `content` property
Title: Message Title Jacob Helwig commented on PUP-1043 Re: Remove ability to specify file checksum in `content` property This is turning into fairly major surgery to the File type, and will not be done in time for 6.0.0. We'll have to work on this for 7.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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-754) Add a cert whitelist to bolt-server
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-754 Add a cert whitelist to bolt-server Change By: Kate Lopresti Labels: 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-809) Make max_threads configurable for bolt-server
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-809 Make max_threads configurable for bolt-server Change By: Kate Lopresti Labels: 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6165) it should not be possible to disable manifest ordering
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-6165 it should not be possible to disable manifest ordering Change By: Jacob Helwig Sprint: Platform Core Hopper 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6165) it should not be possible to disable manifest ordering
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-6165 it should not be possible to disable manifest ordering Change By: Jacob Helwig Assignee: Jacob Helwig 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4061) Look into variables being exported by pdb packaging scripts
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4061 Look into variables being exported by pdb packaging scripts Issue Type: Improvement Assignee: Unassigned Created: 2018/09/05 9:57 AM Priority: Normal Reporter: Zachary Kent It looks like we're exporting some generically named variables in our packaging scripts which it may be a good idea to prefix with "puppet_blarg" or something along those lines. See the note here. Investigate where this is happening in ezbake and figure out if pdb can support some of these variables itself. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-664) Make file copy work over WinRM
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-664 Make file copy work over WinRM Change By: Lucy Wyman Assignee: Cas Donoghue 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9106) Windows file system ACLs should always write SYSTEM: (F)
Title: Message Title Ethan Brown created an issue Puppet / PUP-9106 Windows file system ACLs should always write SYSTEM: (F) Issue Type: Bug Affects Versions: PUP 5.5.6 Assignee: Unassigned Components: Windows Created: 2018/09/05 10:42 AM Fix Versions: PUP 6.0.0 Labels: windows ntfs acl Priority: Normal Reporter: Ethan Brown When creating Windows ACLs when writing file permissions, the current code allows for the SYSTEM ACE to be written as something other than F (Full Control). This can be problematic as it can result in files that cannot have permissions reset, or that may be inaccessible to Puppet itself (which typically runs as SYSTEM). In practical terms, there is no good reason to set SYSTEM permissions to anything other than F and Puppet should disallow that. At one point the Puppet code was modified as part of https://projects.puppetlabs.com/issues/15559 (related to PUP-5480) in https://github.com/puppetlabs/puppet/commit/b578ed48ac9585edb86b296e99f8aeeecc02fb4e#diff-a788175040b15f1e899dae62e4c1b8c6 to re-add a missing SYSTEM if it wasn't already specified. We never took the additional step of making sure that SYSTEM can only be set to F, which in hindsight, seems like the right approach, given what is now known about permissions management and the work that was done as part of PA-2019 and PUP-5985. One thing to note is that this will technically be
Jira (FACT-1880) SLES 15 fails acceptance tests due to not providing an os.release.minor value
Title: Message Title Scott Garman created an issue Facter / FACT-1880 SLES 15 fails acceptance tests due to not providing an os.release.minor value Issue Type: Bug Assignee: Scott Garman Created: 2018/09/05 11:06 AM Priority: Normal Reporter: Scott Garman For SLES 15, we now parse /etc/os-release instead of Suse's old /etc/SuSE-release file to determine os facts. Since SLES 15 doesn't have any point-releases yet, the VERSION_ID value it's parsing from /etc/os-release is simply "15". This is resulting in there being no os.release.minor to return. The acceptance test os_processors_and_kernel.rb uses a regex that expects os.release.full to return something with a point release - so "15.0" would pass, but "15" would not. After some discussion in the Platform Core channel, the consensus was that os.release.minor should always return a value, given that there's likely code which relies upon it to perform things like version arithmetic or comparisons. Add Comment
Jira (BOLT-794) Unable to call a task with a Sensitive string
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-794 Unable to call a task with a Sensitive string Change By: Kate Lopresti Labels: docs docs-reviewed 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6919) Puppet::Util::Windows::Process.execute should accept a working directory
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-6919
Puppet::Util::Windows::Process.execute should accept a working directory
Change By:
Ethan Brown
The Windows API supports setting a working directory when starting a process. However, Puppet does not currently allow setting this value programatically.The win32-process gem can pass {{cwd}} supplied through it's argument hash - see code at https://github.com/djberg96/win32-process/blob/win32-process-0.7.5/lib/win32/process.rb#L681Puppet currently uses {{Dir.chdir}} to set a working directory before creating a process - however, this might not always work properly on Windows. The {{cwd}} has {{File.directory?(dir)}} used to validate it, which could fail on UNC or other path types (like reparse points - i.e. symlinks) on Windows - meaning that {{Dir.chdir}} at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec.rb#L29 never gets called as expected.{{cwd}} should be passed in to {{Puppet::Util::Execution.execute}} at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec.rb#L59 / and the call to {{Process.create}} at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/process.rb#L12 should pass the {{arguments}} value through.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4062) Nodes Endpoint Doc Missing node_state as Filter Option
Title: Message Title Michelle Fredette moved an issue PuppetDB / PDB-4062 Nodes Endpoint Doc Missing node_state as Filter Option Change By: Michelle Fredette Method Found: Needs Assessment Workflow: Documentation Scrum Team Workflow Key: DOCUMENT PDB - 901 4062 Project: Documentation PuppetDB 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
Jira (PDB-4062) Nodes Endpoint Doc Missing node_state as Filter Option
Title: Message Title Michelle Fredette commented on PDB-4062 Re: Nodes Endpoint Doc Missing node_state as Filter Option hey PuppetDB - per our discussion yesterday, I'm assigning this to you. Let me know if you have any questions! 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9107) Deprecate non-manifest orderings
Title: Message Title Jacob Helwig created an issue Puppet / PUP-9107 Deprecate non-manifest orderings Issue Type: Improvement Assignee: Jacob Helwig Created: 2018/09/05 1:24 PM Fix Versions: PUP 5.5.z Priority: Normal Reporter: Jacob Helwig PUP-6165 is to remove all options other than "manifest" from the ordering setting, since there is only going to be one valid value for the setting, we may as well deprecate the setting itself, and remove it in 6.0.0. This deprecates the setting in 5.5.x. Add Comment
Jira (PUP-9107) Deprecate non-manifest orderings
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-9107 Deprecate non-manifest orderings Change By: Jacob Helwig Release Notes Summary: The "ordering" setting is deprecated, and will be removed in 6.0.0. The setting will always have a value of "manifest" in 6.0.0. Release Notes: Deprecation 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6165) it should not be possible to disable manifest ordering
Title: Message Title Jacob Helwig commented on PUP-6165 Re: it should not be possible to disable manifest ordering Seems like if the only valid option will be "manifest", that we might as well add a deprecation to 5.5.x, and remove the setting entirely in 6.0.0. PUP-9107 is to deprecate in 5.5.x. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-813) Support tilde expansion in nodes file path
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-813 Support tilde expansion in nodes file path Change By: Kate Lopresti Labels: docs-reviewed 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4063) Test merge master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4063 Test merge master Issue Type: Bug Assignee: Unassigned Created: 2018/09/05 1:43 PM Priority: Normal Reporter: gepetto-bot 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. Fo
Jira (BOLT-807) Local transport doesn't serialize arguments in environment variables to JSON
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-807 Local transport doesn't serialize arguments in environment variables to JSON Change By: Kate Lopresti Labels: docs-reviewed 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-812) Bolt does not correctly report Puppet absent running 'apply' on newer Powershell
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-812 Bolt does not correctly report Puppet absent running 'apply' on newer Powershell Change By: Kate Lopresti Labels: docs-reviewed 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-751) Move file_upload function to upload_file
Title: Message Title Kate Lopresti assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-751 Move file_upload function to upload_file Change By: Kate Lopresti Assignee: Kate Lopresti 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-751) Move file_upload function to upload_file
Title: Message Title Kate Lopresti assigned an issue to Unassigned Puppet Task Runner / BOLT-751 Move file_upload function to upload_file Change By: Kate Lopresti Assignee: Kate Lopresti 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-751) Move file_upload function to upload_file
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-751 Move file_upload function to upload_file Change By: Kate Lopresti Release Notes Summary: The 'file_upload' function is renamed to 'upload_file' to match the other verb-oriented core functions like 'run_task'. ' upload_file file_upload ' is deprecated and will be removed in a future release. Note that 'bolt file upload' is unchanged. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-751) Move file_upload function to upload_file
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-751 Move file_upload function to upload_file Change By: Kate Lopresti Labels: deprecation 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6919) Puppet::Util::Windows::Process.execute should accept a working directory
Title: Message Title Enis Inan commented on PUP-6919 Re: Puppet::Util::Windows::Process.execute should accept a working directory Ended up reverting this change – see https://github.com/puppetlabs/puppet/pull/7045. Note that the POSIX issue with cd'ing to the cwd when the user does not have permissions to access it would have been resolved in https://github.com/puppetlabs/puppet/pull/7034; however, that was not merged due to some other issues with the existing implementation. These were: Puppet::Util::Execution.execute still runs the command in the cwd even if the cwd cannot be accessed. There are some design questions around whether we can move the directory existence check to the top-level execute method so that both execute_posix + execute_windows can use it. Right now, we only do this in execute_posix while in execute_windows, we wrap the system call error. For reference, the original implementation of this ticket was merged here: https://github.com/puppetlabs/puppet/pull/7016 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. Fo
Jira (PUP-9108) Update `node clean` to not rely on the CA face
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9108 Update `node clean` to not rely on the CA face Change By: Maggie Dreyer Fix Version/s: PUP 6.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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9108) Update `node clean` to not rely on the CA face
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-9108 Update `node clean` to not rely on the CA face Issue Type: Task Assignee: Unassigned Created: 2018/09/05 2:25 PM Priority: Normal Reporter: Maggie Dreyer We are removing CA-related faces in Puppet 6, and the puppet node clean command relies on one of them. We should update its cert cleaning functionality to use the puppetserver-ca gem instead. Question: should that gem be considered a runtime dependency for the puppet gem, or should we only expect this functionality to work when there is a puppetserver package present? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9108) Update `node clean` to not rely on the CA face
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-9108 Update `node clean` to not rely on the CA face Change By: Maggie Dreyer Assignee: Maggie Dreyer 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9093) Add option to DataConverter to suppress warnings about stringification of rich data
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9093 Add option to DataConverter to suppress warnings about stringification of rich data Change By: Henrik Lindberg Fix Version/s: PUP 6.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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9093) Make Reported Event objects stringify rich data
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9093 Make Reported Event objects stringify rich data Change By: Henrik Lindberg Issue Type: New Feature Improvement 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6919) Puppet::Util::Windows::Process.execute should accept a working directory
Title: Message Title Enis Inan updated an issue Puppet / PUP-6919 Puppet::Util::Windows::Process.execute should accept a working directory Change By: Enis Inan Sprint: Platform OS 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9093) Make Reported Event objects stringify rich data
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9093 Make Reported Event objects stringify rich data Change By: Henrik Lindberg Summary: Add option to DataConverter to suppress warnings about stringification of Make Reported Event objects stringify rich data 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9093) Make Reported Event objects stringify rich data
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-9093
Make Reported Event objects stringify rich data
Change By:
Henrik Lindberg
ORIGINAL An option is needed in the ToDataConverter so that warnings for stringification of rich data is suppressed. This is needed because there is legitimate use cases where stringification is required. UPDATEThe legitimate use case was in {{Event}} objects in reports. There, rich-data cannot be allowed because nothing downstream from the report is prepared to handle rich data. The specification for reports even say that all values in Events (before/after) are supposed to be strings, but that is a lie since it is any JSON data type (but not any additional "rich data" encoding.
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...@g
Jira (PUP-9093) Make Reported Event objects stringify rich data
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9093 Make Reported Event objects stringify rich data Change By: Henrik Lindberg Release Notes Summary: With rich-data turned on for a catalog (now the default) a Report could contain rich data in reported events, and that was not good because nothing downstream from the agent is prepared to handle rich data. This is now fixed so that data in reported events are stringified when needed. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5985) Features are not being re-evaluated when a block is used
Title: Message Title Kris Bosland commented on PUP-5985 Re: Features are not being re-evaluated when a block is used Merged into master at 24ead48. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4064) Check current java version before installing with require-jdk
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4064 Check current java version before installing with require-jdk Issue Type: Improvement Assignee: Unassigned Created: 2018/09/05 5:06 PM Priority: Normal Reporter: Austin Blatt In the style of require-leiningen, we should check the version and type (oracle/open) of the current jdk before installing and using another. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
