Jira (PUP-9472) Use OpenSSL::X509::Name#to_utf8
Title: Message Title Josh Cooper created an issue Puppet / PUP-9472 Use OpenSSL::X509::Name#to_utf8 Issue Type: New Feature Assignee: Unassigned Created: 2019/02/01 4:44 PM Priority: Normal Reporter: Josh Cooper Calling OpenSSL::X509::Name#to_s with a non USASCII string generates a binary ruby string, which can cause problems when later string operations are performed. We should always use the to_utf8 method instead. irb(main):013:0> name = "CN=root-ca-天" => "CN=root-ca-天" irb(main):014:0> irb(main):015:0> OpenSSL::X509::Name.parse(name).to_s => "/CN=root-ca-\\xE5\\xA4\\xA9" irb(main):016:0> OpenSSL::X509::Name.parse(name).to_s.encoding
Jira (PUP-6885) Remove warning about server_list and server conflicting
Title: Message Title Melissa Stone updated an issue Puppet / PUP-6885 Remove warning about server_list and server conflicting Change By: Melissa Stone Release Notes Summary: Conflict warning between `server` and `server_list` has been removed. There are scenarios where it is appropriate to have both `server` and `server_list` defined in a config. Release Notes: Known Issue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1109) Create `dynamic` inventory group attribute
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1109 Create `dynamic` inventory group attribute Issue Type: Task Assignee: Unassigned Created: 2019/02/01 4:03 PM Priority: Normal Reporter: Lucy Wyman This adds new attributes to Bolt::Inventory::Group called dynamic and data_paths, which if specified on a group will load node information from a json file (specifically a terraform state file) when the function inventory_from_json is called in a plan. dynamic is a boolean value which indicates whether the group should generate new inventory when inventory_from_json is called or not. If it is set to true and has nodes defined the node list should be merged with the dynamic inventory. If it is set to false, then no dynamic inventory should be loaded. data_paths is an array of data paths represented as an array of selectors to navigate the JSON data to where we can expect to find hostnames to load as inventory. Questions: Are dynamic, data_paths, and inventory_from_json the write words for what these components are doing? "If it is set to true and has nodes defined the node list should be merged with the dynamic inventory" - this seems doable, but if it's complex I think we can say that any nodes listed will be ignored if dynamic is true. Can we do glob expantion as part of datapaths, so that users don't need to enumerate each specific node? - name: dyn
Jira (PUP-6885) Remove warning about server_list and server conflicting
Title: Message Title Melissa Stone commented on PUP-6885 Re: Remove warning about server_list and server conflicting This has passed ci as a part of puppet agent 5.5.10.52.g9aa1bfd Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6571) An invalid path to the --logdest option is silently ignored
Title: Message Title Melissa Stone commented on PUP-6571 Re: An invalid path to the --logdest option is silently ignored This has passed ci as a part of puppet agent 5.5.10.52.g9aa1bfd Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9076) Puppet agent should not fall back to puppet:0 when servers in server_list are unreachable
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-9076 Puppet agent should not fall back to puppet:0 when servers in server_list are unreachable Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9076) Puppet agent should not fall back to puppet:0 when servers in server_list are unreachable
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9076 Puppet agent should not fall back to puppet:0 when servers in server_list are unreachable Change By: Melissa Stone Sprint: Coremunity Hopper Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9150 cwd option in Puppet::Util::Execution.execute should work with different Windows path types Change By: Sean McDonald Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9025) Filebucket resources fail when using server_list
Title: Message Title Melissa Stone commented on PUP-9025 Re: Filebucket resources fail when using server_list Okay, I tracked this a bit farther. My conclusion is that we should simply remove all references to `server_list` from the filebucket documentation and point all people to use `server`, if we decide filebucket should use `server` over `server_list` Though filebucket will fall back to using the first entry of `server_list` if server is explicitly set to an empty string, that happens as a part of the indirector logic, at https://github.com/puppetlabs/puppet/blob/cc4edbe4fce38406a97cfbd31751842a6b3e7cae/lib/puppet/indirector/request.rb#L181-L221 I realized that the issue this user was originally complaining about was that he didn't have server set to anything (thus it was set to the default of `puppet`), and expected filebucket to use `server_list`. The crux of this ticket is that puppet instead used the default of server, as we would expect, instead of `server_list`, which the user expected. That being said, there's now a behavior discrepancy here. The filebucket command prefers `server_list`, but the filebucket resource prefers `server`. What do we expect filebucket to prefer, `server` or `server_list`? Based on conversations with Branan Riley, it sounds like the only application that should be aware of `server_list` is agent, so we need to undo the changes introduced as a part of https://tickets.puppetlabs.com/browse/PUP-6823 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this
Jira (BOLT-920) Bolt unable to connect with ecdsa key
Title: Message Title Cas Donoghue commented on BOLT-920 Re: Bolt unable to connect with ecdsa key Verified ecdsa key works with 5.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-920) Bolt unable to connect with ecdsa key
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-920 Bolt unable to connect with ecdsa key Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)
Title: Message Title
John Meyers updated an issue
Puppet / PUP-9471
User management fails on MacOS 10.14 (Mojave)
Change By:
John Meyers
*Puppet Version: 4.10.6 and newer* *Puppet Server Version: N/A* *OS Name/Version: MacOS 10.14 (Mojave)*Apple has introduced new security functions in MacOS 10.14 (Mojave) that break Puppet's ability to manage users.To reproduce:Apply a puppet file that creates a 'user' with a given password hash on MacOS 10.13. Upgrade to MacOS 10.14. Apply the same puppet file - it will work without issue. Delete the user puppet created under 10.13 and re-apply the same puppet file to force Puppet to update the users data. Puppet will fail with a plethora of "Operation not permitted @ rb_sysopen" errors. Applying a 'TCC Profile' to the 10.14 system naming the Ruby interpreter used by Puppet does not help. *Desired Behavior: Puppet should be able to manage users in MacOS 10.14.**Actual Behavior: Puppet fails to change user data in MacOS 10.14 with "Operation not permitted"* Example:user { 'test': ensure => 'present', comment => 'Test', gid => '20', groups => ['_appserveradm', '_appserverusr', '_lpadmin', 'admin'], home => '/Users/test', iterations => '15898', password => 'somepassword', salt => 'somehash', shell => '/bin/bash', uid => '405', notify => Exec['Hide sub-500 users'], } puppet apply output:Error: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plistError: /Stage[main]/Main/Node[default]/User[test]/password: change from [old password hash redacted] to [new password hash redacted] failed: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plistError: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plistError: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plistError: /Stage[main]/Main/Node[default]/User[test]/iterations: change from 58823 to 15898 failed: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plist
Add Comment
Jira (BOLT-1107) plan executor should use the internal API to connect to orchestrator
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1107 plan executor should use the internal API to connect to orchestrator Change By: Nick Lewis Issue Type: Improvement Sub-task Parent: BOLT-986 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)
Title: Message Title
John Meyers updated an issue
Puppet / PUP-9471
User management fails on MacOS 10.14 (Mojave)
Change By:
John Meyers
*Puppet Version: 4.10.6 and newer* *Puppet Server Version: N/A* *OS Name/Version: MacOS 10.14 (Mojave)*Apple has introduced new security functions in MacOS 10.14 (Mojave) that break Puppet's ability to manage users.To reproduce:Apply a puppet file that creates a 'user' with a given password hash on MacOS 10.13. Upgrade to MacOS 10.14. Apply the same puppet file - it will work without issue. Delete the user puppet created under 10.13 and re-apply the same puppet file to force Puppet to update the users data. Puppet will fail with a plethora of "Operation not permitted @ rb_sysopen" errors. Applying a 'TCC Profile' to the 10.14 system naming the Ruby interpreter used by Puppet does not help. *Desired Behavior: Puppet should be able to manage users in MacOS 10.14.**Actual Behavior: Puppet fails to change user data in MacOS 10.14 with "Operation not permitted"* Example:user { 'test': ensure => 'present', comment => 'Test', gid => '20', groups => ['_appserveradm', '_appserverusr', '_lpadmin', 'admin'], home => '/Users/test', iterations => '15898', password => 'somepassword', salt => 'somehash', shell => '/bin/bash', uid => '405', notify => Exec['Hide sub-500 users'], } puppet apply output:Error: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plistError: /Stage[main]/Main/Node[default]/User[test]/password: change from [old password hash redacted] to [new password hash redacted] failed: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plistError: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plistError: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plistError: /Stage[main]/Main/Node[default]/User[test]/iterations: change from 58823 to 15898 failed: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/test.plist
Add Comment
Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)
Title: Message Title John Meyers created an issue Puppet / PUP-9471 User management fails on MacOS 10.14 (Mojave) Issue Type: Bug Assignee: Unassigned Created: 2019/02/01 10:52 AM Priority: Normal Reporter: John Meyers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (BOLT-1108) Add site-modules to the module path for bolt
Title: Message Title Nick Walker commented on BOLT-1108 Re: Add site-modules to the module path for bolt https://github.com/puppetlabs/control-repo/pull/71 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3284) PQL operators sometimes whitespace sensitive
Title: Message Title Austin Blatt commented on PDB-3284 Re: PQL operators sometimes whitespace sensitive Since this will be a breaking change, I have added a fix version of 7.0.0 and will put this in the backlog for now. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3284) PQL operators sometimes whitespace sensitive
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3284 PQL operators sometimes whitespace sensitive Change By: Austin Blatt Fix Version/s: PDB 7.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4256) Installing with PuppetDB module creates dependency cycle with latest apt module
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4256 Installing with PuppetDB module creates dependency cycle with latest apt module Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4256) Installing with PuppetDB module creates dependency cycle with latest apt module
Title: Message Title Austin Blatt commented on PDB-4256 Re: Installing with PuppetDB module creates dependency cycle with latest apt module It's fixed on our side too, thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4256) Installing with PuppetDB module creates dependency cycle with latest apt module
Title: Message Title Helen Campbell commented on PDB-4256 Re: Installing with PuppetDB module creates dependency cycle with latest apt module Hey everyone, I've made a fix which I was able to test out using Austins environment he provided (thanks Austin!). The release with the fix is now out and Postgresql 5.12.0 should work for you, would someone be able to confirm this and close out these tickets if so? Don't want to resolve anything until I know it's fixed on your side, thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9357) Noop exec debug logging should include the command
Title: Message Title
Eric Sorenson commented on PUP-9357
Re: Noop exec debug logging should include the command
Hm, so the code snippet would be
exec { 'example':
command => Sensitive.new('/bin/true'),
unless => Sensitive.new('/bin/false'),
}
Like Chris Roddy I don't have any evidence that people need this today but if it's easy to add, then sure, go for it.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
