Jira (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command
Title: Message Title Glenn Sarti commented on BOLT-303 Re: Unable to connect over winrm HTTP with bolt task, but works with bolt command Adding for comments I was testing on Ruby 2.3.1 C:\Source\tmp\reboot-dylan\reboot [master ≡ +2 ~2 -0 !]> bundle exec ruby -I./lib -ropenssl -ve'puts OpenSSL::OPENSSL_VERSION, OpenSSL::OPENSSL_LIBRARY_VERSION' ruby 2.3.1p112 (2016-04-26 revision 54768) [x64-mingw32] OpenSSL 1.0.1l 15 Jan 2015 OpenSSL 1.0.1l 15 Jan 2015 C:\Source\tmp\reboot-dylan\reboot [master ≡ +2 ~2 -0 !]> Tried with Ruby 2.4.1. C:\Source\tmp\reboot-dylan\reboot [master ≡ +2 ~2 -0 !]> bundle exec ruby -I./lib -ropenssl -ve'puts OpenSSL::OPENSSL_VERSION, OpenSSL::OPENSSL_LIBRARY_VERSION' ruby 2.4.1p111 (2017-03-22 revision 58053) [x64-mingw32] OpenSSL 1.0.2k 26 Jan 2017
Jira (PUP-8297) Puppet webrick no longer functions in Ruby 2.3.6/2.4.3 and up
Title: Message Title Rainbow commented on PUP-8297 Re: Puppet webrick no longer functions in Ruby 2.3.6/2.4.3 and up So sorry I never responded Eric, my email server turned into a black hole and has been slurping down all my alerts! It looks like you managed to get what y'all needed though. Thanks for responding and wrangling this, and if there's anything y'all need from me further, the email issue should be resolved now Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-303 Unable to connect over winrm HTTP with bolt task, but works with bolt command Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-303 Unable to connect over winrm HTTP with bolt task, but works with bolt command Change By: Michael Smith Sub-team: Bolt Team: Direct Change Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7968) group resource doesn't default to ensure=>present
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-7968 group resource doesn't default to ensure=>present Change By: Melissa Stone Assignee: Erik Hansen Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command
Title: Message Title Michael Smith commented on BOLT-303 Re: Unable to connect over winrm HTTP with bolt task, but works with bolt command This appears to be a manifestation of https://github.com/rails/rails/issues/25805. Can be "fixed" by ensuring require 'openssl'; OpenSSL::Random.random_bytes(1) is called before requiring Puppet. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8360) Improve documentation of forcelocal and libuser on user resource documentation page
Title: Message Title Garrett Guillotte assigned an issue to Garrett Guillotte Puppet / PUP-8360 Improve documentation of forcelocal and libuser on user resource documentation page Change By: Garrett Guillotte Assignee: Garrett Guillotte Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8360) Improve documentation of forcelocal and libuser on user resource documentation page
Title: Message Title Garrett Guillotte commented on PUP-8360 Re: Improve documentation of forcelocal and libuser on user resource documentation page Dupe of DOCUMENT-800, miscommunication on my part. Closing. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8362) Add setting list add/remove functions to puppet config.
Title: Message Title Craig Gomes created an issue Puppet / PUP-8362 Add setting list add/remove functions to puppet config. Issue Type: Improvement Assignee: Eric Sorenson Components: Community Created: 2018/01/16 4:25 PM Priority: Normal Reporter: Craig Gomes This is the placeholder for the ticket to support editing lists in a section (cloned from original ticket) The puppet config face has facility for creating settings, but not removing or updating lists of settings. From the PR: puppet config add [name] [value] will add to a comma separated list. `puppet config add reports store` -- (adds store to the reports list) puppet config del [name]
Jira (PUP-8361) Create a CI job to generate manpages
Title: Message Title Josh Cooper created an issue Puppet / PUP-8361 Create a CI job to generate manpages Issue Type: Task Assignee: Unassigned Created: 2018/01/16 4:23 PM Priority: Normal Reporter: Josh Cooper Our man pages must be generated manually and are often out of sync when code changes are made to applications or puppet settings (defaults.rb). We should create a CI job in the per-component pipelines, similar to how we do localization. 1. We need to add ronn as a gem dependency, only when running from bundler, not when installing puppet as a gem. Similar to what we do for gettext-setup. 2. We need to run bundle exec rake gen_manpages to update the man pages 3. If that succeeds, run git add man -m "..." 4. Ensure the job that does automatic merge ups always resolves the conflicts as ours. /cc Maggie Dreyer, Branan Riley, Jorie Tappa, Garrett Guillotte Add Comment
Jira (BOLT-308) Update writing plans docs for 0.15.0
Title: Message Title Alex Dreyer commented on BOLT-308 Re: Update writing plans docs for 0.15.0 Michelle Fredette where is the best place to do predocs work for the writing plans page? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-309) Update hands on lab for 0.15.0
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-309 Update hands on lab for 0.15.0 Change By: Alex Dreyer Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8175) facing problem with puppet-agent on window server 2016.
Title: Message Title Ethan Brown commented on PUP-8175 Re: facing problem with puppet-agent on window server 2016. Thanks for the report Manish Pandey. It looks like you specified the wrong name for your puppet master and/or it's not currently resolvable. As such, closing this ticket. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-310) Update task-modules control repo for 0.15.0
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-310 Update task-modules control repo for 0.15.0 Issue Type: Task Assignee: Unassigned Created: 2018/01/16 4:06 PM Priority: Normal Reporter: Alex Dreyer Some of the plans and functions in 0.15.0 will break due to run_* function changes or moving the ExecutionResult to Result set. They'll need to be updated with the release. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-308) Update writing plans docs for 0.15.0
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-308 Update writing plans docs for 0.15.0 Change By: Alex Dreyer Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-309) Update hands on lab for 0.15.0
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-309 Update hands on lab for 0.15.0 Issue Type: Task Assignee: Unassigned Created: 2018/01/16 4:05 PM Priority: Normal Reporter: Alex Dreyer The tasks hands on lab needs to be updated for the 0.15.0 changes to run_* functions and ExecutionResult Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command
Title: Message Title Michael Smith commented on BOLT-303 Re: Unable to connect over winrm HTTP with bolt task, but works with bolt command I've tracked this down to the OpenSSL RC4#update command being much slower for bolt task as part of the NTLM handshake... still trying to figure out why. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-308) Update writing plans docs for 0.15.0
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-308 Update writing plans docs for 0.15.0 Issue Type: Task Assignee: Unassigned Created: 2018/01/16 4:04 PM Priority: Normal Reporter: Alex Dreyer The writing plans docs need to be updated for 0.15.0 to capture the changes to run_* and ExecutionResults Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8360) Improve documentation of forcelocal and libuser on user resource documentation page
Title: Message Title Joel Weierman created an issue Puppet / PUP-8360 Improve documentation of forcelocal and libuser on user resource documentation page Issue Type: Improvement Assignee: Unassigned Created: 2018/01/16 4:04 PM Fix Versions: PUP 4.10.9 Priority: Normal Reporter: Joel Weierman Puppet Version: 2016.4.x Puppet Server Version: 2016.4.6 OS Name/Version: CentOS I am working in an environment where users / groups are managed remotely via Samba. I'm trying to use the existing user documentation to manage some users locally but running into issues in understanding the documentation. The libuser "feature" seems relevant to what I want to accomplish but the documentation on this is extremely sparse on this page: https://puppet.com/docs/puppet/5.3/types/user.html#user-provider-features Desired Behavior: Improve existing documentation re: "libuser" and any associated requirements / dependencies. A few additional sentences explaining how the library can be used, any limitations, and on which particular Operating Systems it's supported would be extremely useful. My understanding is that the current documentation is generated from source code and the associated in-line documentation will need to be updated in order to improve the documentation on the above page.
Jira (PUP-3020) Add action for deleting settings from puppet config
Title: Message Title Josh Cooper commented on PUP-3020 Re: Add action for deleting settings from puppet config After discussion with the team, we've decided to split the issue of deleting a single setting vs managing multivalued settings into different tickets. The latter is filed as PUP-8359. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8359) Provide actions to manage multi-valued attributes with puppet config
Title: Message Title Josh Cooper created an issue Puppet / PUP-8359 Provide actions to manage multi-valued attributes with puppet config Issue Type: Bug Assignee: Unassigned Created: 2018/01/16 3:55 PM Fix Versions: PUP 5.y Priority: Normal Reporter: Josh Cooper Migrated from PUP-3020: It should be possible to append a value to a list-type of setting. It should handle the case where the setting is not defined and is already defined with possibly an empty value. It should be possible to remove a value from a list-type of setting. It should handle cases where the setting has more than one value, has only one value, or the value doesn't exist. Removing the last value should not remove the setting. The delimiter for multiple values should depend on the setting type. For example, we use comma for report processors, but File::PATH_SEPARATOR for path settings. Propose syntax like the following: puppet config add [--section ] will add to a list.
Jira (BOLT-307) Standardize success and failure for plans
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-307
Standardize success and failure for plans
Change By:
Alex Dreyer
Plan success should be defined as "returning" any value.Plan failure should be defined as "raising" an Error. New features: h3. raise_error function: A function to create an raise an exception from a plan. This should accept the information used by the {{Error}} datatype and {{Bolt::Error}}{noformat}raise_error(msg, kind=puppetlabs/plain-error, details={}){noformat} h3. catch_errors option:Add a new {{\_catch\_errors}} option on the {{run_plan}} function. By default plan execution should stop if a plan called with run_plan errors. When a plan is called with {{\_catch\_errors => true}} it should instead return a pcore {{Error}} object containing the error. This should work both for the exceptions thrown by run_* and from the raise_error function. This should not catch errors that cannot be obviously converted to the {{Error}} datatype because they don't have a kind/msg/detailsh3. output:The plan outputter should display error message in red for {{human}} format and the entire error hash as pretty printed json for the {{json}} format
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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 (BOLT-307) Standardize success and failure for plans
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-307
Standardize success and failure for plans
Change By:
Alex Dreyer
Plan success should be defined as "returning" any value.Plan failure should be defined as "raising" an Error.New features: 1. raise_error function: A function to create an raise an exception from a plan. This should accept the information used by the {{Error}} datatype and {{Bolt::Error}} {noformat}raise_error(msg, kind=puppetlabs/plain-error, details={}){noformat} 2. A catch_errors option:Add a new "_catch_errors" {{\_catch\_errors}} option on the {{run_plan}} function. By default plan execution should stop if a plan called with run_plan errors. When a plan is called with {{\_catch\_errors => true}} it should instead return a pcore {{Error}} object containing the error. This should work both for the exceptions thrown by run_* and from the raise_error function. This should not catch errors that cannot be obviously converted to the {{Error}} datatype because they don't have a kind/msg/details 3 h3 . output: The plan outputter should display error message in red for {{human}} format and the entire error hash as pretty printed json for the {{json}} format
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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.
Jira (PUP-3020) Add action for deleting settings from puppet config
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3020 Add action for deleting settings from puppet config Change By: Josh Cooper Acceptance Criteria: * It should be possible to delete/unset a setting from puppet.conf, so that the default value defined in code is used. It should be possible to append * Deleting a value to a list-type of setting . It should handle the case where the setting whose value is not defined and is already defined with possibly set should not produce an empty value error . It should be possible to remove a value from a list-type of setting like "ensure => absent" . It should handle cases where the setting has more than one value, has only one value, or the value doesn't exist. Removing the last value should not remove the setting. The delimiter for multiple values should depend on the setting type. For example, we use comma for report processors, but File::PATH_SEPARATOR for path settings. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3020) Add action for deleting settings from puppet config
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-3020
Add action for deleting settings from puppet config
Change By:
Josh Cooper
*Updated* The puppet config app cannot delete settings it previously set. Propose the following syntax:{code}puppet config delete [--section ]{code}If a section is specified, the setting is removed from that section, allowing a lower precedence section {{main}} or the defaults in code to take effect. If a section is not specified, the setting should be removed from the default {{main}} section. Trying to delete a setting that hasn't been set should not be an error.Adding to and deleting from multivalued settings is being moved to a separate ticket.*Original Description*The puppet config face has facility for creating settings, but not removing or updating lists of settings.From the PR:{code}puppet config add [name] [value] will add to a comma separated list. `puppet config add reports store` -- (adds store to the reports list)puppet config del [name] [value] will remove from a comma separated list `puppet config del reports store` -- (deletes store from the list)puppet config del [name] will remove a setting from puppet.conf `puppet config del reporturl` -- (removes reporturl from puppet.conf){code}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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
Jira (BOLT-307) Standardize success and failure for plans
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-307
Standardize success and failure for plans
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/01/16 3:49 PM
Priority:
Normal
Reporter:
Alex Dreyer
Plan success should be defined as "returning" any value. Plan failure should be defined as "raising" an Error.
New features: 1. A function to create an raise an exception from a plan. This should accept the information used by the Error datatype and Bolt::Error
raise_error(msg, kind=puppetlabs/plain-error, details={})
2. A new "catch_errors" option on the run_plan function. By default plan execution should stop if a plan called with run_plan errors. When a plan is called with _catch_errors => true it should instead return a pcore Error object containing the error. This should work both for the exceptions thrown by run* and from the raise_error function. 3. The plan outputter should display error message in red for human format and the entire error hash as pretty printed json for the json format
Jira (PUP-3020) Add action for deleting settings from puppet config
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3020 Add action for deleting settings from puppet config Change By: Josh Cooper Summary: Add setting delete and setting list add/remove functions to action for deleting settings from puppet config . Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-6702) Windows service in Paused state cannot be managed
Title: Message Title Michael Smith commented on PUP-6702 Re: Windows service in Paused state cannot be managed I'll have to look into that. Last I checked, there wasn't a way to make PATH override system32; I think the only thing that works is to put the binaries in the same directory. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8107) Ability to specify source IP for the agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8107 Ability to specify source IP for the agent Change By: Josh Cooper Release Notes Summary: The `sourceaddress` setting can now be used to specify which interface the agent should use for outbound HTTP requests. It may be necessary to set this if the agent is running on a host with multiple interfaces. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-6702) Windows service in Paused state cannot be managed
Title: Message Title Josh Cooper commented on PUP-6702 Re: Windows service in Paused state cannot be managed The pxp-agent service should be configuring its PATH so that our vendored openssl takes precedence over any directory including system32. Please file a pxp-agent ticket if there isn't one already. /cc Michael Smith, Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command
Title: Message Title Michael Smith commented on BOLT-303 Re: Unable to connect over winrm HTTP with bolt task, but works with bolt command Definitely reproduce it. My guess is loading Puppet is introducing something that slows it all down, but I'm having to dig deep into the WinRM gem to figure out what. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7482 Agent sends wrong content-type when using http file sources Change By: Josh Cooper Release Notes Summary: Puppet can now retrieve file sources from webservers when the associated MIME type is not "binary". This affects affects IIS webservers in particular. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Acceptance Criteria: * rspec tests includes ability to ensure that output is being written to stderr* test to validate warning to stderr when no section provided* config help - manually verify content * stdout is not altered Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-2868) `puppet config print` confusing for users
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Craig Gomes
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. 'main' is the default.An example: You may have a server setting that is already in the agent setting. When you ran puppet config set server "value" - that will throw it in the "main" section. There already exists a server setting in the " agent " section that is overriding this. The next time you run puppet config print - you will get the one out of the main section (not the overriding agent setting)1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.comAlso print any other settings found that may/will override this setting as in the example above - "Setting is also defined in the following sections: X, Y, Z"2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section:* what the list of commonly used sections are * guidance on naming sections* the output of the help command point to the sections documentation* Include a good solid example of sections (what settings go in what section)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Craig Gomes
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. 'main' is the default. An example: You may have a server setting that is already in the agent setting. When you ran puppet config set server "value" - that will throw it in the "main" section. There already exists a server setting in the agent section that is overriding this. The next time you run puppet config print - you will get the one out of the main section (not the overriding agent setting) 1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.com Also print any other settings found that may/will override this setting as in the example above - "Setting is also defined in the following sections: X, Y, Z" 2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section:* what the list of commonly used sections are * guidance on naming sections* the output of the help command point to the sections documentation* Include a good solid example of sections (what settings go in what section)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8358) puppet server's compile and puppet apply differs for String.new for an Array
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8358
puppet server's compile and puppet apply differs for String.new for an Array
Change By:
Henrik Lindberg
Summary:
{brief summary of issue} puppet server's compile and puppet apply differs for String.new for an Array
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Acceptance Criteria: * rspec tests includes ability to ensure that output is being written to stderr* test to validate warning to stderr when no section provided * config help - manually verify content Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-2868) `puppet config print` confusing for users
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Craig Gomes
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section.1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.com2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section , and :* what the list of commonly used sections are along with * guidance on naming sections . * the output of the help command point to the sections documentation* Include a good solid example of sections (what settings go in what section)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-2868
`puppet config print` confusing for users
Change By:
Craig Gomes
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command.The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section.1. Always print section info to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'puppetserver.example.com2. If section is omitted, also emit a warning to stderr:$ puppet config print serverResolving settings from section 'main' in environment 'production'No section specified, using 'user' section - settings will not affect agent execution!puppetserver.example.com3. Update "config" help to strongly recommend always specifying a section, and what the list of valid commonly used sections are along with guidance on naming sections .
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Acceptance Criteria: Acceptance * rspec tests includes ability to ensure that output is being written to stderr * test to validate warning to stderr when no section provided Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes Acceptance Criteria: Acceptance tests includes ability to ensure that output is being written to stderr Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7542) Puppet Config
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-7542
Puppet Config
Change By:
Craig Gomes
{{puppet config}} was intended as replacement for {{puppet agent --configprint}} and {{puppet master --configprint}}, however, it has a number of issues.The goal of this epic is to fix bugs and reconcile the feature mismatch between the two. Once we are feature compatible with the old ones we can start adding deprecation warnings to them.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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-7542) Puppet Config
Title: Message Title
Craig Gomes updated an issue
Puppet / PUP-7542
Puppet Config
Change By:
Craig Gomes
{{puppet config}} was intended as replacement for {{puppet agent --configprint}} and {{puppet master --configprint}}, however, it has a number of issues. The goal of this epic is to fix bugs and reconcile the feature mismatch between the two.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7482 Agent sends wrong content-type when using http file sources Change By: Josh Cooper Release Notes Summary: Puppet can now retrieve file sources from webservers when the associated MIME type is not "binary". This affects affects IIS webservers in particular. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Adam Gardner commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax I'd like to point out, the absence of exported resources in Puppet Forge modules seems like a pretty big red herring; I suspect (obviously I can't prove) that exported resources are most often created and consumed by organization-specific Puppet code that never gets published to forge.puppet.com. Certainly, that's how we're using them. That's not to say I'm not in favor of eventually deprecating these features, and the idea of being able to use PuppetDB as a key-value store without having to create dummy types (either instead of or in addition to collecting resources) has a lot of appeal. But for the moment I agree with Sean, John, etc, the current alternatives aren't quite there yet. At the very least, if you're going to deprecate these features, add functions to query PuppetDB into stdlib. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Josh Cooper assigned an issue to Kris Bosland Puppet can now retrieve file sources from webservers when the associated MIME type is not "binary". This affects affects IIS webservers in particular. Puppet / PUP-7482 Agent sends wrong content-type when using http file sources Change By: Josh Cooper Assignee: Jacob Helwig Kris Bosland Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7394) Puppet::Util.replace_file cannot be used to create a read-only file (on non-Windows)
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7394 Puppet::Util.replace_file cannot be used to create a read-only file (on non-Windows) Change By: Jorie Tappa Sub-team: Coremunity Story Points: 3 Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title Craig Gomes assigned an issue to Eric Delaney Puppet / PUP-8249 Certain environments return "invalid byte sequence in " when parsing module PO files Change By: Craig Gomes Assignee: Maggie Dreyer Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8013) Translations should be stored in different text domains based on environment
Title: Message Title Craig Gomes assigned an issue to Eric Delaney Puppet / PUP-8013 Translations should be stored in different text domains based on environment Change By: Craig Gomes Assignee: Maggie Dreyer Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Craig Gomes assigned an issue to Jacob Helwig Puppet / PUP-7482 Agent sends wrong content-type when using http file sources Change By: Craig Gomes Assignee: Kris Bosland Jacob Helwig Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Josh Cooper commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Additional fixed merged to master in https://github.com/puppetlabs/puppet/commit/231a04816bf2063415b56bd8767fc06aea20b867. See PR for steps to verify. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8223) User and group modifications should respect forcelocal
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8223 User and group modifications should respect forcelocal Change By: Melissa Stone Assignee: Trey Dockendorf Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7968) group resource doesn't default to ensure=>present
Title: Message Title Melissa Stone updated an issue Puppet / PUP-7968 group resource doesn't default to ensure=>present Change By: Melissa Stone Sub-team: Coremunity Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The default location for the inventory file is ~/.puppetlabs/bolt/inventory.yaml- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. - Bolt should not error with an invalid inventory file or one where the version is not '1.0' .(unexpected keys do not make an Inventory invalid)h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical specsee: https://docs.google.com/document/d/1V2LwAit-17GxWMrfPW7qFMwSdSnaJ7NdUEywNNVPlJM/edith2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8356) Replace use of facter for detecting fips mode with a local method
Title: Message Title Jayant Sane assigned an issue to Jayant Sane Puppet / PUP-8356 Replace use of facter for detecting fips mode with a local method Change By: Jayant Sane Assignee: Jayant Sane Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8356) Replace use of facter for detecting fips mode with a local method
Title: Message Title Jayant Sane commented on PUP-8356 Re: Replace use of facter for detecting fips mode with a local method PR: https://github.com/puppetlabs/puppet/pull/6532 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8358) {brief summary of issue}
Title: Message Title
Adam S updated an issue
Puppet / PUP-8358
{brief summary of issue}
Change By:
Adam S
*Puppet Version:* 1.10.0*Puppet Server Version:* 2.7.2*OS Name/Version:* CentOS 7.4*Desired Behavior:* Masterful and Masterless should behave identically*Actual Behavior:* Masterful breaks(doesn't identify Array during String.new), and Masterless is correctExamples:Prepared an EPP template for testing and found a difference between Masterful and Masterless results.{code:puppet}# testmodule/manifests/init.pp class testmodule {file { '/tmp/test.conf': ensure => file, content => epp('testmodule/test.conf.epp')} }# end of testmodule/manifests/init.pp{code}{code:puppet}# testmodule/templates/test.conf.epp <% $formats = { Array => {format => '%(a', string_formats => { Integer => '%#x' } }, } $str = String([1,2,3], $formats) -%> <%= $str %># end of testmodule/templates/test.conf.epp{code}When I apply testmodule to the node and run(Masteful)puppet agent -t>>> [1, 2, 3](Masterless)puppet apply -e 'include testmodule'>>> (0x1, 0x2, 0x3) I'm not sure if this affects Puppetserver in the new 5.x or not, I'll see if I can get around to testing that.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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-8358) {brief summary of issue}
Title: Message Title
Adam S updated an issue
Puppet / PUP-8358
{brief summary of issue}
Change By:
Adam S
*Puppet Version:* 1.10.0 *Puppet Server Version:* 2.7.2 *OS Name/Version:* CentOS 7.4 Describe your issue in as much detail as possible…Describe steps to reproduce… *Desired Behavior:* Masterful and Masterless should behave identically *Actual Behavior:* Please take a moment and attach any relevant log output and/or manifests Masterful breaks(doesn't identify Array during String . This will help us immensely when troubleshooting the issue. new), and Masterless is correct Examples:Prepared an EPP template for testing and found a difference between Masterful and Masterless results.{code:puppet}# testmodule/manifests/init.pp class testmodule {file { '/tmp/test.conf': ensure => file, content => epp('testmodule/test.conf.epp')} }# end of testmodule/manifests/init.pp{code}{code:puppet}# testmodule/templates/test.conf.epp <% $formats = { Array => {format => '%(a', string_formats => { Integer => '%#x' } }, } $str = String([1,2,3], $formats) -%> <%= $str %># end of testmodule/templates/test.conf.epp{code}When I apply testmodule to the node and run (Masteful) Run puppet agent with - -test --trace --debug t >>> [1, 2, 3] Relevant sections of {{/var/log/puppetlabs/puppetserver/puppetserver.log}} or any applicable logs from the same directory. (Masterless) For more detailed information turn up the server logs by upping the log level in the server puppet apply -e ' s logback.xml include testmodule' Relevant sections of configurations files >>> ( puppet.conf 0x1 , hiera.conf 0x2 , Server's conf.d, defaults/sysconfig 0x3 ) For memory issues with server heap dumps are also helpful.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8358) {brief summary of issue}
Title: Message Title
Adam S created an issue
Puppet / PUP-8358
{brief summary of issue}
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/01/16 1:41 PM
Environment:
puppetserver-2.7.2-1.el7.noarch puppet-agent-1.10.0-1.el7.x86_64 CentOS 3.10.0-693.5.2.el7.x86_64
Priority:
Normal
Reporter:
Adam S
Puppet Version: Puppet Server Version: OS Name/Version:
Describe your issue in as much detail as possible… Describe steps to reproduce…
Desired Behavior:
Actual Behavior:
Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.
Examples: Prepared an EPP template for testing and found a difference between Masterful and Masterless results.
# testmodule/manifests/init.pp
class testmodule {
Jira (PUP-4963) "puppet module build" fails on FIPS-enabled system
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4963 "puppet module build" fails on FIPS-enabled system Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4963) "puppet module build" fails on FIPS-enabled system
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4963 "puppet module build" fails on FIPS-enabled system Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4963) "puppet module build" fails on FIPS-enabled system
Title: Message Title Josh Cooper assigned an issue to Jayant Sane Puppet / PUP-4963 "puppet module build" fails on FIPS-enabled system Change By: Josh Cooper Assignee: Jayant Sane Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-217) Run privileged operations on Windows
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-217 Run privileged operations on Windows Change By: Michael Smith Being able to escalate permissions on Windows is desirable to allow running WindowsUpdate via Bolt.Some background links:- https://serverfault.com/questions/645604/howto-initiate-windows-update-on-server-core-from-a-ps-remote-session/645619#645619- https://msdn.microsoft.com/en-us/library/windows/desktop/aa387288%28v=vs.85%29.aspx?f=255=-2147217396- https://github.com/WinRb/winrm-elevated may be an option for addressing thisCurrently this seems best-served as a specific task that uses scheduled task to trigger an update. If there are a wider variety of use-cases, it could be turned into an operational mode for Bolt. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-217) Run privileged operations on Windows
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-217 Run privileged operations on Windows Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command
Title: Message Title Michael Smith commented on BOLT-303 Re: Unable to connect over winrm HTTP with bolt task, but works with bolt command I'm not sure why that particular section would be slower for task vs command... I guess I'll try to reproduce your findings. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8321) Update how warn_once and deprecation warnings print their location and i18n messages
Title: Message Title Eric Delaney commented on PUP-8321 Re: Update how warn_once and deprecation warnings print their location and i18n messages Update warn_once and deprecation strings to 5.3.x at Update warn_once calls to 5.3.x at https://github.com/puppetlabs/puppet/commit/5426e29ab25ee442380b5bd49d8d5aaa1346b194 Update deprecation_warning calls to 5.3.x at Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8357) Listing tasks incorrectly maps files to task names
Title: Message Title Nick Lewis commented on PUP-8357 Re: Listing tasks incorrectly maps files to task names Yes. I'm not sure where else this code path might be triggered though. It's this bit of code that has the problem. I have a fix working, but I can't figure out how to write a test that works for it... Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8227 Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Change By: Josh Cooper Fix Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Josh Cooper commented on PUP-8227 Re: Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Merged to 5.3.x in https://github.com/puppetlabs/puppet/commit/e951eb99c0cae72ea9fb10026ddb31bebd74eadc Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8357) Listing tasks incorrectly maps files to task names
Title: Message Title Henrik Lindberg commented on PUP-8357 Re: Listing tasks incorrectly maps files to task names Is this via PAL? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8357) Listing tasks incorrectly maps files to task names
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet / PUP-8357 Listing tasks incorrectly maps files to task names Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8357) Listing tasks incorrectly maps files to task names
Title: Message Title Nick Lewis moved an issue Puppet / PUP-8357 Listing tasks incorrectly maps files to task names Change By: Nick Lewis Key: BOLT PUP - 306 8357 Project: Puppet Task Runner Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-306) Listing tasks incorrectly maps files to task names
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-306 Listing tasks incorrectly maps files to task names Change By: Nick Lewis Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-186) Comprehensive strings style guide
Title: Message Title Jean Bond commented on PDOC-186 Re: Comprehensive strings style guide Assigning this to myself as I work on drafting this and compiling feedback. That doesn't mean Eric Putnam is off the hook, though. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-186) Comprehensive strings style guide
Title: Message Title Jean Bond assigned an issue to Jean Bond Puppet Strings / PDOC-186 Comprehensive strings style guide Change By: Jean Bond Assignee: Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8347) Find more places where we report the file or line information and convert them to use error_location()
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8347
Find more places where we report the file or line information and convert them to use error_location()
Change By:
Eric Delaney
We need to grep the puppet code base and find more of the locations that we report the file and line location information for an error and use the Puppet::Util::Errors.error_location() method to create the string so we are consistent.For example:{code}16:03 $ grep -nr 'at line' liblib/puppet/settings/config_file.rb:86:raise(Puppet::Error, _("Illegal section '%{name}' in config file %{file} at line %{line}. The only valid puppet.conf sections are: [%{allowed_sections}]. Please use the directory environments feature to specify environments. (See https://docs.puppet.com/puppet/latest/reference/environments.html)") % { name: section.name, file: file, line: section.line_number, allowed_sections: allowed_section_names.join(", ") })lib/puppet/pops/issues.rb:779:fl ? _("%{msg}. First defined at line %{line}") % { msg: msg, line: fl } : msglib/puppet/pops/issues.rb:789:fl ? _("%{msg}. First defined at line %{line}") % { msg: msg, line: fl } : msglib/puppet/util/network_device/config.rb:55:raise Puppet::Error, _("Duplicate device found at line %{count}, already found at %{line}") % { count: count, line: device.line } if devices.include?(name)lib/puppet/util/network_device/config.rb:94: raise Puppet::Error, _("Invalid argument '%{var}' at line %{count}") % { var: var, count: count }lib/puppet/network/auth_config_parser.rb:32: raise Puppet::ConfigurationError, _("Missing or invalid 'path' before right directive at line %{count} of %{file}") % { count: count, file: @file }lib/puppet/network/auth_config_parser.rb:69:_("Invalid argument '%{var}' at line %{count}") % { var: var, count: count }lib/puppet/network/auth_config_parser.rb:80:raise Puppet::ConfigurationError, _("%{detail} at line %{count} of %{file}") % { detail: detail, count: count, file: @file }, detail.backtrace -lib/puppet/provider/package/gem.rb:55:# but when it's not to the console that line--lib/puppet/type/ssh_authorized_key.rb:7: to split that line into several attributes. Thus, a key that appears in- ${code}More cases to consider:{code}16:05 $ egrep -nr 'at .*file.*:.*line' liblib/puppet/settings/config_file.rb:86:raise(Puppet::Error, _("Illegal section '%{name}' in config file %{file} at line %{line}. The only valid puppet.conf sections are: [%{allowed_sections}]. Please use the directory environments feature to specify environments. (See https://docs.puppet.com/puppet/latest/reference/environments.html)") % { name: section.name, file: file, line: section.line_number, allowed_sections: allowed_section_names.join(", ") })lib/puppet/file_serving/configuration/parser.rb:43: raise ArgumentError.new(_("Invalid line '%{line}' at %{file}, line %{line_num}") % { line: line.chomp, file: @file.filename, line_num: @count })lib/puppet/file_serving/configuration/parser.rb:89:raise ArgumentError.new(_("%{mount} is already mounted at %{name} in %{file}, line %{line_num}") % { mount: @mounts[name], name: name, file: @file, line_num: @count }) if @mounts.include?(name)lib/puppet/util/logging.rb:184: _("\n (at
Jira (PUP-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8041 Replace FACTER_url with --target for puppet resource with devices Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-306) Listing tasks incorrectly maps files to task names
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-306 Listing tasks incorrectly maps files to task names Issue Type: Bug Assignee: Unassigned Created: 2018/01/16 11:06 AM Priority: Normal Reporter: Nick Lewis Currently, puppet uses basic substring matching to determine which files are associated with a given task. That causes task files to be incorrectly associated with tasks in the case where the name of one task is a prefix of another task. For example: $ ls tasks foo.sh foo.json foobar.sh
Jira (PUP-7057) Update password property of User type to mention Sensitive data type
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7057
Update password property of User type to mention Sensitive data type
Change By:
Josh Cooper
Comment:
Hi [~jorie] I think we want to say that the `Sensitive` datatype is useful in cases like the user's password property. It can be used like:{code:puppet}user { 'foo': ensure => present, password => Sensitive("my secret password")}{code}The {{Sensitive}} data type will cause puppet to redact the {{previous_value}} and {{desired_value}} in the report that it sends to puppetdb, and which is eventually viewable in the console.{code:yaml}events:- !ruby/object:Puppet::Transaction::Event audited: false property: password previous_value: "[redacted]" desired_value: "[redacted]" historical_value: message: changed [redacted] to [redacted] name: :password_changed status: success time: 2017-05-17 16:06:02.934398293 -07:00 redacted: true corrective_change: falsecorrective_change: false{code}The sensitive data type is also handy in {{scheduled_task}}, {{yum_repo}}, p
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. - Bolt should not error with an invalid inventory file or one where the version is not '1.0' .(unexpected keys do not make an Inventory invalid)h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical spec It will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges see: https://docs . At this stage we should prioritize a robust schema for API use over user friendliness to some extent google . We will handle easy to write formats in later tickets. com/document/d/1V2LwAit-17GxWMrfPW7qFMwSdSnaJ7NdUEywNNVPlJM/edit example file: h2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. - Bolt should not error with an invalid inventory file or one where the version is not '1 . 0' .(unexpected keys do not make an Inventory invalid) h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical specIt will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges. At this stage we should prioritize a robust schema for API use over user friendliness to some extent. We will handle easy to write formats in later tickets. example file:h2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. - Bolt should not error with an invalid inventory file. h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical specIt will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges. At this stage we should prioritize a robust schema for API use over user friendliness to some extent. We will handle easy to write formats in later tickets. example file:h2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories 1. I want to make lists of nodes in a file and target them by name. 2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical specIt will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges. At this stage we should prioritize a robust schema for API use over user friendliness to some extent. We will handle easy to write formats in later tickets. example file:h2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8297) Puppet webrick no longer functions in Ruby 2.3.6/2.4.3 and up
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8297 Puppet webrick no longer functions in Ruby 2.3.6/2.4.3 and up Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-279) '_error' key is ignored by bolt if task does not exit 1
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-279 '_error' key is ignored by bolt if task does not exit 1 Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-287) Standardize calling for run_ functions on nodes.
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-287 Standardize calling for run_ functions on nodes. Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-209) Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-209 Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8347) Find more places where we report the file or line information and convert them to use error_location()
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8347
Find more places where we report the file or line information and convert them to use error_location()
Change By:
Eric Delaney
We need to grep the puppet code base and find more of the locations that we report the file and line location information for an error and use the Puppet::Util::Errors.error_location() method to create the string so we are consistent.For example:{code}16:03 $ grep -nr 'at line' liblib/puppet/settings/config_file.rb:86:raise(Puppet::Error, _("Illegal section '%{name}' in config file %{file} at line %{line}. The only valid puppet.conf sections are: [%{allowed_sections}]. Please use the directory environments feature to specify environments. (See https://docs.puppet.com/puppet/latest/reference/environments.html)") % { name: section.name, file: file, line: section.line_number, allowed_sections: allowed_section_names.join(", ") })lib/puppet/pops/ validation.rb:336:" at line #{line}:#{pos}"lib/puppet/pops/validation.rb:338:" at line #{line}"lib/puppet/pops/ issues.rb:779:fl ? _("%{msg}. First defined at line %{line}") % { msg: msg, line: fl } : msglib/puppet/pops/issues.rb:789:fl ? _("%{msg}. First defined at line %{line}") % { msg: msg, line: fl } : msglib/puppet/util/network_device/config.rb:55:raise Puppet::Error, _("Duplicate device found at line %{count}, already found at %{line}") % { count: count, line: device.line } if devices.include?(name)lib/puppet/util/network_device/config.rb:94: raise Puppet::Error, _("Invalid argument '%{var}' at line %{count}") % { var: var, count: count }lib/puppet/network/auth_config_parser.rb:32: raise Puppet::ConfigurationError, _("Missing or invalid 'path' before right directive at line %{count} of %{file}") % { count: count, file: @file }lib/puppet/network/auth_config_parser.rb:69:_("Invalid argument '%{var}' at line %{count}") % { var: var, count: count }lib/puppet/network/auth_config_parser.rb:80:raise Puppet::ConfigurationError, _("%{detail} at line %{count} of %{file}") % { detail: detail, count: count, file: @file }, detail.backtrace-lib/puppet/provider/package/gem.rb:55:# but when it's not to the console that line--lib/puppet/type/ssh_authorized_key.rb:7: to split that line into several attributes. Thus, a key that appears in-${code}More cases to consider:{code}16:05 $ egrep -nr 'at .*file.*:.*line' liblib/puppet/settings/config_file.rb:86:raise(Puppet::Error, _("Illegal section '%{name}' in config file %{file} at line %{line}. The only valid puppet.conf sections are: [%{allowed_sections}]. Please use the directory environments feature to specify environments. (See https://docs.puppet.com/puppet/latest/reference/environments.html)") % { name: section.name, file: file, line: section.line_number, allowed_sections: allowed_section_names.join(", ") })lib/puppet/file_serving/configuration/parser.rb:43: raise ArgumentError.new(_("Invalid line '%{line}' at %{file}, line %{line_num}") % { line: line.chomp, file: @file.filename, line_num: @count })lib/puppet/file_serving/configuration/parser.rb:89:raise ArgumentError.new(_("%{mount} is already mounted at %{name} in %{file}, line %{line_num}") % { mount: @mounts[name], name:
Jira (PUP-8356) Replace use of facter for detecting fips mode with a local method
Title: Message Title Jayant Sane created an issue Puppet / PUP-8356 Replace use of facter for detecting fips mode with a local method Issue Type: Task Assignee: Jayant Sane Created: 2018/01/16 8:57 AM Fix Versions: PUP 5.4.0 Priority: Normal Reporter: Jayant Sane *Puppet Version: master branch (going into 5.4.0 release) Puppet Server Version:5.1.x OS Name/Version: N/A PUP-8141 adjusts use of md5 based on whether fips mode is enabled or not. Some of these changes in Puppet settings. FIPS mode detection was done using facter. However since Puppet is also used by Puppet Server and it does not have ability to load facter due to some missing dependencies and its use of an older version of facter (which do not have support for FIPS fact). It be noted that this is not an issue in production but on dev systems when running puppet server from sources. This ticket is to replace the use of facter to detect FIPS mode with a local method, which will duplicate the functionality in facter, to do the same. Temporarily a workaround was created in puppetserver per this PR: https://github.com/puppetlabs/puppetserver/pull/1597
Jira (PUP-8351) PA-437 fix causes pip provider failures when SCL version is installed
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8351 PA-437 fix causes pip provider failures when SCL version is installed Change By: Owen Rodabaugh CS Priority: Needs Priority Minor CS Impact: This issue occurs because the pip provider we ship does not expect the use of SCL. The impact of this could be a failed upgrade/postgres migration.At minimum we should document the assumptions this provider has and then at some point update the provider to handle these cases(if that is possible) CS Severity: 3 - Serious CS Business Value: 2 - $$$ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-6702) Windows service in Paused state cannot be managed
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6702 Windows service in Paused state cannot be managed Change By: Owen Rodabaugh Method Found: Customer Feedback Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-6702) Windows service in Paused state cannot be managed
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6702 Windows service in Paused state cannot be managed Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: If openssl libraries(of a different version than ours) are installed in the Windows system folders then the PXP agent will fail to start. The workaround is to is to reorder the path or remove or replace those library files in other locations. This has come up with 5-10x in the last few weeks, a very high rate of occurrence. CS Severity: 4 - Major CS Business Value: 5 - $$ CS Frequency: 3 - 25-50% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (FACT-1737) Disks & partitions for FreeBSD
Title: Message Title Romain Tartière commented on FACT-1737 Re: Disks & partitions for FreeBSD Hi! I opened a Pull-Request on GitHub to add support for "disks" and "partitions" facts on FreeBSD a few months ago, and would like to go further in that direction, however, I have not had feedback yet. Before proposing to collect disks models and serial numbers, may I request feedback on this issue? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
