Jira (PUP-11774) Adding lots of hosts on Windows results in "permission denied" errors for some of them
Title: Message Title Dirk Heinrichs commented on PUP-11774 Re: Adding lots of hosts on Windows results in "permission denied" errors for some of them Josh Cooper, thanks for looking into it. You wrote "multiple", but your output only shows adding two hosts. As I wrote in the description, you'd need to add at least 20 to 30 host entries in one agent run for the error to show up and then it also doesn't happen all the time. The complete error message is: Error: Puppet::Util::FileType::FileTypeFlat could not write C:/Windows/System32/drivers/etc/hosts: Permission denied @ rb_sysopen - C:/Windows/System32/drivers/etc/hosts Error: /Stage[init]/Hosts/Host[XXX]: Could not evaluate: Puppet::Util::FileType::FileTypeFlat could not write C:/Windows/System32/drivers/etc/hosts: Permission denied @ rb_sysopen - C:/Windows/System32/drivers/etc/hosts and it shows up after multiple tens of entries have already been created w/o problems, and afterwards another bunch of entries is created. Sometimes this happens multiple times during one agent run, sometimes not at all. "Permission denied" showing up on a Windows host after lots of successful writes to the same file usually indicates a locking problem, rather than a real permission problem. Maybe this can be solved/worked around by simply adding a retry... Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-4080) support S3 URL as the file type 'source'
Title: Message Title Dirk Heinrichs commented on PUP-4080 Re: support S3 URL as the file type 'source' Hmmm, still not... Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.70204.142546711.5548.1686144420125%40Atlassian.JIRA.
Jira (PUP-11774) Adding lots of hosts on Windows results in "permission denied" errors for some of them
Title: Message Title Dirk Heinrichs commented on PUP-11774 Re: Adding lots of hosts on Windows results in "permission denied" errors for some of them Any news here? This is quite annoying as it requires two Puppet runs to completely setup new Windows hosts. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.482158.1677828568000.13218.1684130520020%40Atlassian.JIRA.
Jira (PUP-11774) Adding lots of hosts on Windows results in "permission denied" errors for some of them
Title: Message Title
Dirk Heinrichs created an issue
Puppet / PUP-11774
Adding lots of hosts on Windows results in "permission denied" errors for some of them
Issue Type:
Bug
Affects Versions:
PUP 7.21.0
Assignee:
Unassigned
Components:
Windows
Created:
2023/03/02 11:29 PM
Priority:
Major
Reporter:
Dirk Heinrichs
Puppet Version: 7.21.0 Puppet Server Version: latest OS Name/Version: Windows Server 2019+ When managing a lot of "hosts" resources on Windows (by means of collecting exported resources), the first ones are applied without problems, but later ones fail with
Error: Puppet::Util::FileType::FileTypeFlat could not write C:/Windows/System32/drivers/etc/hosts: Permission denied @ rb_sysopen - C:/Windows/System32/drivers/etc/hosts
which looks like some kind of race condition to me. Steps to reproduce: Apply the following class on a new Windows host when Puppet is already managing at least 20 or 30 other hosts, all of which have the same class applied:
class hosts {
# Let each host create a host entry as exported resource
Jira (PUP-11720) Package provider "windows" concatenates "source" and "install_options" to one command
Title: Message Title Dirk Heinrichs commented on PUP-11720 Re: Package provider "windows" concatenates "source" and "install_options" to one command Nevermind, was a problem in my environment. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479393.1674475712000.3153.1674484920022%40Atlassian.JIRA.
Jira (PUP-11720) Package provider "windows" concatenates "source" and "install_options" to one command
Title: Message Title
Dirk Heinrichs created an issue
Puppet / PUP-11720
Package provider "windows" concatenates "source" and "install_options" to one command
Issue Type:
Bug
Affects Versions:
PUP 7.20.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2023/01/23 4:08 AM
Priority:
Critical
Reporter:
Dirk Heinrichs
Puppet Version: 7.21 Puppet Server Version: 4.0.1 OS Name/Version: Windows Server 2016+ While trying to install from an "exe" installer, the package provider concatenates the "source" path with the given "install_options" and tries to execute the result as command. Example:
package { 'Apache Tomcat 7.0 Tomcat7 (remove only)':
alias => 'Tomcat7',
ensure => installed,
source => 'C:\PuppetStore\Tomcat\apache-tomcat-7.0.109.exe',
Jira (PUP-11681) Package provider "pip3" fails to target pip from virtual env on first run
Title: Message Title Dirk Heinrichs commented on PUP-11681 Re: Package provider "pip3" fails to target pip from virtual env on first run Josh Cooper , thanks a lot, that helped me get things working. For the record: I finally ended up with a defined type "python::venv" which sets up a single virtual environment together with its modules. The "exec" for creating the venv, as well as the "package" resources for each module, are now created as tagged virtual resources, which are finally realized using Exec <| tag == 'PythonVenvSetup' |> -> Package <| tag == 'PythonVenvModule' |> This allows me to create as much virtual environments as I want, even in a loop, in just one single agent run. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-6524) The shell used with exec resource provider=shell should be configurable
Title: Message Title Dirk Heinrichs commented on PUP-6524 Re: The shell used with exec resource provider=shell should be configurable I wonder why this hasn't been implemented in 6(!!!) years. It's a matter of simply copying lib/puppet/provider/exec/shell.rb to lib/puppet/provider/exec/bash.rb, change its name from ":shell" to ":bash" on line 1 and every occurrence of "/bin/sh" (Hint: there are exactly two of them) to "/bin/bash". Two minutes, problem solved. So, please, just do it. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.120640.1457566032000.61712.1669711920038%40Atlassian.JIRA.
Jira (PUP-11681) Package provider "pip3" fails to target pip from virtual env on first run
Title: Message Title
Dirk Heinrichs updated an issue
Puppet / PUP-11681
Package provider "pip3" fails to target pip from virtual env on first run
Change By:
Dirk Heinrichs
*Puppet Version:* 7.20.0*Puppet Server Version:* latest*OS Name/Version:* Debian 11Given the following Puppet class: {code:puppet}# Install Python, and optionally configure different virtual# environments with a set of given modules# Parameters:# - venvs: A list of virtual environments to be installed,# together with a set of modules. It should have the following# content:# python::venvs:# - name: foo# modules:# - name: bar# version: 1.2.3# - name: baz# version: latest# - name: no_modules# modules: []# ...## NOTE: Module version defaults to latest if not specifiedclass python ( venvs = [],) { $venv_base_path = '/opt/venvs' package { 'python3': ensure => latest, } ['python3-pip', 'python3-venv'].each |$pkg| { package { $pkg: ensure => latest, require => Package['python3'], } } file { 'venv_base': path => $venv_base_path, ensure => directory, } $venvs.each |$venv| { $venv_path = "${venv_base_path}/${venv['name']}/bin" $pip = "${venv_path}/pip" exec { "setup_venv_${venv['name']}": command => "python3 -m venv --upgrade ${venv_base_path}/${venv['name']}", path => $facts['path'], unless => "test -L ${venv_path}/python3", } $venv['modules'].each |$module| { $mod_ver = if $module['version'] { $module['version'] } else { latest } package { "mod_${venv['name']}_${module['name']}": name => $module['name'], ensure => $mod_ver, provider => 'pip3', command => $pip, require => Exec["setup_venv_${venv['name']}"], } } }}{code}and the following input data: {code:yaml}python::venvs: - name: foomodules: - name: cffi - name: barmodules: - name: celery - name: bazmodules: - name: celeryversion: 4.4.7{code} the pip3 package provider fails on first run.*Desired Behavior:*First run of the class should succeed w/o error.*Actual Behavior:*The class needs two runs to succeed because the first one errors out with {code:java}Error: Could not prefetch package provider 'pip3': Provider pip3 package command '/opt/venvs/bar/bin/pip' does not exist on this host{code}The second run finally succeeds because this time '/opt/venvs/bar/bin/pip' exists.
Jira (PUP-11681) Package provider "pip3" fails to target pip from virtual env on first run
Title: Message Title
Dirk Heinrichs updated an issue
Puppet / PUP-11681
Package provider "pip3" fails to target pip from virtual env on first run
Change By:
Dirk Heinrichs
*Puppet Version:* 7.20.0*Puppet Server Version:* latest*OS Name/Version:* Debian 11Given the following Puppet class: {code: java puppet }# Install Python, and optionally configure different virtual# environments with a set of given modules # Parameters:# - venvs: A list of virtual environments to be installed,# together with a set of modules. It should have the following# content:# python::venvs:# - name: foo# modules:# - name: bar# version: 1.2.3# - name: baz# version: latest# - name: no_modules# modules: []# ...## NOTE: Module version defaults to latest if not specifiedclass specifiedclass python ( venvs = [],) { $venv_base_path = '/opt/venvs' package { 'python3': ensure => latest, } ['python3-pip', 'python3-venv'].each |$pkg| { package { $pkg: ensure => latest, require => Package['python3'], } } file { 'venv_base': path => $venv_base_path, ensure => directory, } $venvs.each |$venv| { $venv_path = "${venv_base_path}/${venv['name']}/bin" $pip = "${venv_path}/pip" exec { "setup_venv_${venv['name']}": command => "python3 -m venv --upgrade ${venv_base_path}/${venv['name']}", path => $facts['path'], unless => "test -L ${venv_path}/python3", } $venv['modules'].each |$module| { $mod_ver = if $module['version'] { $module['version'] } else { latest } package { "mod_${venv['name']}_${module['name']}": name => $module['name'], ensure => $mod_ver, provider => 'pip3', command => $pip, require => Exec["setup_venv_${venv['name']}"], } } }}{code}and the following input data: {code: java yaml }python::venvs: - name: foomodules: - name: cffi - name: barmodules: - name: celery - name: bazmodules: - name: celeryversion: 4.4.7{code} the pip3 package provider fails on first run.*Desired Behavior:*First run of the class should succeed w/o error.*Actual Behavior:*The class needs two runs to succeed because the first one errors out with {code:java}Error: Could not prefetch package provider 'pip3': Provider pip3 package command '/opt/venvs/bar/bin/pip' does not exist on this host{code}The second run finally succeeds because this time '/opt/venvs/bar/bin/pip' exists.
Jira (PUP-11681) Package provider "pip3" fails to target pip from virtual env on first run
Title: Message Title
Dirk Heinrichs updated an issue
Puppet / PUP-11681
Package provider "pip3" fails to target pip from virtual env on first run
Change By:
Dirk Heinrichs
*Puppet Version:* 7.20.0*Puppet Server Version:* latest*OS Name/Version:* Debian 11Given the following Puppet class: {code:java} # Install Python, and optionally configure different virtual# environments with a set of given modules# Parameters:# - venvs: A list of virtual environments to be installed,# together with a set of modules. It should have the following# content:# python::venvs:# - name: foo# modules:# - name: bar# version: 1.2.3# - name: baz# version: latest# - name: no_modules# modules: []# ...## NOTE: Module version defaults to latest if not specifiedclass python ( venvs = [],) { $venv_base_path = '/opt/venvs' package { 'python3': ensure => latest, } ['python3-pip', 'python3-venv'].each |$pkg| { package { $pkg: ensure => latest, require => Package['python3'], } } file { 'venv_base': path => $venv_base_path, ensure => directory, } $venvs.each |$venv| { $venv_path = "${venv_base_path}/${venv['name']}/bin" $pip = "${venv_path}/pip" exec { "setup_venv_${venv['name']}": command => "python3 -m venv --upgrade ${venv_base_path}/${venv['name']}", path => $facts['path'], unless => "test -L ${venv_path}/python3", } $venv['modules'].each |$module| { $mod_ver = if $module['version'] { $module['version'] } else { latest } package { "mod_${venv['name']}_${module['name']}": name => $module['name'], ensure => $mod_ver, provider => 'pip3', command => $pip, require => Exec["setup_venv_${venv['name']}"], } } }}{code}and the following input data: {code:java} python::venvs: - name: foomodules: - name: cffi - name: barmodules: - name: celery - name: bazmodules: - name: celeryversion: 4.4.7{code} the pip3 package provider fails on first run.*Desired Behavior:*First run of the class should succeed w/o error.*Actual Behavior:*The class needs two runs to succeed because the first one errors out with {code:java} Error: Could not prefetch package provider 'pip3': Provider pip3 package command '/opt/venvs/bar/bin/pip' does not exist on this host{code}The second run finally succeeds because this time '/opt/venvs/bar/bin/pip' exists.
Jira (PUP-11681) Package provider "pip3" fails to target pip from virtual env on first run
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-11681 Package provider "pip3" fails to target pip from virtual env on first run Issue Type: Bug Affects Versions: PUP 7.20.0 Assignee: Unassigned Created: 2022/11/25 6:59 AM Environment: Linux Priority: High Reporter: Dirk Heinrichs Puppet Version: 7.20.0 Puppet Server Version: latest OS Name/Version: Debian 11 Given the following Puppet class: # Install Python, and optionally configure different virtual # environments with a set of given modules# Parameters: # - venvs: A list of virtual environments to be installed, # together with a set of modules. It should have the following
Jira (PUP-11479) Support for BLAKE2 checksums
Title: Message Title Dirk Heinrichs updated an issue Puppet / PUP-11479 Support for BLAKE2 checksums Change By: Dirk Heinrichs The [BLAKE2|https://www.blake2.net/] family of cryptographic hash algorithms outperform outperforms SHA2/3 by a factor of 2 (according to my tests with a 267M file) while at the same time claiming to be as secure.It would thus be nice to have support for it in the file resource. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.441178.1648038518000.7817.1648040640096%40Atlassian.JIRA.
Jira (PUP-11479) Support for BLAKE2 checksums
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-11479 Support for BLAKE2 checksums Issue Type: Improvement Affects Versions: PUP 7.14.0, PUP 6.26.0 Assignee: Unassigned Created: 2022/03/23 5:28 AM Priority: Normal Reporter: Dirk Heinrichs The BLAKE2 family of cryptographic hash algorithms outperform SHA2/3 by a factor of 2 (according to my tests with a 267M file) while at the same time claiming to be as secure. It would thus be nice to have support for it in the file resource. Add Comment
Jira (PUP-9514) tidy: Allow removal of old directories, even if not empty
Title: Message Title Dirk Heinrichs commented on PUP-9514 Re: tidy: Allow removal of old directories, even if not empty OK, tested on Windows and it's working there, too. Anyway, after more than 2 years I can't remember anymore what exactly wasn't working back then. Thanks Josh Cooper for looking into it. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.298539.1551862945000.4830.1636628340029%40Atlassian.JIRA.
Jira (PUP-9514) tidy: Allow removal of old directories, even if not empty
Title: Message Title Dirk Heinrichs commented on PUP-9514 Re: tidy: Allow removal of old directories, even if not empty Could this be a Windows-only thing? I see you tested it on Linux. Anyway, I've already moved it into a Powershell script, triggered by a scheduled task. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.298539.1551862945000.4742.1636615740037%40Atlassian.JIRA.
Jira (PUP-11189) Add functions to iterate over files/templates in the current module
Title: Message Title Dirk Heinrichs commented on PUP-11189 Re: Add functions to iterate over files/templates in the current module Reid Vandewiele, thanks a lot for the detailed explanation. Yes, the request was to add (a) new function(s), not to modify any existing ones. I will definitely try to implement "module_files()" myself (using your example above) to get a quick result. However, I also think this might be useful for others, too, so it would be really great to have it shipped as part of Puppet itself. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408658.1627373801000.99868.1628144340032%40Atlassian.JIRA.
Jira (PUP-11189) Add functions to iterate over files/templates in the current module
Title: Message Title Dirk Heinrichs commented on PUP-11189 Re: Add functions to iterate over files/templates in the current module Reid Vandewiele, my use case is to manage files on the agent based on content of the "files" or "templates" directory of a module (or a sub directory thereof), so that I don't need to change the class' code every time new files are added. Anyway, I've read the documentation for the "file" resource again, and it looks like I can indeed achieve that with "recurse" (at least partly). Up to now, I've only used recurse together with "ensure => absent". It didn't come to my mind that it would also work this way. What's missing is the "templates" part, though. I also like the idea of using glob patterns here, which is currently not possible. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408658.1627373801000.97091.1627971180033%40Atlassian.JIRA.
Jira (PUP-11189) Add functions to iterate over files/templates in the current module
Title: Message Title Dirk Heinrichs commented on PUP-11189 Re: Add functions to iterate over files/templates in the current module I'm fine with globs, if extended glob syntax can be used, like "foo/sub/*/.ini". Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408658.1627373801000.93757.1627550280024%40Atlassian.JIRA.
Jira (PUP-11189) Add functions to iterate over files/templates in the current module
Title: Message Title Dirk Heinrichs commented on PUP-11189 Re: Add functions to iterate over files/templates in the current module Would also be great if the new functions had an optional "recurse" parameter (default: false). Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408658.1627373801000.90928.1627374240026%40Atlassian.JIRA.
Jira (PUP-11189) Add functions to iterate over files/templates in the current module
Title: Message Title
Dirk Heinrichs created an issue
Puppet / PUP-11189
Add functions to iterate over files/templates in the current module
Issue Type:
New Feature
Assignee:
Henrik Lindberg
Components:
Functions, Language
Created:
2021/07/27 1:16 AM
Priority:
Normal
Reporter:
Dirk Heinrichs
Puppet Version: 6.x, 7.x Puppet Server Version: 6.x, 7.x OS Name/Version: all Sometimes, one needs to put several files in place on an agent node that come from the same module. As it is now, one needs to explicitly name each file in an array to iterate over. This has the drawback that one needs to adapt the code whenever a new file is added to /files (or /templates) Desired Behavior: Be able to write something like that:
files('puppet:///modules/foo/subdir').each |$file| {
file {
...
}
}
Jira (PUP-11171) "Server Error: no parameter named 'max_files'", when adding max_files to file resource
Title: Message Title Dirk Heinrichs commented on PUP-11171 Re: "Server Error: no parameter named 'max_files'", when adding max_files to file resource Sorry for replying late. Issue is resolved now. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.407573.1626851976000.90915.1627372740024%40Atlassian.JIRA.
Jira (PUP-11171) "Server Error: no parameter named 'max_files'", when adding max_files to file resource
Title: Message Title Dirk Heinrichs commented on PUP-11171 Re: "Server Error: no parameter named 'max_files'", when adding max_files to file resource Josh Cooper, yes, by the time this happened, the agent version on the server was still at 6.22.1, while all other agents had already been upgraded to 6.23.0. Meanwhile, everything was upgraded to 6.24.0, so I'll test again... Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.407573.1626851976000.88448.1627019520040%40Atlassian.JIRA.
Jira (PUP-11171) "Server Error: no parameter named 'max_files'", when adding max_files to file resource
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-11171 "Server Error: no parameter named 'max_files'", when adding max_files to file resource Issue Type: Bug Affects Versions: PUP 6.23.0 Assignee: Unassigned Components: Types and Providers Created: 2021/07/21 12:19 AM Environment: Linux Priority: Major Reporter: Dirk Heinrichs Puppet Version: 6.23.0 Puppet Server Version: 6.15.3 OS Name/Version: Debian 10 (Master), Ubuntu 20.04.2 LTS (Agent) After getting the following warning: The directory 'XXX' contains 1530 entries, which exceeds the default soft limit 1000 and may cause excessive resource consumption and degraded performance. To remove this warning set a value for `max_files` parameter or consider using an alternate method to manage large directory trees for a file resource that removes a directory tree, I added a "max_files => 2000" attribute to that resource. But then I got this:
Jira (PUP-10616) Windows: package doesn't pass uninstall_options to uninstaller
Title: Message Title
Dirk Heinrichs updated an issue
Puppet / PUP-10616
Windows: package doesn't pass uninstall_options to uninstaller
Change By:
Dirk Heinrichs
*Puppet Version: 6.17.0* *Puppet Server Version: 6.12.1* *OS Name/Version: Windows*In order to uninstall a package from Windows agent agents , I created a package resource, which also included specific "uninstall_options" for the package. While the correct uninstaller ("...\uninstall.exe", as recorded in the registry) was executed, the package wasn't uninstalled. I checked with Process Explorer and found that the uninstaller was called w/o any option. So I ended up using an exec resource...{code:java}package {'Sentinel Agent': ensure => absent, uninstall_options => ['/uninstall', '/norestart', '/q', "/k=\"${unlock_key}\""],}{code} *Desired Behavior:*Puppet should have uninstalled the package by passing the correct options to the uninstaller.*Actual Behavior:*Options were not passed, which lead to package not being uninstalled. (Maybe related: There was also no error in the report, but that might have been caused by the uninstaller itself, which might not have reported one).
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10616) Windows: package doesn't pass uninstall_options to uninstaller
Title: Message Title
Dirk Heinrichs updated an issue
Puppet / PUP-10616
Windows: package doesn't pass uninstall_options to uninstaller
Change By:
Dirk Heinrichs
*Puppet Version: 6.17.0* *Puppet Server Version: 6.12.1* *OS Name/Version: Windows*In order to uninstall a package from Windows agent, I created a package resource, which also included specific "uninstall_options" for the package. While the correct uninstaller ("...\uninstall.exe", as recorded in the registry) was executed, the package wasn't uninstalled. I checked with Process Explorer and found that the uninstaller was called w/o any option. So I ended up using an exec resource... {code:java} package {'Sentinel Agent': ensure=> absent, uninstall_options => ['/uninstall', '/norestart', '/q', "/k=\"${unlock_key}\""], }{code} *Desired Behavior:*Puppet should have uninstalled the package by passing the correct options to the uninstaller.*Actual Behavior:*Options were not passed, which lead to package not being uninstalled. (Maybe related: There was also no error in the report, but that might have been caused by the uninstaller itself, which might not have reported one).
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10616) Windows: package doesn't pass uninstall_options to uninstaller
Title: Message Title
Dirk Heinrichs updated an issue
Puppet / PUP-10616
Windows: package doesn't pass uninstall_options to uninstaller
Change By:
Dirk Heinrichs
*Puppet Version: 6.17.0* *Puppet Server Version: 6.12.1* *OS Name/Version: Windows*In order to uninstall a package from Windows agent, I created a package resource, which also included specific "uninstall_options" for the package. While the correct uninstaller ("...\uninstall.exe", as recorded in the registry) was executed, the package wasn't uninstalled. I checked with Process Explorer and found that the uninstaller was called w/o any option. So I ended up using an exec resource... {code:java}package {'Sentinel Agent': ensure => absent, uninstall_options => ['/uninstall', '/norestart', '/q', "/k=\"${unlock_key}\""],}{code} *Desired Behavior:*Puppet should have uninstalled the package by passing the correct options to the uninstaller.*Actual Behavior:*Options were not passed, which lead to package not being uninstalled. (Maybe related: There was also no error in the report, but that might have been caused by the uninstaller itself, which might not have reported one).
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10616) Windows: package doesn't pass uninstall_options to uninstaller
Title: Message Title
Dirk Heinrichs created an issue
Puppet / PUP-10616
Windows: package doesn't pass uninstall_options to uninstaller
Issue Type:
Bug
Affects Versions:
PUP 6.17.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2020/08/11 3:50 AM
Priority:
Major
Reporter:
Dirk Heinrichs
Puppet Version: 6.17.0 Puppet Server Version: 6.12.1 OS Name/Version: Windows In order to uninstall a package from Windows agent, I created a package resource, which also included specific "uninstall_options" for the package. While the correct uninstaller ("...\uninstall.exe", as recorded in the registry) was executed, the package wasn't uninstalled. I checked with Process Explorer and found that the uninstaller was called w/o any option. So I ended up using an exec resource...
package {'Sentinel Agent':
ensure=> absent,
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Dirk Heinrichs commented on PUP-6382 Re: Add "Automatic (delayed start)" as option for Service Resource on Windows BTW: It's not yet documented. Does this count as "Resolved", then? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.135151.1464896598000.7056.1583762760027%40Atlassian.JIRA.
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Dirk Heinrichs commented on PUP-6382 Re: Add "Automatic (delayed start)" as option for Service Resource on Windows Mihai Buzgau, thats good news. Thanks a lot. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.135151.1464896598000.110812.1569303420662%40Atlassian.JIRA.
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Dirk Heinrichs commented on PUP-6382 Re: Add "Automatic (delayed start)" as option for Service Resource on Windows Will it be available in P6 only or also backported to P5? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.135151.1464896598000.86496.1567683180365%40Atlassian.JIRA.
Jira (PUP-4080) support S3 URL as the file type 'source'
Title: Message Title Dirk Heinrichs commented on PUP-4080 Re: support S3 URL as the file type 'source' >4 years have passed and Puppet still can't do it. What a pity... Anyway, meanwhile, there's the AWS Ruby SDK version 3, which essentially splits the monolithic gem into lots of smaller ones. Just install the S3 one and you'll get everything needed to support s3:// URIs. That would make writing classes which pull files from either source much easier, as one could simply define the base URI in hiera instead of coding corner cases using "aws s3 cp ..." in exec's into classes which need to get files from S3 sometimes. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.70204.142546711.41422.1564750081885%40Atlassian.JIRA.
Jira (PUP-4080) support S3 URL as the file type 'source'
Title: Message Title Dirk Heinrichs commented on PUP-4080 Re: support S3 URL as the file type 'source' Oh, forgot to mention: Salt can... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.70204.142546711.41437.1564750082119%40Atlassian.JIRA.
Jira (PUP-9822) Windows package provider doesn't have reinstallable feature
Title: Message Title
Dirk Heinrichs created an issue
Puppet / PUP-9822
Windows package provider doesn't have reinstallable feature
Issue Type:
Bug
Affects Versions:
PUP 6.6.0, PUP 5.5.14, PUP 4.10.12
Assignee:
Unassigned
Components:
Windows
Created:
2019/07/12 1:12 AM
Environment:
Windows
Priority:
Normal
Reporter:
Dirk Heinrichs
Puppet Version: 5.5.14 Puppet Server Version: 2.8.x OS Name/Version: Windows While writing a class to install VisualStudio 2019 I found that the Windows package provider doesn't support the reinstallable feature. The VisualStudio installer can install user defined subsets of VS components (called workloads), which can be specified on the command line. Thus, the package should be reinstalled when the list of workloads changes, like for example:
# Create a trigger file containing the list of workloads
file {'C:/ProgramData/Puppet/VisualStudio/2019/Workloads':
Jira (FACT-1934) Add OpenSSH host keys to core facts for Windows
Title: Message Title Dirk Heinrichs commented on FACT-1934 Re: Add OpenSSH host keys to core facts for Windows Could the acceptance criteria be broadened a bit, please? It can also be installed on earlier Windows (Server) versions, by means of this Github project. In fact, I'm running it on systems as old as Server 2008R2. 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.316044.1562825377000.11981.1562826060082%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9139) Package provider apt fails when installing from local file
Title: Message Title Dirk Heinrichs commented on PUP-9139 Re: Package provider apt fails when installing from local file Any news on this? 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-9514) tidy: Allow removal of old directories, even if not empty
Title: Message Title
Dirk Heinrichs created an issue
Puppet / PUP-9514
tidy: Allow removal of old directories, even if not empty
Issue Type:
Improvement
Assignee:
Unassigned
Components:
Platform
Created:
2019/03/06 1:02 AM
Priority:
Major
Reporter:
Dirk Heinrichs
The tidy resource currently doesn't allow removal of non-empty directories. But sometimes this is exactly what is needed. For example we have a Windows application which doesn't cleanup after itself and leaves behind lots of directories with name "out-*" which I would like to remove after some days. Unfortunately, those directories are written to the root of drive D:, alongside other directories, which ought to be kept (but shouldn't need to be traversed). So the approach I'd like to use is:
tidy { 'cleanup_d':
path => 'D:/',
matches => ['out-*'],
age => '7d',
Jira (PUP-5759) Windows: Puppet agent doesn't create directory when parent is a mounted volume
Title: Message Title Dirk Heinrichs commented on PUP-5759 Re: Windows: Puppet agent doesn't create directory when parent is a mounted volume Wanted to upgrade to P5 anyway in the near future (and, as written above, I can't even remember the use case anymore). But anyway, thanks a lot for looking into it. 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-9139) Package provider apt fails when installing from local file
Title: Message Title Dirk Heinrichs updated an issue Puppet / PUP-9139 Package provider apt fails when installing from local file Change By: Dirk Heinrichs *Puppet Version: 4.10* *Puppet Server Version: 2.8.1* *OS Name/Version: Ubuntu 16.04*apt-get is able to install packages from locally stored .deb files (apt-get install /path/to/package), resolving dependencies as usual. However, the apt package provider doesn't seem to support this, which enforces the use of the dpkg provider. Unfortunately, this provider doesn't do depenedency dependency resolution (since dpkg itself can't do that).*Desired Behavior:*Installing a from a local package file with the apt provider should just work.*Actual Behavior:*apt provider fails when trying to install from a local file. 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
Jira (PUP-9139) Package provider apt fails when installing from local file
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-9139 Package provider apt fails when installing from local file Issue Type: New Feature Assignee: Unassigned Created: 2018/09/14 3:54 AM Priority: Normal Reporter: Dirk Heinrichs Puppet Version: 4.10 Puppet Server Version: 2.8.1 OS Name/Version: Ubuntu 16.04 apt-get is able to install packages from locally stored .deb files (apt-get install /path/to/package), resolving dependencies as usual. However, the apt package provider doesn't seem to support this, which enforces the use of the dpkg provider. Unfortunately, this provider doesn't do depenedency resolution (since dpkg itself can't do that). Desired Behavior: Installing a from a local package file with the apt provider should just work. Actual Behavior: apt provider fails when trying to install from a local file. Add Comment
Jira (PUP-5759) Windows: Puppet agent doesn't create directory when parent is a mounted volume
Title: Message Title Dirk Heinrichs commented on PUP-5759 Re: Windows: Puppet agent doesn't create directory when parent is a mounted volume That's been so long ago, I can't even remember why I was trying to do this. Windows version was Server 2008 R2 or 2012 R2, Puppet agent version could have been 1.5.x at that time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5263) Puppet agent can't update itself on Windows Server 2012R2
Title: Message Title Dirk Heinrichs commented on PUP-5263 Re: Puppet agent can't update itself on Windows Server 2012R2 More than one month since this has been reported. Meanwhile, 1.2.6 is out and I can't roll it out to 2012 servers via Puppet itself. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Dirk Heinrichs commented on PUP-5264 Re: Agent service status wrong on CentOS 6 That was the right hint. Looks like I have the PID in /var/run/puppet/agent.pid, not in /var/run/puppetlabs/agent.pid. Short investigation showed that puppet.conf had the wrong paths for some dirs. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Dirk Heinrichs commented on PUP-5264 Re: Agent service status wrong on CentOS 6 Works fine on Ubuntu 14.04, though. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5263) Puppet agent can't update itself on Windows Server 2012R2
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-5263 Puppet agent can't update itself on Windows Server 2012R2 Issue Type: Bug Affects Versions: puppet-agent 1.2.2 Assignee: Unassigned Created: 2015/09/17 1:19 AM Environment: Windows Server 2012R2 Priority: Major Reporter: Dirk Heinrichs I use a self-written class to manage (and upgrade) Puppet agent on all agent nodes. This works fine on Linux and Windows Server 2008R2, but on Server 2012R2 the upgrade to 1.2.4 fails reproducably with the following message in the report: change from 1.2.2 to 1.2.4 failed: Could not update: Failed to install: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-5264 Agent service status wrong on CentOS 6 Issue Type: Bug Affects Versions: puppet-agent 1.2.4 Assignee: Unassigned Created: 2015/09/17 1:23 AM Environment: CentOS Linux 6 Priority: Normal Reporter: Dirk Heinrichs A service resource for managing the Puppet agent service tries to change it from stopped to running, although it already runs: # ps -ef|grep [Pp]uppet root 20951 1 0 10:06 ?00:00:00 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Dirk Heinrichs commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Any chance to get this fixed in 3.7.x instead of 4.0.0? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1497) Missing version number in Windows packages displayname prevents update
Title: Message Title Dirk Heinrichs commented on an issue Re: Missing version number in Windows packages displayname prevents update Ah, OK. That's great. Thanks a lot. Add Comment Puppet / PUP-1497 Missing version number in Windows packages displayname prevents update Wanted to update the Puppet agent on Windows via Puppet. Unfortunately, the displayname, which is what the package resource looks after, of the Puppet package for Windows is just Puppet. So no matter what version I want to update to, the package resource is always satisfied if ANY version of puppet is already installed. Putting the version number into t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1497) Missing version number in Windows packages displayname prevents update
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-1497 Missing version number in Windows packages displayname prevents update Issue Type: Improvement Assignee: Eric Sorenson Created: 23/Jan/14 1:44 AM Environment: Windows Priority: Normal Reporter: Dirk Heinrichs Wanted to update the Puppet agent on Windows via Puppet. Unfortunately, the displayname, which is what the package resource looks after, of the Puppet package for Windows is just Puppet. So no matter what version I want to update to, package resource is always satisfied if ANY version of puppet is already installed. Pupping the version number into the displayname field, like many other packages do as well, would solve that problem. Add Comment
Jira (PUP-1497) Missing version number in Windows packages displayname prevents update
Title: Message Title Dirk Heinrichs updated an issue Puppet / PUP-1497 Missing version number in Windows packages displayname prevents update Change By: Dirk Heinrichs WantedtoupdatethePuppetagentonWindowsviaPuppet.Unfortunately,thedisplayname,whichiswhatthepackageresourcelooksafter,ofthePuppetpackageforWindowsisjustPuppet.SonomatterwhatversionIwanttoupdateto, the packageresourceisalwayssatisfiedifANYversionofpuppetisalreadyinstalled. Pupping Putting theversionnumberintothedisplaynamefield,likemanyotherpackagesdoaswell,wouldsolvethatproblem. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
