Jira (PUP-9692) hiera explain should redact values converted to Sensitive in --debug mode
Title: Message Title Sanjay Tripathi commented on PUP-9692 Re: hiera explain should redact values converted to Sensitive in --debug mode Hello, Is there any possibility of this issue getting fixed in the near future? We would like to up-take the fix of https://tickets.puppetlabs.com/browse/PUP-9693 (thanks for fixing it!) but it would be really useful to have the data redacted in the log, when the debug flag is passed, for data which has convert_to: "Sensitive". We "heavily rely" on the debug flag for all the environment information Puppet logs in debug mode. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307422.1556927311000.54821.1561005840232%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9788) AIX nim test sometimes takes over an hour
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9788
AIX nim test sometimes takes over an hour
Change By:
Josh Cooper
Something is wrong with {{aix71-10.delivery.puppetlabs.net}} and maybe others.In https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/Acceptance%20Suites/view/6.4.x/view/Suite/job/platform_puppet-agent_puppet-agent-integration-suite_daily-6.4.x/RMM_COMPONENT_TO_TEST_NAME=puppet,SLAVE_LABEL=beaker,TEST_TARGET=aix71-POWERfa/76/ The nim package provider test sometimes takes over took an hour and half :{noformat}tests/aix/nim_package_provider.rb passed in 5884.87 seconds{noformat} These other tests were slow:{noformat}tests/parser_functions/puppet_lookup_cmd.rb passed in 107.64 secondstests/resource/file/symbolic_modes.rb passed in 108.45 secondstests/resource/service/AIX_service_provider.rb passed in 150.64 secondstests/resource/service/puppet_service_management.rb passed in 259.18 seconds{noformat}Altogether the tests took over 3 hours.The same tests running on {{aix71-8.delivery.puppetlabs.net}} "only" took 1hr 39mins:https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/Acceptance%20Suites/view/6.4.x/view/Suite/job/platform_puppet-agent_puppet-agent-integration-suite_daily-6.4.x/RMM_COMPONENT_TO_TEST_NAME=puppet,SLAVE_LABEL=beaker,TEST_TARGET=aix71-POWERfa/74/
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9788) AIX nim test sometimes takes over an hour
Title: Message Title Josh Cooper created an issue Puppet / PUP-9788 AIX nim test sometimes takes over an hour Issue Type: Improvement Assignee: Unassigned Created: 2019/06/19 7:02 PM Priority: Normal Reporter: Josh Cooper The nim package provider test sometimes takes over an hour: tests/aix/nim_package_provider.rb passed in 5884.87 seconds Add Comment
Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH
Title: Message Title Vadym Chepkov commented on PUP-6488 Re: Gem provider should allow alternative gem command; should not rely on $PATH FYI, puppetlabs-puppetserver_gem module is not compatible with this change 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.140954.1468271833000.54788.1560993840314%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9787) Unintentional secret reveal while installing modules
Title: Message Title Chris Suszynski updated an issue Puppet / PUP-9787 Unintentional secret reveal while installing modules Change By: Chris Suszynski Affects Version/s: PUP 4.10.0 Affects Version/s: PUP 4.10.12 Affects Version/s: PUP 5.5.14 Affects Version/s: PUP 6.4.2 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
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Team: Platform OS Puppet Romania Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.54344.1560984421306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9787) Unintentional secret reveal while installing modules
Title: Message Title Chris Suszynski updated an issue Puppet / PUP-9787 Unintentional secret reveal while installing modules Change By: Chris Suszynski Acceptance Criteria: * Puppet should not reveal sensitive information while isntalling modules. * Usit Unit tests are added that assure that marking masking is done 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.313276.1560984349000.54345.1560984421359%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9787) Unintentional secret reveal while installing modules
Title: Message Title Chris Suszynski created an issue Puppet / PUP-9787 Unintentional secret reveal while installing modules Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Unassigned Components: Modules Created: 2019/06/19 3:45 PM Priority: Minor Reporter: Chris Suszynski Puppet Version: any Puppet Server Version: any OS Name/Version: any Actual Behavior: Puppet Forge is public, and downloading modules don't require authentication. However there are some repositories that can hold modules and require authentication to connect. Those repositories are: Artifactory (live) Nexus (emerging) (emerging) When installing modules from those repositories user is forced to set his credentials in plain text in URI supported form, for ex.: https://admin:s3c...@pkg.acmecorp.com/repository/puppet Installing modules with similar module repository being set, reveals those credentials. In fact it's done each time a module is installed, with a message:
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Tom Beech assigned an issue to Tom Beech Puppet Task Runner / BOLT-1318 Modulepath unable to handle folder names in uppercase characters on Windows Change By: Tom Beech Assignee: Tom Beech Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.54189.1560983700268%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9742) Update Confluence and JIRA based on release (Puppet Platform 6.5.0)
Title: Message Title Kenn Hussey commented on PUP-9742 Re: Update Confluence and JIRA based on release (Puppet Platform 6.5.0) James Shen as discussed, I've already taken care of #8. 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.311735.155994663.54161.1560982800331%40Atlassian.JIRA. 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 Josh Cooper updated an issue Puppet / PUP-9514 tidy: Allow removal of old directories, even if not empty Change By: Josh Cooper Labels: help_wanted 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.298539.1551862945000.54038.1560979560169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1042) Change --write-catalog-summary option into a config setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1042 Change --write-catalog-summary option into a config setting Change By: Josh Cooper Labels: beginner help_wanted redmine 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.21360.1387191693000.54023.1560979140936%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5687) resources type takes long time to evaluate
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5687 resources type takes long time to evaluate Change By: Josh Cooper Labels: beginner help_wanted 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.111915.1452544952000.54012.1560979080704%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9365) Newlines in resource titles result in invalid .dot files
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9365 Newlines in resource titles result in invalid .dot files Change By: Josh Cooper Labels: beginner help_wanted 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.289068.154505099.54005.1560979021162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5687) resources type takes long time to evaluate
Title: Message Title
Josh Cooper commented on PUP-5687
Re: resources type takes long time to evaluate
The user type has a similar problem when parsing an ssh authorized keys file:
names.map { |keyname|
Puppet::Type.type(:ssh_authorized_key).new(
:name => keyname,
:target => keyfile)
}.reject { |res|
catalog.resource_refs.include? res.ref
}
In general Catalog#resource_refs should be avoided since it creates temporary strings for each resource in the catalog, compares res.ref against that, and throws away all of the data. It would be better to just check if the catalog contains the resource, something like catalog.contains_resource?(res), as that could be implemented as @resource_table.has_value?(ref).
Add Comment
Jira (PUP-5687) resources type takes long time to evaluate
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5687 resources type takes long time to evaluate Change By: Josh Cooper Labels: help_wanted 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.111915.1452544952000.53970.1560978181010%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6190) Puppet module build errors if a file or directory contains non US English characters
Title: Message Title Josh Cooper commented on PUP-6190 Re: Puppet module build errors if a file or directory contains non US English characters puppet module build has been removed in favor of pdk. Please reopen against pdk if this is still a problem. 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.127514.146118477.53956.1560977940732%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1401) Puppet package providers use execpipe, which does not set LC_ALL or LANG
Title: Message Title Josh Cooper commented on PUP-1401 Re: Puppet package providers use execpipe, which does not set LC_ALL or LANG Interestingly this ticket contradicts PUP-1191. 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.23233.1389211294000.53936.1560977580505%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6208) Invalid byte sequence in US-ASCII on gem install
Title: Message Title Josh Cooper commented on PUP-6208 Re: Invalid byte sequence in US-ASCII on gem install This is another symptom of PUP-1191. It's not clear to me if the gem provider should pass override_locale: false or if puppet shouldn't override the locale in the first place... 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.127658.1461224707000.53940.1560977580701%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1197) Allow $nodes as second positional arg for run_plan()
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1197 Allow $nodes as second positional arg for run_plan() Change By: Lucy Wyman Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.30.1553194628000.53908.1560976921242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1191) Puppet should not reset locale when executing child processes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1191 Puppet should not reset locale when executing child processes Change By: Josh Cooper Summary: Puppet should not reset locale when executing child processes 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.22330.1387476204000.53871.1560976200638%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1042) Change --write-catalog-summary option into a config setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1042 Change --write-catalog-summary option into a config setting Change By: Josh Cooper Labels: help_wanted redmine 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.21360.1387191693000.53853.1560976021115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1411) Bolt should honor StrictHostKeyChecking setting in SSH config
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-1411 Bolt should honor StrictHostKeyChecking setting in SSH config Issue Type: New Feature Assignee: Unassigned Created: 2019/06/19 1:23 PM Priority: Normal Reporter: Michael Smith When connecting to a host that I don't have an host key signature for, I'd expect it to behave similar to SSH. Specifically, I've setup my ~/.ssh/config with Host *.mysite.example.com StrictHostKeyChecking no UserKnownHostsFile /dev/null as these are ephemeral hosts that I may only connect to a few times. I can connect to them with `ssh host.mysite.example.com`. I would expect the same to work with Bolt without specific arguments. Relies on a fix for https://github.com/net-ssh/net-ssh/issues/678.
Jira (BOLT-1403) Prepare bolt-server for bolt_shim removal
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1403
Prepare bolt-server for bolt_shim removal
Change By:
Casey Williams
There are places in bolt-server where it is assumed that "task run" is the only type of action that bolt server will run. Before we do BOLT-1400, BOLT-1401, and BOLT-1402, we want to look over the existing bolt-server code and find places where it makes sense to refactor things in an action-agnostic way, so that functionality can be reused for other bolt actions, like "command run", "upload file", and "run script". *In scope:* * *JSON schemas:* The bolt server app reuses a partial json schema for task details in both the ssh and winrm request schemas (see them [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]). We will also want to reuse the target schemas for winrm and ssh while creating new endpoints for other actions. Refactor the task endpoint schemas so that they load details about target parameters from two new schemas, one each for winrm and ssh targets. * * SSH and WinRM route reuse:* There will be endpoints for each bolt action nested under the 'ssh' and 'winrm' route segments (/ssh/run_task, /ssh/run_command, /ssh/upload_file, etc.). There are a few cases (which are detailed in the transport app's spec tests) where a certain combination of parameters to an SSH or WinRM execution should be rejected and the request halted early – right now, this is done in the run_task handler, but we should break out the SSH and WinRM validations into their own functions and apply them using Sinatra's dynamic route handling, if possible. * * Spec tests:* Look at the following tests and refactor where warranted so that they can more easily test other bolt actions besides "task run" ("command run", "file upload", "script run"). ** [https://github.com/puppetlabs/bolt/blob/master/spec/bolt_server/transport_app_spec.rb] ** [https://github.com/puppetlabs/bolt/blob/master/spec/bolt_server/app_integration_spec.rb] ** Review these files and the three BOLT tickets and then extract any helpers, shared examples, etc. that seem appropriate.*Out of scope:* * This ticket concerns only refactors that apply to all bolt actions – refactors that apply to only one or a few actions should be ticketed separately. The purpose of this ticket is only to unblock BOLT-1400, BOLT-1401, BOLT-1402 as a group.
Jira (PUP-4795) smf.rb provider for service - manifest does not work for S11.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4795 smf.rb provider for service - manifest does not work for S11.x Change By: Josh Cooper Team: Coremunity Puppet Romania Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.86601.1435600569000.53683.1560971220369%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6465) Catalog evaltrace should log resource number and totals
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6465 Catalog evaltrace should log resource number and totals Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.139759.1467383374000.53677.1560971160691%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6465) Catalog evaltrace should log resource number and totals
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6465 Catalog evaltrace should log resource number and totals Change By: Josh Cooper Fix Version/s: PUP 6.6.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.139759.1467383374000.53673.1560971160545%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6465) Catalog evaltrace should log resource number and totals
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-6465 Catalog evaltrace should log resource number and totals Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.139759.1467383374000.53675.1560971160639%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9742) Update Confluence and JIRA based on release (Puppet Platform 6.5.0)
Title: Message Title James Shen commented on PUP-9742 Re: Update Confluence and JIRA based on release (Puppet Platform 6.5.0) Kenn Hussey yep. I am good! 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.311735.155994663.53661.1560970380579%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9742) Update Confluence and JIRA based on release (Puppet Platform 6.5.0)
Title: Message Title Kenn Hussey assigned an issue to James Shen James Shen are you OK with "closing out" the 6.5.0 release if I take on communication around the the next one (6.6.0)? Puppet / PUP-9742 Update Confluence and JIRA based on release (Puppet Platform 6.5.0) Change By: Kenn Hussey Assignee: Nirupama Mantha James Shen 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
Jira (PUP-9786) Compiling catalog for AIX actually executes commands when managing users with group
Title: Message Title Dylan Ratcliffe commented on PUP-9786 Re: Compiling catalog for AIX actually executes commands when managing users with group Ah that makes sense, workaround created: https://github.com/dylanratcliffe/onceover/pull/236 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.313097.156095524.53636.1560969900160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4421) Fixing the hyperlink for facts doc
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4421 Fixing the hyperlink for facts doc Issue Type: Bug Assignee: Unassigned Created: 2019/06/19 11:38 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
Jira (PUP-9181) Notify resource behaves in unexpected fashion
Title: Message Title Josh Cooper commented on PUP-9181 Re: Notify resource behaves in unexpected fashion This is a bug in the resource harness whereby it doesn't allow the desired value (aka Property#should) for a property to be falsey due to: if param.should && !param.safe_insync?(current_value) This is a duplicate of PUP-2368, closing 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.277602.153796905.53592.1560969002482%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9301) Reduce noise from notify resource
Title: Message Title Josh Cooper commented on PUP-9301 Re: Reduce noise from notify resource There is a notice server function which does what you want when running puppet apply. But I think you're wanting a client side function, which is best handled using Deferred. See https://puppet.com/docs/puppet/6.5/write_a_puppet_function_to_store_secrets.html. That said we can't change how notify so I'm going to close 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.283483.1541133295000.53556.1560968521730%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-259) relax ruby requirement to 2.1.0 from 2.1.9
Title: Message Title Jesse Scott commented on PDOC-259 Re: relax ruby requirement to 2.1.0 from 2.1.9 David Schmitt is this still needed? We would like to actually bump the puppet-strings required ruby version at some point. If it's still needed can you point me to the test cases in the puppet_agent module? 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.261734.1529500595000.53543.1560968460659%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1403) Prepare bolt-server for bolt_shim removal
Title: Message Title Geoff Nichols updated an issue Puppet Task Runner / BOLT-1403 Prepare bolt-server for bolt_shim removal Change By: Geoff Nichols Story Points: 1 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.312897.1560810439000.53533.1560968400495%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Geoff Nichols updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Geoff Nichols Sprint: Skeletor Kanban 20190619 , Skeletor Kanban 20190703 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.312869.1560800327000.53516.1560968342032%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1403) Prepare bolt-server for bolt_shim removal
Title: Message Title Geoff Nichols updated an issue Puppet Task Runner / BOLT-1403 Prepare bolt-server for bolt_shim removal Change By: Geoff Nichols Sprint: Skeletor Kanban 20190619 , Skeletor Kanban 20190703 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.312897.1560810439000.53531.1560968342710%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9718) Create a plan_information_service in Puppet and add it to the information_service
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-9718 Create a plan_information_service in Puppet and add it to the information_service Change By: Geoff Nichols Sprint: Skeletor Kanban 20190605, Skeletor Kanban 20190619 , Skeletor Kanban 20190703 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.309780.1558558495000.53507.1560968341665%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9314) puppetdb-termini for puppet standalone try to connect to master
Title: Message Title Josh Cooper commented on PUP-9314 Re: puppetdb-termini for puppet standalone try to connect to master Grégoire Menuel This part of puppet's code has been rewritten so that it no longer attempts to initialize the SSL state machine while in the process of making a network connection. Please try with a more recent version of puppet 6.4 or later 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.285263.1542291964000.53488.1560968040384%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9365) Newlines in resource titles result in invalid .dot files
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9365 Newlines in resource titles result in invalid .dot files Change By: Josh Cooper Labels: help_wanted 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.289068.154505099.53459.1560967800453%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4433) Puppet doesn't process SIGCHLD
Title: Message Title Josh Cooper commented on PUP-4433 Re: Puppet doesn't process SIGCHLD Since puppet fork/execs the child process and immediately waits after, the window of time for the zombie'd process is short. My understanding is that registering a signal handler for SIG_CHLD is only necessary if you want to ensure the child never becomes a zombie. However, it also means the main program can't know what the child process' exit status was. Could you provide more information about why you feel puppet's implementation is incorrect? 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.76305.1429279394000.53452.1560967620273%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title Josh Cooper commented on PUP-9754 Re: Log resident configuration upon daemon launch Logging every setting value could get spammy. We may want to limit this to only log settings whose values are different than the default and/or add a signal handler (maybe USR2?) to dump the configuration in response to the signal. Not sure about Windows. This is another reason to run puppet from cron instead of running our homegrown daemonization code. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312512.1560543853000.53423.1560966840346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9786) Compiling catalog for AIX actually executes commands when managing users with group
Title: Message Title Josh Cooper commented on PUP-9786 Re: Compiling catalog for AIX actually executes commands when managing users with group The error you are seeing is because rspec_puppet does more than compile a catalog. It transforms the server catalog produced by the compiler into a RAL (agent) catalog. That process triggers all of the validation, munge, provider selection that normally occurs on the agent. So it's not unexpected to see provider code being executed in rspec-puppet. This is a fundamental problem with puppet's type and provider system, which rspec-puppet attempt to paper over. You'll probably need to update rspec-puppet or your tests to stub out `Puppet::Util::Execution.execute`. 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.313097.156095524.53391.1560966540333%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Josh Cooper commented on PUP-3062 Re: The default unit for `splaylimit` should not be seconds. The runinterval and splaylimit settings are both type duration. If you set either of them and don't specify units, then they both are interpreted as seconds. The reason this issue occurred is because runinterval defaults to 30m, but splaylimit was overridden as 60 which is interpreted as seconds. I don't think requiring units is a good idea. It would be very disruptive without a lot of benefit, as everything that has ever set a puppet setting would need to be aware of units, such as puppet config set runinterval 30m, packaging (rpm, deb, msi), cloud-init scripts, kickstart, foreman, etc. Closing this ticket. 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.47913.140805296.53357.1560965881251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8959) FastGettext.default_text_domain order dependent test failure
Title: Message Title Josh Cooper commented on PUP-8959 Re: FastGettext.default_text_domain order dependent test failure Can't reproduce on master, so the immediate issue is fixed in https://github.com/puppetlabs/puppet/commit/72c804feb4327d8a4502ba2de477366e78128981 merged to 5.5.x and first released in 5.5.7 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.262704.153000368.53298.1560964621287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8959) FastGettext.default_text_domain order dependent test failure
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8959 FastGettext.default_text_domain order dependent test failure Change By: Josh Cooper Fix Version/s: PUP 5.5.7 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.262704.153000368.53300.1560964621390%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9738) Prepare release announcement (Puppet Platform 6.5.0)
Title: Message Title Jean Bond commented on PUP-9738 Re: Prepare release announcement (Puppet Platform 6.5.0) lgtm! 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.311726.1559946561000.53275.1560964140213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9736) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.5.0)
Title: Message Title James Shen assigned an issue to James Shen Puppet / PUP-9736 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.5.0) Change By: James Shen Assignee: Nirupama Mantha James Shen 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.311724.1559946548000.53256.1560964020724%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9738) Prepare release announcement (Puppet Platform 6.5.0)
Title: Message Title Bill Tang commented on PUP-9738 Re: Prepare release announcement (Puppet Platform 6.5.0) Jean Bond - for your review: Puppet Platform 6.5.0 is now available! This release contain bug fixes and enhancement, notably: Support added for Fedora 30 (amd64) New v4 catalog endpoint You can see the full list of changes in the release notes https://puppet.com/docs/puppet/6.5/release_notes_puppet.html 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.311726.1559946561000.53249.1560963900670%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1197) Allow $nodes as second positional arg for run_plan()
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1197 Allow $nodes as second positional arg for run_plan() Change By: Lucy Wyman Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.30.1553194628000.53029.1560959100550%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9786) Compiling catalog for AIX actually executes commands when managing users with group
Title: Message Title Dylan Ratcliffe created an issue Puppet / PUP-9786 Compiling catalog for AIX actually executes commands when managing users with group Issue Type: Bug Affects Versions: PUP 6.4.2 Assignee: Unassigned Components: Types and Providers Created: 2019/06/19 7:40 AM Priority: Normal Reporter: Dylan Ratcliffe Puppet Version: 6.4.2 Puppet Server Version: N/A OS Name/Version: AIX (any) When compiling a catalog for AIX, the user type causes the provider to actually execute commands using Puppet::Util::Execution.execute(). This is fine because they don't do anything and the catalog compiles fine anyway. However when we run tests on Windows with rspec-puppet, because it's pretending to be UNIX, the null_file is set to /dev/null https://github.com/puppetlabs/puppet/blob/3f7a06c50a8707811387dd60a6f7f26d94b606f4/lib/puppet/util/execution.rb#L191 and therefore ruby actually tries to read it, causing the catalog to fail with the following error: No such file or directory @ rb_sysopen - /dev/null This essentially means that it's impossible to test code destined for AIX on Windows if it includes a user resource that is managing groups (It's group management that causes this) This can be
Jira (PUP-9785) Unable to connect puppetserver ca endpoints
Title: Message Title
foo bar updated an issue
Puppet / PUP-9785
Unable to connect puppetserver ca endpoints
Change By:
foo bar
*Puppet Version: 6.4.2 -1 * *Puppet Server Version: 6.3.0* *OS Name/Version: RHEL 7.6 x86_64*I’m facing a issue if running `puppet node clean someagent.test.com` or `puppetserver ca clean --certname someagent.test.com` and `puppetserver ca list --all` (on the same machine as root) at the same time. This only occurs if I'm running one of the clean commands and the list command concurrently.{code:java}# puppet node clean someagent.test.comWARN: Unresolved specs during Gem::Specification.reset: facter (< 4, >= 2.0.1)WARN: Clearing out unresolved specs.Please report a bug if this causes problems.Notice: Revoked certificate for someagent.test.comNotice: Cleaned files related to someagent.test.comsomeagent.test.com{code} {code:java}# puppetserver ca clean --certname someagent.test.netRevoked certificate for someagent.test.netCleaned files related to someagent.test.net{code} {code:java}# puppetserver ca list --allFatal error when running action 'list' Error: Failed connecting to https://puppet1.test.com:8140/puppet-ca/v1/certificate_statuses/any_key Root cause: SSL_connect returned=1 errno=0 state=error: sslv3 alert certificate unknownFatal error when running action 'list' Error: Failed connecting to https://puppet1.test.com:8140/puppet-ca/v1/certificate_statuses/any_key Root cause: Net::OpenTimeout{code} My Puppet config{code:java}# cat /etc/puppetlabs/puppet/puppet.conf[agent]server=puppet0.test.comreport=truestringify_facts=falseruninterval=1800[master]storeconfigs = truestoreconfigs_backend = puppetdbvardir = /opt/puppetlabs/server/data/puppetserverlogdir = /var/log/puppetlabs/puppetserverrundir = /var/run/puppetlabs/puppetserverpidfile = /var/run/puppetlabs/puppetserver/puppetserver.pidcodedir = /etc/puppetlabs/codessldir=/etc/puppetlabs/puppet/sslmasterreports=puppetdbcertname=puppet1.test.comdns_alt_names=puppet1.test.com,master1.test.comparser=futureautosign=/usr/local/bin/autosign.shca_server=puppet1.test.com[main]rundir=/var/run/puppetlabshiera_config = /etc/puppetlabs/puppet/hiera.yaml{code} *Desired Behavior:*`puppetserver ca list --all` should list certificates *Actual Behavior:* `puppetserver ca list --all` raises on errors{code:java}Fatal error when running action 'list' Error: Failed connecting to https://puppet1.test.com:8140/puppet-ca/v1/certificate_statuses/any_key Root cause: SSL_connect returned=1 errno=0 state=error: sslv3 alert certificate unknown Fatal error when running action 'list' Error: Failed connecting to https://puppet1.test.com:8140/puppet-ca/v1/certificate_statuses/any_key Root cause: Net::OpenTimeout{code}puppetserver.log{code:java}2019-06-19T15:08:08.594+02:00 INFO [clojure-agent-send-off-pool-1] [o.e.j.u.s.SslContextFactory] x509=X509@1e21d885(private key,h=[master1.test.com, puppet1.test.com],w=[]) for InternalSslContextFactory@ 5352bca3[provider=null,keyStore=null,trustStore=null] 2019-06-19T15:08:08.689+02:00 ERROR
Jira (PUP-9785) Unable to connect puppetserver ca endpoints
Title: Message Title
foo bar updated an issue
Puppet / PUP-9785
Unable to connect puppetserver ca endpoints
Change By:
foo bar
*Puppet Version: 6.4.2-1* *Puppet Server Version: 6.3.0* *OS Name/Version: RHEL 7.6 x86_64*I’m facing a issue if running `puppet node clean someagent.test.com` or `puppetserver ca clean --certname someagent.test.com` and `puppetserver ca list --all` (on the same machine as root) at the same time. This only occurs if I'm running one of the clean commands and the list command concurrently.{code:java} # puppet node clean someagent.test.comWARN: Unresolved specs during Gem::Specification.reset: facter (< 4, >= 2.0.1)WARN: Clearing out unresolved specs.Please report a bug if this causes problems.Notice: Revoked certificate for someagent.test.comNotice: Cleaned files related to someagent.test.comsomeagent.test.com{code} {code:java} # puppetserver ca clean --certname someagent.test.netRevoked certificate for someagent.test.netCleaned files related to someagent.test.net{code} {code:java} # puppetserver ca list --allFatal error when running action 'list' Error: Failed connecting to https://puppet1.test.com:8140/puppet-ca/v1/certificate_statuses/any_key Root cause: SSL_connect returned=1 errno=0 state=error: sslv3 alert certificate unknownFatal error when running action 'list' Error: Failed connecting to https://puppet1.test.com:8140/puppet-ca/v1/certificate_statuses/any_key Root cause: Net::OpenTimeout{code} My Puppet config{code:java} # cat /etc/puppetlabs/puppet/puppet.conf[agent]server=puppet0.test.comreport=truestringify_facts=falseruninterval=1800[master]storeconfigs = truestoreconfigs_backend = puppetdbvardir = /opt/puppetlabs/server/data/puppetserverlogdir = /var/log/puppetlabs/puppetserverrundir = /var/run/puppetlabs/puppetserverpidfile = /var/run/puppetlabs/puppetserver/puppetserver.pidcodedir = /etc/puppetlabs/codessldir=/etc/puppetlabs/puppet/sslmasterreports=puppetdbcertname=puppet1.test.comdns_alt_names=puppet1.test.com,master1.test.comparser=futureautosign=/usr/local/bin/autosign.shca_server=puppet1.test.com[main]rundir=/var/run/puppetlabshiera_config = /etc/puppetlabs/puppet/hiera.yaml{code} *Desired Behavior:*`puppetserver ca list --all` should list certificates *Actual Behavior:* `puppetserver ca list --all` raises on errors{code:java} Fatal error when running action 'list' Error: Failed connecting to https://puppet1.test.com:8140/puppet-ca/v1/certificate_statuses/any_key Root cause: SSL_connect returned=1 errno=0 state=error: sslv3 alert certificate unknown Fatal error when running action 'list' Error: Failed connecting to https://puppet1.test.com:8140/puppet-ca/v1/certificate_statuses/any_key Root cause: Net::OpenTimeout{code}puppetserver.log{code:java} 2019-06-19T15:08:08.594+02:00 INFO [clojure-agent-send-off-pool-1] [o.e.j.u.s.SslContextFactory] x509=X509@1e21d885(private key,h=[master1.test.com, puppet1.test.com],w=[]) for InternalSslContextFactory@ 5352bca3[provider=null,keyStore=null,trustStore=null]2019-06-19T15:08:08.689+02:00
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title John O'Connor commented on PUP-9719 Re: Can't run puppet agent after installing the MSI using the SYSTEM account Gareth McGrillan Moving this temporarily to Blocked/Needs Information until we get further reproduction information from the customer as per discussion on Slack Support channel So tried once more to reproduce using their instructions - i.e. copied and modifed `puppet.ps1/puppetrun.ps1` to run on a vmpooler machine and ran both of these using `psexec -s` I then tried `puppet agent -t` as Administrator and it worked without problem. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.52870.1560950700239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title
John O'Connor updated an issue
Puppet / PUP-9719
Can't run puppet agent after installing the MSI using the SYSTEM account
Change By:
John O'Connor
*Puppet Version:* 6.4.2*Puppet Server Version:* N/A*OS Name/Version:* Windows Server 2016 x64When installing Puppet Agent (6.4.2/PE 2019.1.0) on Server 2016 using a Powershell script running as the SYSTEM account, Administrator users can't run Puppet. Daemon/service runs are performed as expected. Direct Puppet runs appear to occur but no report is sent to the master.PUP-8939 had reportedly solved this issue.*Desired Behavior:* *note* - you need to use {{psexec -s}} to repro this on {{vmpooler}} nodes to ensure the SYSTEM account is used: 1. Install: {{psexec -s -i "msiexec.exe" /qn /norestart /l*v C:\windows\temp\puppetinstall.log /i C:\Users\Administrator\Downloads\puppet-agent-6.4.2-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual}}2. Run PA {{psexec -s "C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" agent -t}} 1. Download the Agent 6.4.2 x64 MSI to a temp path (in this example, {{C:\temp\puppet\puppet-agent-x64.msi}}).2. Install Puppet Agent on a Server 2016 node as the SYSTEM user by running {{start-process -filepath "msiexec.exe" -arg "/qn /norestart /l*v C:\windows\temp\puppetinstall.log /i c:\temp\puppet\puppet-agent-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual" -Wait}}3. Populate csr_attributes.yml and {{server}} in the agent config as necessary.4. As an Administrator, run {{puppet agent --test}} on the newly installed agent.*Actual Behavior:*Catalog retrieval fails; log has been redacted: {code} 2019-05-21 17:20:36 -0400 Puppet (debug): HTTP POST https://compiler.example.net:8140/puppet/v3/catalog/examplenode.example.net returned 200 OK2019-05-21 17:20:36 -0400 Puppet (debug): Caching connection for https://compiler.example.net:81402019-05-21 17:20:36 -0400 Puppet (info): Caching catalog for examplenode.example.net2019-05-21 17:20:38 -0400 Puppet (err): ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json, C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json20190521-6580-blokpv): Access is denied. c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/file.rb:89:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:636:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/json.rb:17:in `save'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:200:in `find'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:466:in `block in retrieve_new_catalog'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:518:in `block in thinmark'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:517:in `thinmark'c:/Program
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title John O'Connor assigned an issue to John O'Connor Puppet / PUP-9719 Can't run puppet agent after installing the MSI using the SYSTEM account Change By: John O'Connor Assignee: John O'Connor Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.52750.1560934440956%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
