Jira (PDB-3806) PQL's "in" operator doesn't work on resource parameters
Title: Message Title Daniel Parks commented on PDB-3806 Re: PQL's "in" operator doesn't work on resource parameters Also, as Ryan Whitehurst noted in the PDB-3285 , is null and is not null are still broken. I haven't made an effort to check other operators; these are just things I'm running into. 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 Josh Cooper commented on PUP-8249 Re: Certain environments return "invalid byte sequence in " when parsing module PO files Merged to 5.3.x in https://github.com/puppetlabs/puppet/commit/f27a598ec312030029afdea3bbe871cffae3b7e7 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-252) Run Bolt acceptance tests on merge
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-252 Run Bolt acceptance tests on merge Change By: Michael Smith Release Notes: Not Needed 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-8342) Add transaction_completed to schema
Title: Message Title Kris Bosland updated an issue Puppet / PUP-8342 Add transaction_completed to schema Change By: Kris Bosland 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-8312) i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings
Title: Message Title Eric Delaney commented on PUP-8312 Re: i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/44df5c1d5e02e4610f31049aaadd10e24d6ef3d7 Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/0362bad3a4b436dbeead18f1a00354e1f26493f1 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. Stories1. 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 spec It 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:- 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-289) Standardize Target object
Title: Message Title Michael Smith commented on BOLT-289 Re: Standardize Target object I'm not sure why we need a from_url method if the initializer for Target already takes a single argument that is the url. 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-8342) Add transaction_completed to schema
Title: Message Title Kris Bosland created an issue Puppet / PUP-8342 Add transaction_completed to schema Issue Type: Bug Assignee: Kris Bosland Created: 2018/01/10 3:14 PM Fix Versions: PUP 5.4.0 Priority: Major Reporter: Kris Bosland Forked off of PUP-8288 to track adding the transaction_completed flag to the report schema for serialization/deserialization. Broken out into a separate ticket targeted at master branch to minimize impact to our LTS release at 4.10.x, which the flag/partial fix was added to. Add Comment
Jira (PUP-8341) Lookup interpolation on alias to missing key should return not found
Title: Message Title Henrik Lindberg commented on PUP-8341 Re: Lookup interpolation on alias to missing key should return not found I think this breaking change will lead to problems for existing users as they may be required to change if they rely on empty string interpolation semantics for "not found" (and people do clever things with hiera a lot). With hiera 5 it is possible for anyone to write a simple "aliasing" data provider function - it could be given a hash as an option with "from-to" mappings - and it looks up the "to" when user is looking up "from". That way the data type is preserved and it is a true alias with "not found" semantics. If we want to provide a "not found" resulting alias-interpolation-function (as suggested in this ticket), then I think it needs to be a new hiera interpolation function to make it non-breaking and opt-in. 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-8219) Tidy should only log a notice if there are changes to be made
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8219 Tidy should only log a notice if there are changes to be made Change By: Eric Delaney Method Found: Needs Assessment Manual Test 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-8219) Tidy should only log a notice if there are changes to be made
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8219 Tidy should only log a notice if there are changes to be made Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual 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-8219) Tidy should only log a notice if there are changes to be made
Title: Message Title Eric Delaney commented on PUP-8219 Re: Tidy should only log a notice if there are changes to be made Tested on master at SHA=2317a85efc8ffdcba36f0e478ca944e1eb0b9459 SUITE_VERSION=5.3.3.403.g2317a85 [root@n6nzs73aeyuoi0w ~]# puppet apply foo.pp Notice: Compiled catalog for n6nzs73aeyuoi0w.delivery.puppetlabs.net in environment production in 0.04 seconds Notice: /Stage[main]/Main/Tidy[/tmp/tidy]: Tidying 2 files Notice: /Stage[main]/Main/File[/tmp/tidy/thing]/ensure: removed Notice: /Stage[main]/Main/File[/tmp/tidy/foo]/ensure: removed Notice: Applied catalog in 0.03 seconds [root@n6nzs73aeyuoi0w ~]# puppet apply foo.pp Notice: Compiled catalog for n6nzs73aeyuoi0w.delivery.puppetlabs.net in environment production in 0.04 seconds Notice: Applied catalog in 0.02 seconds
Jira (PUP-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Josh Cooper commented on PUP-7630 Re: "Successful" puppet agent reports hide provider errors Note to watchers, we are making an immediate fix for this issue in PUP-8288 to be released in the next 4.10.x release so that we don't report success if we fail to apply the entire transaction. We are planning additional improvements for all of the issues described here in 5.4.0. 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-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Josh Cooper Fix Version/s: PUP 4.10.z 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-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Josh Cooper Fix Version/s: PUP 5.4.0 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-8288) Exceptions during transaction evaluate reported as success
Title: Message Title Josh Cooper commented on PUP-8288 Re: Exceptions during transaction evaluate reported as success Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/e58f47581365541db09318aff697d93397ece31c 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-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Josh Cooper Comment: Fix merged into 4.10.x at https://github.com/puppetlabs/puppet/commit/e58f47581365541db09318aff697d93397ece31c. 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 (PDB-3802) facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3802 facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array Change By: Russell Mull Fix Version/s: 5.1.4 Fix Version/s: PDB 5.2.0 Fix Version/s: PDB 4.4.2 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 (PDB-3802) facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3802 facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array Change By: Russell Mull Release Notes: Not Needed 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 (PDB-3802) facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3802 facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array Change By: Jeff Yarnell Fix Version/s: 4.2.3.8 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-7685) puppet resource user may show double groups
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7685 puppet resource user may show double groups Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual Release Notes Summary: The 'puppet resource user' now only lists a unique set of groups for a user. Even when a user is in the same group from multiple sources. 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 Jesse Scott updated an issue Puppet / PUP-8082 Add warning to Puppet Module Tool when installing a deprecated module Change By: Jesse Scott Release Notes Summary: The Puppet Module Tool (PMT) will now warn users when interacting with Forge modules that have been "deprecated" by their author. 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Verified that the update is in that build, did discover a minor formatting issue on the search results but I don't think fixing it is a super-high priority, I'll spend a little time investigating a fix 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 (PUP-7685) puppet resource user may show double groups
Title: Message Title Eric Delaney commented on PUP-7685 Re: puppet resource user may show double groups Tested on master at SERVER_VERSION=5.1.4 SHA=2317a85efc8ffdcba36f0e478ca944e1eb0b9459 SUITE_VERSION=5.3.3.403.g2317a85 [root@n6nzs73aeyuoi0w ~]# puppet resource user | grep group groups => ['mail'], groups => ['mail'], [root@n6nzs73aeyuoi0w ~]# grep mail /etc/group mail:x:12:postfix,root,root mail:x:12:postfix,root,root [root@n6nzs73aeyuoi0w ~]# On 5.3.3 puppet will show root and postfix in the mail group 2 times. Add Comment
Jira (BOLT-289) Standardize Target object
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-289 Standardize Target object 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-218) Bolt file_upload should upload files consistent with the context of run-as
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-218 Bolt file_upload should upload files consistent with the context of run-as Change By: Michael Smith Summary: Bolt file_upload should upload files consistent in with the context of run-as 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-218) Bolt file_upload should upload files consistent in the context of run-as
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-218
Bolt file_upload should upload files consistent in the context of run-as
Change By:
Michael Smith
When using {{run-as}}, uploaded files would be expected to be usable in any subsequent tasks. Potentially the file might be uploaded to a location the non-escalated login user doesn't have permission to write to, and that should work.
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-6043) puppet apply -e states "syntax error at end of file" when there is no file
Title: Message Title Eric Delaney commented on PUP-6043 Re: puppet apply -e states "syntax error at end of file" when there is no file Tested with 'SERVER_VERSION=5.1.4 SHA=2317a85efc8ffdcba36f0e478ca944e1eb0b9459 SUITE_VERSION=5.3.3.403.g2317a85' [root@u6uo40q696wiumq ~]# puppet apply -e 'assert_type(type(Integer, "yes. hello")' Error: Could not parse for environment production: Syntax error at end of input on node u6uo40q696wiumq.delivery.puppetlabs.net [root@u6uo40q696wiumq ~]# echo 'assert_type(type(Integer, "yes. hello")' > foo.pp [root@u6uo40q696wiumq ~]# puppet apply foo.pp Error: Could not parse for environment production: Syntax error at end of input (file: /root/foo.pp) on node u6uo40q696wiumq.delivery.puppetlabs.net [root@u6uo40q696wiumq ~]# Add Comment
Jira (PUP-3329) Puppet agent can't clear a stale agent_catalog_run.lock file
Title: Message Title Dylan Ratcliffe commented on PUP-3329 Re: Puppet agent can't clear a stale agent_catalog_run.lock file This should be fixed by PUP-7517 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-281) Update writing tasks doc
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-281 Update writing tasks doc Change By: Michael Smith 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-266) Log run_* actions when called from a plan
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Zach Reichert Assignee: Zach Reichert 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-295) Run any script with extension handler on Windows
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-295 Run any script with extension handler 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 (PUP-8341) Lookup interpolation on alias to missing key should return not found
Title: Message Title Thomas Hallgren commented on PUP-8341 Re: Lookup interpolation on alias to missing key should return not found If we would make this change, then it would be a breaking change. It might also be perceived as inconsistent with how other interpolations work for a "not found" condition. That said, an alias is special in any case (it can for instance alias a hash and a hash will be returned verbatim, i.e. no conversion to string) so the change does make sense. I'm just not sure if it's worth the effort involved when changing established behaviour. Josh Cooper, Henrik Lindberg, what's your thoughts on this? 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-8314) i18n add string decorations to "raise ArgumentError" call
Title: Message Title Eric Delaney commented on PUP-8314 Re: i18n add string decorations to "raise ArgumentError" call Merged part 1 to 5.3.x at https://github.com/puppetlabs/puppet/commit/afca7f10425dfa3b3d237d3573f32710ea290f26 Merged part 2 to 5.3.x at Merged part 3 to 5.3.x at Merged part 4 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 (PUP-8341) Lookup interpolation on alias to missing key should return not found
Title: Message Title Sean Millichamp created an issue Puppet / PUP-8341 Lookup interpolation on alias to missing key should return not found Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Thomas Hallgren Components: Hiera & Lookup Created: 2018/01/10 11:55 AM Priority: Normal Reporter: Sean Millichamp The Hiera interpolation function alias returns an empty string if the key referenced for lookup is not found. In order to preserve the intent of alias and its usefulness in re-mapping key names in lookups it should return a not found condition like a direct lookup of a missing Hiera key would, and not an empty string. For example, given: ---
Jira (BOLT-285) Bolt should handle parser errors better
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-285 Bolt should handle parser errors better 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-302) Inventory
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-302 Inventory Issue Type: Epic Assignee: Unassigned Created: 2018/01/10 11:47 AM Priority: Normal Reporter: Alex Dreyer How bolt discovers and manages information about targets: 1. Connection information about targets 2. Groups of targets 3. Information about the state of targets 4.Target specific parameter defaults and variables 5. History of actions that have happened on target. 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. Stories1. 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 spec h2. Out of scope:- 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)
--
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 (PUP-8340) Update Puppet::Resource::Catalog.alias to use Puppet::Util::Errors.error_location()
Title: Message Title Eric Delaney created an issue Puppet / PUP-8340 Update Puppet::Resource::Catalog.alias to use Puppet::Util::Errors.error_location() Issue Type: Task Affects Versions: PUP 5.3.3 Assignee: Unassigned Created: 2018/01/10 11:22 AM Priority: Normal Reporter: Eric Delaney The 'Puppet::Resource::Catalog.alias' method prints out the location of an error and should be updated to use Puppet::Util::Errors.error_location() instead so that we're being consistent: def alias(resource, key) ... if existing = @resource_table[newref]
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. Stories1. 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- h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- url highesth3. formath2. Out of scope:- 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.
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. Stories1. 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- h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. formath2. Out of scope:- 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.
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
As soon as they get into nontrivial plans, users face a common pattern of needing to map different roles used inside the plan to concrete lists of hosts, which are usually provided dynamically by the executor. In Ansible this is a first-class plugin point called "inventory" and the introductory way to do it is with INI style flat files with a section header containing the role name, a list of hosts below that:{code}[webservers]web01.domain.comweb02.domain.com{code}which is then referenced inside the playbook as {code:yaml} hosts: webservers remote_user: root tasks: - name: ensure apache is at the latest versionyum: name=httpd state=latest - name: write the apache config filetemplate: src="" />{code}This lets users provide different sets of nodes without changing the playbook, akin to the data/code separation that Hiera provides for Puppet. It'll be super important to develop a way to perform this type of mapping, preferably with a combination of conventions ("the roles you use in a plan should be exposed in the plan as parameters of type {{Nodes}}") and an easy way to develop and use plugins to different inventory sources.
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
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 Summary: Design conventions for mapping roles to nodes Support inventory file in plans 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 (FACT-1806) Windows KVM host not recognized as virtual
Title: Message Title Branan Riley commented on FACT-1806 Re: Windows KVM host not recognized as virtual Well that's obviously wrong. I know that some versions of qemu/kvm try to disguise themselves as hyperv to Windows guests. Given how old your host OS is, it's possible we won't be able to detect it correctly. This is definitely something we can look in to the next time we're focused on the hypervisor-detection project, 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 (FACT-1806) Windows KVM host not recognized as virtual
Title: Message Title Branan Riley updated an issue Facter / FACT-1806 Windows KVM host not recognized as virtual Change By: Branan Riley Team: Platform OS 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-8315) i18n add string decorations to Puppet.info calls
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8315 i18n add string decorations to Puppet.info calls Change By: Eric Delaney Release Notes: Not Needed 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-8331) Add translation for issue_reporter.rb error/warning count message
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8331 Add translation for issue_reporter.rb error/warning count message Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action 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-8331) Add translation for issue_reporter.rb error/warning count message
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8331 Add translation for issue_reporter.rb error/warning count message Change By: Eric Delaney Release Notes: Not Needed 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-285) Bolt should handle parser errors better
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-285 Bolt should handle parser errors better Change By: Michael Smith 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-285) Bolt should handle parser errors better
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-285 Bolt should handle parser errors better 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-295) Run any script with extension handler on Windows
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-295 Run any script with extension handler on Windows Change By: Alex Dreyer Fix Version/s: BOLT 0.14.0 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-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Fix Version/s: BOLT 0.14.0 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 (FACT-1803) Core fact disk not available on Windows OS
Title: Message Title Craig Gomes updated an issue Facter / FACT-1803 Core fact disk not available on Windows OS Change By: Craig Gomes Team: Platform OS 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8337 Package source on Windows errors out on deduped installation files Change By: Craig Gomes Sprint: Windows 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-8339) i18n add string decorations to "raise NotImplementedError" call
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8339 i18n add string decorations to "raise NotImplementedError" call Change By: Eric Delaney In the Puppet code when we call "raise ArgumentError NotImplementedError " the string passed most likely should be internationalized. 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-8339) i18n add string decorations to "raise NotImplementedError" call
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8339 i18n add string decorations to "raise NotImplementedError" call Change By: Eric Delaney Acceptance Criteria: - Review calls to "raise ArgumentError NotImplementedError " and determine which need string decorations for i18n- unit tests updated and passing- acceptance tests updated and passing 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-8339) i18n add string decorations to "raise NotImplementedError" call
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8339 i18n add string decorations to "raise NotImplementedError" call Change By: Eric Delaney Assignee: 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-8339) i18n add string decorations to "raise NotImplementedError" call
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8339 i18n add string decorations to "raise NotImplementedError" call Change By: Eric Delaney Sprint: Platform Core KANBAN Hopper 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-8339) i18n add string decorations to "raise NotImplementedError" call
Title: Message Title Eric Delaney created an issue Puppet / PUP-8339 i18n add string decorations to "raise NotImplementedError" call Issue Type: Task Affects Versions: PUP 5.3.3 Assignee: Eric Delaney Created: 2018/01/10 8:27 AM Priority: Normal Reporter: Eric Delaney In the Puppet code when we call "raise ArgumentError" the string passed most likely should be internationalized. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-8336) Update for i18n support of DataHashFunctionProvider and ModuleDataProvider methods
Title: Message Title Henrik Lindberg commented on PUP-8336 Re: Update for i18n support of DataHashFunctionProvider and ModuleDataProvider methods Ping Thomas Hallgren any ideas? 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-222) run_* functions should abort on error
Title: Message Title Henrik Lindberg commented on BOLT-222 Re: run_* functions should abort on error As we discussed in the meeting yesterday - a simple "abort on error" can be implemented by using Ruby throw :bolt_abort which both ensures that it goes straight through all the error/exception handling, and allows passing a value with the reason for the abort. This can be expanded upon later - for example when in the context of running a plan, it could deal with "bolt_abort" from the tasks it is executing. 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-8300) File resource can't handle HTTP redirects when server does not accept HEAD requests
Title: Message Title Mariusz Gronczewski commented on PUP-8300 Re: File resource can't handle HTTP redirects when server does not accept HEAD requests Okay, but why it does 3 HEADs then ? On my localhost server (no redirect, just nginx on localhost serving a directory), just requesting one file yields me access log like that: 127.0.0.1 - - [10/Jan/2018:10:42:18 +0100] "HEAD /rnd HTTP/1.1" 200 0 "-" "Ruby" 127.0.0.1 - - [10/Jan/2018:10:42:18 +0100] "HEAD /rnd HTTP/1.1" 200 0 "-" "Ruby" 127.0.0.1 - - [10/Jan/2018:10:42:18 +0100] "HEAD /rnd HTTP/1.1" 200 0 "-" "Ruby" 127.0.0.1 - - [10/Jan/2018:10:42:18 +0100] "GET /rnd HTTP/1.1" 200 1024 "-" "Ruby" then it downloads the file and saves it in destination... *without checking the checksum*. On next run, it does check the checksum of file on the disk, then re-downloads it: Notice: /Stage[main]/Main/File[/tmp/rnd]/checksum_value: checksum_value changed '34bcf0e1286630afc465ac5f6219cabc97f63567e9f206442d8314a451e406a3' to '19248907fa84d23721987abf90f9f7cbac44c547fd38ef2c0ce31e194eb4d9ed' Notice: Applied catalog in 0.12 seconds and that is repeated in every run. So currently checksum functionality is utterly broken with http (do you want me to make a separate ticket about it?) as having "bad" file on target will still download "bad" file to client as for this ticket, yes, that's a dupe Add Comment
Jira (FACT-1807) Puppet 3.7.4 how to obtain cfacter for it
Title: Message Title Maciej Kostkiewicz commented on FACT-1807 Re: Puppet 3.7.4 how to obtain cfacter for it Yes I am aware that upgrade is the best solution, but sometimes it is almost to impossible with big infrastructure, a lots of procedures and so forth... but thank you for your answer 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 (FACT-1806) Windows KVM host not recognized as virtual
Title: Message Title
Matthias Baur commented on FACT-1806
Re: Windows KVM host not recognized as virtual
Sure, the output is:
PS C:\Windows\system32> facter hypervisors
{
hyperv => {}
}
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
