Jira (PDB-4635) puppetdb_avg_mem larger than baseline values
Title: Message Title John Duarte commented on PDB-4635 Re: puppetdb_avg_mem larger than baseline values For the performance comparison run of week 2020-04-06, this tolerance failed when testing recent PE master build (2019.7.0-rc0-11-g427cad1) to the LTS baseline (but not STS). 2019.7.0-rc0-11-g427cad1 2018.1.13 comparison: Result 'process_puppetdb_avg_mem' is outside tolerances: baseline: 730773; result: 937053; variance: 28.23% 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.343321.1579814655000.32667.1586293020041%40Atlassian.JIRA.
Jira (PDB-4681) Investigate which pg user owns on demand partitions
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4681 Investigate which pg user owns on demand partitions Change By: Zachary Kent Release Notes: Not Needed 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.353717.1585759029000.32479.1586285700162%40Atlassian.JIRA.
Jira (PUP-10408) Puppet .dmg packages fail on macOS 10.15
Title: Message Title Josh Cooper commented on PUP-10408 Re: Puppet .dmg packages fail on macOS 10.15 Merged to master in https://github.com/puppetlabs/puppet/commit/28ea0af52cd53b1a540a1c61fee202ec4f20e1fd 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.354076.1585870709000.32456.1586284860027%40Atlassian.JIRA.
Jira (PUP-10410) package fails on openjdk with non-boolean status string
Title: Message Title Josh Cooper commented on PUP-10410 Re: package fails on openjdk with non-boolean status string For next time, it helps to run with the --trace command line argument so it will print the ruby stacktrace leading up to the problem. 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.354183.1586042388000.32364.1586281980029%40Atlassian.JIRA.
Jira (PUP-10378) 'puppet resource service' does not return all active services on Ubuntu
Title: Message Title
Luchian Nemes commented on PUP-10378
Re: 'puppet resource service' does not return all active services on Ubuntu
When puppet is listing information about a single service (in our case via puppet resource service pe-postgresql), it will get it's data from the systemd provider, through the statuscmd (:ensure field) and enabled? (:enable field) methods. Then it will output:
service { 'pe-postgresql':
ensure => 'running',
enable => 'true',
provider => 'systemd',
}
When puppet is listing all the available services (via puppet resource service), systemctl is queried, through the instances method, to gather all the services. These are filtered and only the ones with any of the following states are shown to the user: `disabled`, `enabled`, `masked` or `indirect`. Since in our case pe-postgresql is marked as bad, it is indeed omitted. systemctl's man section for the is-enabled parameter possible statuses states that:
Name
Description
Error code
"bad"
The unit file is invalid or another error occurred. Note that is-enabled will not actually return this state, but print an error message instead. However the unit file listing printed by list-unit-files might show it.
> 0
Jira (PUP-10415) puppet-apply: Could not set 'file' on ensure: Is a directory @ io_fread
Title: Message Title
Daniel Kimsey updated an issue
Puppet / PUP-10415
puppet-apply: Could not set 'file' on ensure: Is a directory @ io_fread
Change By:
Daniel Kimsey
*Puppet Version:* 6.14.0*Puppet Server Version:* n/a*OS Name/Version:* CentOS 5/6/7 Describe your issue in as much detail as possible…Describe steps to reproduce…`puppet Given a simple module install with a directory to deploy via the file resource . Puppet is no longer able to copy out files if the target directory does not exist . .` `puppet-apply --test examples/site.pp` *Desired Behavior:*Deploying a module's source directory using the `file` resource no longer works with `puppet apply`.*Actual Behavior:*6.13.0 results:{code}Notice: /Stage[main]/Zabbixagent/File[/usr/local/libexec/zabbix/discover_ssl_interface.sh]/ensure: defined content as '{md5}d80441a366c9f5785292dafe8d45375e'Notice: /Stage[main]/Zabbixagent/File[/usr/local/libexec/zabbix/ssl_cert_info.sh]/ensure: defined content as '{md5}d41e50e79ed0fe1c96dac40931e641a2'{code}6.14.0 results:{code}Error: Could not set 'file' on ensure: Is a directory @ io_fread - /etc/puppetlabs/code/environments/production/modules/zabbixagent/files/localscriptsError: Could not set 'file' on ensure: Is a directory @ io_fread - /etc/puppetlabs/code/environments/production/modules/zabbixagent/files/localscriptsWrapped exception:Is a directory @ io_fread - /etc/puppetlabs/code/environments/production/modules/zabbixagent/files/localscriptsError: /Stage[main]/Zabbixagent/File[/usr/local/libexec/zabbix/discover_ssl_interface.sh]/ensure: change from 'absent' to 'file' failed: Could not set 'file' on ensure: Is a directory @ io_fread - /etc/puppetlabs/code/environments/production/modules/zabbixagent/files/localscriptsError: Could not set 'file' on ensure: Is a directory @ io_fread - /etc/puppetlabs/code/environments/production/modules/zabbixagent/files/localscriptsError: Could not set 'file' on ensure: Is a directory @ io_fread - /etc/puppetlabs/code/environments/production/modules/zabbixagent/files/localscriptsWrapped exception:Is a directory @ io_fread - /etc/puppetlabs/code/environments/production/modules/zabbixagent/files/localscriptsError: /Stage[main]/Zabbixagent/File[/usr/local/libexec/zabbix/ssl_cert_info.sh]/ensure: change from 'absent' to 'file' failed: Could not set 'file' on ensure: Is a directory @ io_fread - /etc/puppetlabs/code/environments/production/modules/zabbixagent/files/localscripts{code}Interestingly, upgrading to 6.14.0 _after_ successful run with 6.13.0, runs successfully until the target path directory is removed. Issue is reproducible by removing the target directory.Examples:Run puppet agent with --test --trace --debugNote, this appears to require a module to use the puppet:// urls. It doesn't appear to be an issue with file:// urls. `puppet module install ...``puppet-apply --test examples/site.pp` {code:java}file { '/usr/local/libexec/zabbix/': recurse => true, mode => '0755', owner => 'root', group => 'root', purge =>
Jira (PUP-10415) puppet-apply: Could not set 'file' on ensure: Is a directory @ io_fread
Title: Message Title
Daniel Kimsey created an issue
Puppet / PUP-10415
puppet-apply: Could not set 'file' on ensure: Is a directory @ io_fread
Issue Type:
Bug
Affects Versions:
PUP 6.14.0
Assignee:
Unassigned
Created:
2020/04/07 9:18 AM
Priority:
Normal
Reporter:
Daniel Kimsey
Puppet Version: 6.14.0 Puppet Server Version: n/a OS Name/Version: CentOS 5/6/7 Describe your issue in as much detail as possible… Describe steps to reproduce… `puppet module install ...` `puppet-apply --test examples/site.pp` Desired Behavior: Deploying a module's source directory using the `file` resource no longer works with `puppet apply`. Actual Behavior: 6.13.0 results:
Notice: /Stage[main]/Zabbixagent/File[/usr/local/libexec/zabbix/discover_ssl_interface.sh]/ensure: defined content as '{md5}d80441a366c9f5785292dafe8d45375e'
Notice: /Stage[main]/Zabbixagent/File[/usr/local/libexec/zabbix/ssl_cert_info.sh]/ensure: defined content as '{md5}d41e50e79ed0fe1c96dac40931e641a2'
6.14.0 results:
Jira (PUP-10248) windows pidlock can raise access denied
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10248 windows pidlock can raise access denied Change By: Gabriel Nagy Release Notes: Bug Fix Release Notes Summary: Use `SeDebugPrivilege` on Windows when opening a lockfile PID in order to determine whether the process is a Puppet process. 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.343144.1579760192000.32148.1586273280851%40Atlassian.JIRA.
Jira (PUP-10414) Windows service calls deprecated `puppet agent --configprint`
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10414 Windows service calls deprecated `puppet agent --configprint` Change By: Mihai Buzgau Sprint: PR - Triage 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.354468.1586208728000.32033.1586265240168%40Atlassian.JIRA.
Jira (PUP-10410) package fails on openjdk with non-boolean status string
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10410 package fails on openjdk with non-boolean status string Change By: Mihai Buzgau Sprint: PR - Triage 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.354183.1586042388000.32027.1586264940040%40Atlassian.JIRA.
Jira (PUP-10295) Add SemVerRange support to gem package provider
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10295 Add SemVerRange support to gem package provider Change By: Luchian Nemes Release Notes: Enhancement Release Notes Summary: Add support for range intersection (min,max such as: >=A <=B) specified in the :ensure manifest field. This will install a version that satisfies the provided range. 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.346484.1582028683000.31971.1586249580034%40Atlassian.JIRA.
Jira (FACT-2538) Nil facts are shown when facter is called with --show-legacy
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2538 Nil facts are shown when facter is called with --show-legacy Change By: Sebastian Miclea Assignee: Sebastian Miclea 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.354275.1586173838000.31931.1586244180036%40Atlassian.JIRA.
Jira (FACT-2535) Implement to_s on ResolvedFact
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2535 Implement to_s on ResolvedFact Change By: Sebastian Miclea Assignee: Sebastian Miclea 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.353994.1585839979000.31905.158624135%40Atlassian.JIRA.
Jira (FACT-2513) command line help shows flags incorrectly
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2513 command line help shows flags incorrectly Change By: Sebastian Miclea Assignee: Sebastian Miclea 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.353384.1585634122000.31904.1586240880112%40Atlassian.JIRA.
