Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Henrik Lindberg commented on PUP-10097 Re: Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent Sorry, Binary is pretty much not a working feature in catalogs/agents before Puppet 6. I doubt we will be able to backport all required fixes to Puppet 5. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328673.1570644934000.137682.1570690680186%40Atlassian.JIRA.
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title Jean Bond updated an issue Puppet / PUP-9754 Log resident configuration upon daemon launch Change By: Jean Bond Labels: resolved-issue-added 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312512.1560543853000.137513.1570664760394%40Atlassian.JIRA.
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Jean Bond updated an issue Puppet / PUP-6382 Add "Automatic (delayed start)" as option for Service Resource on Windows Change By: Jean Bond Labels: resolved-issue-added service type_and_provider windows 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.135151.1464896598000.137484.1570664220890%40Atlassian.JIRA.
Jira (PUP-9787) Unintentional secret reveal while installing modules
Title: Message Title Josh Cooper commented on PUP-9787 Re: Unintentional secret reveal while installing modules Yep just 6.10.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313276.1560984349000.137437.1570662840191%40Atlassian.JIRA.
Jira (PUP-9787) Unintentional secret reveal while installing modules
Title: Message Title Jean Bond commented on PUP-9787 Re: Unintentional secret reveal while installing modules Jorie Tappa, is this fix in 6.10.1 only, not in 6.4.4 or 5.5.17? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313276.1560984349000.137403.1570661940490%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Jean Bond updated an issue Puppet / PUP-10013 Update minitar version and call new fsync=false option Change By: Jean Bond Labels: resolved-issue-added 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323877.1567788493000.137393.1570661760248%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Vadym Chepkov commented on PUP-10097 Re: Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent I have enabled rich_data on both servers and agent, restarted puppetserver, receive new error: Error: Could not retrieve catalog from remote server: Could not intern from application/json: Internal Error: Puppet Context ':loaders' missing Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title Josh Cooper commented on PUP-10096 Re: Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions we all seem to agree is a bad idea and that this should be fixed at the source (in the function in question) To help with that, maybe we can warn if a function returns a ruby string with an ascii-8bit/binary encoding, so that module authors know to either force a non-binary encoding (when it can be determined based on the use case), or force the function to return a Binary puppet string and have it declare that using return_type? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328499.1570559378000.137226.1570657500233%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Henrik Lindberg commented on PUP-10097 Re: Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent Before 6 you had to configure both the agent and master with "rich_data=true" setting IIRC, and I think there was other issues as well that were addressed in Puppet 6 where rich data catalog is now both the default and is negotiated between agent and master. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328673.1570644934000.137188.1570656660270%40Atlassian.JIRA.
Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title Henrik Lindberg commented on PUP-10096 Re: Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions Reinhard Vicinus thanks for all the detective work on this and the detailed reports. It really helps! It would be great to file another PUP ticket for the String new with / without %s - both of them should result in an UTF-8 encoded String as that is expected of all strings in the puppet language. The PDB issue is also a separate issue - please file a ticket for that - it basically means it is not possible to roundtrip (export/import) rich data (which is sad). That leaves some kind of "auto convert" feature - which we all seem to agree is a bad idea and that this should be fixed at the source (in the function in question). So I am ok with closing this - maybe Josh Cooper wants something different. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328499.1570559378000.137073.1570654560645%40Atlassian.JIRA.
Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title
Reinhard Vicinus commented on PUP-10096
Re: Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Henrik Lindberg Ok, the reason why the value was not binary encoded in the catalog on the node is that there is still a puppet 5 agent running. With a puppet 6 agent the value is binary encoded. This is a case were afterwards I am asking myself why I spend hours debugging the puppetserver/puppetdb part and did not try what happened if I updated the puppet agent on the node... I'll change the ruby function as suggested by Josh Cooper: Thanks for looking up the correct way to encode DNS domain names. But I tested some things and I found a further problem: The puppetdb does not store, that the value was binary encoded. So if you export a resource with a binary string value and import it on another node the value is base64 encoded, because in the puppetdb postgresql database is no information stored, that the value was binary in the catalog and only the base64 value is stored:
$v = rdnslookup('8.8.8.8')
case $::fqdn {
'node1': {
@@file { $v:
path => '/tmp/test.txt',
content => $v,
}
}
'node2': {
Fi
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Garrett Guillotte commented on PUP-10097 Re: Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent Confirmed that I cannot reproduce on 6.4.3 / PE 2019.1.1. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328673.1570644934000.136643.1570647240286%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Garrett Guillotte commented on PUP-10097 Re: Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent This might be a duplicate of PUP-9110 / PUP-3600. If so, the inability to handle Binary type data in catalogs should be noted as a known issue in Puppet 5.5 that is resolved in Puppet 6. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328673.1570644934000.136632.1570646760151%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-10097 Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent Change By: Garrett Guillotte Zendesk Ticket IDs: 36615 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328673.1570644934000.136600.1570646460299%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title
Garrett Guillotte updated an issue
Puppet / PUP-10097
Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Change By:
Garrett Guillotte
*Puppet Version:* 5.5.16*Puppet Server Version:* PE 2018.1.9*OS Name/Version:* RHEL 7.6*Desired Behavior:*{{puppet agent}} can manage the contents of a {{file}} resource that uses a {{Binary}} type for its contents, with behavior consistent with {{puppet apply}} running the same manifest.*Actual Behavior:*Attempting to write binary file content represented in hex as {{c7 d1 fc 84}}, converted to base64 and passed as {{Binary('x9H8hA==')}}, editing {{/etc/puppetlabs/code/environments/production/manifests/site.pp}}:{code}[root@pe-201819-master manifests]# cat site.pp## site.pp ### This file (/etc/puppetlabs/puppet/manifests/site.pp) is the main entry point...node default { # This is where you can declare classes for all nodes. # Example: # class { 'my_class': } file { '/tmp/test':ensure => present,content => Binary('x9H8hA=='), }}[root@pe-201819-master manifests]# puppet apply site.ppNotice: Compiled catalog for pe-201819-master.puppetdebug.vlan in environment production in 0.02 secondsNotice: /Stage[main]/Main/Node[default]/File[/tmp/test]/ensure: defined content as '{md5}387d16f3cb61048e6fb16cfd81367ce8'Notice: Applied catalog in 0.20 seconds[root@pe-201819-master manifests]# od -t x1 /tmp/test000 c7 d1 fc 84004{code}This is the expected result of applying the manifest. {{puppet apply}} works as expected.Running as {{puppet agent}} fails:{code}[root@pe-201819-master manifests]# puppet agent --testInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Retrieving localesInfo: Loading factsInfo: Caching catalog for pe-201819-master.puppetdebug.vlanInfo: Applying configuration version '1570644420'Notice: /Stage[main]/Main/Node[default]/File[/tmp/test]/content: Received a Log attribute with invalid encoding:"\n--- /tmp/test\t2019-10-09 18:06:34.850138853 +\n+++ /tmp/puppet-file20191009-20057-12z3c2w\t2019-10-09 18:07:15.397076080 +\n@@ -1 +1 @@\n-\xC7\xD1\xFC\x84\n\\ No newline at end of file\n+x9H8hA==\n\\ No newline at end of file\n"\nBacktrace:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:190:in `newmessage'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:313:in `initialize'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:88:in `new'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:88:in `create'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/logging.rb:11:in `send_log'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/logging.rb:20:in `block (2 levels) in '/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/data_sync.rb:45:in `block in checksum_insync?'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/data_sync.rb:19:in `write_temporarily'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/data_sync.rb:44:in `checksum_in
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4502 PuppetDB command size metrics are missing Change By: Austin Blatt Fix Version/s: PDB 6.8.0 Fix Version/s: PDB 6.7.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323996.156781861.136515.1570645560803%40Atlassian.JIRA.
Jira (PDB-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4513 puppetserver fails to connect to puppetdb 6.6.0 Change By: Austin Blatt Release Notes Summary: PuppetDB 6.6.0 was released with a restricted set of cipher suites that could prevent connecting to Puppet Server on using TLSv1.0 and TLSv1.1. This restores the cipher suites required to connect to Puppet Server on those older TLS versions. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326149.1569370509000.136488.1570645021604%40Atlassian.JIRA.
Jira (PDB-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4513 puppetserver fails to connect to puppetdb 6.6.0 Change By: Austin Blatt Release Notes Summary: PuppetDB 6. 5 6 .0 was released with a restricted set of cipher suites that could prevent connecting to Puppet Server on TLSv1.0 and TLSv1.1. This restores the cipher suites required to connect to Puppet Server on those older TLS versions. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326149.1569370509000.136475.1570645021546%40Atlassian.JIRA.
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title
Garrett Guillotte updated an issue
Puppet / PUP-10097
Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Change By:
Garrett Guillotte
*Puppet Version:* 5.5.16*Puppet Server Version:* PE 2018.1.9*OS Name/Version:* RHEL 7.6*Desired Behavior:*{{puppet agent}} can manage the contents of a {{file}} resource that uses a {{Binary}} type for its contents, with behavior consistent with {{puppet apply}} running the same manifest.*Actual Behavior:*Attempting to write binary file content represented in hex as {{c7 d1 fc 84}}, converted to base64 and passed as {{Binary('x9H8hA==')}}, editing {{/etc/puppetlabs/code/environments/production/manifests/site.pp}}:{code}[root@pe-201819-master manifests]# cat site.pp## site.pp ### This file (/etc/puppetlabs/puppet/manifests/site.pp) is the main entry point...node default { # This is where you can declare classes for all nodes. # Example: # class { 'my_class': } file { '/tmp/test':ensure => present,content => Binary('x9H8hA=='), }}[root@pe-201819-master manifests]# puppet apply site.ppNotice: Compiled catalog for pe-201819-master.puppetdebug.vlan in environment production in 0.02 secondsNotice: /Stage[main]/Main/Node[default]/File[/tmp/test]/ensure: defined content as '{md5}387d16f3cb61048e6fb16cfd81367ce8'Notice: Applied catalog in 0.20 seconds[root@pe-201819-master manifests]# od -t x1 /tmp/test000 c7 d1 fc 84004{code}This is the expected result of applying the manifest. {{puppet apply}} works as expected.Running as {{puppet agent}} fails:{code}[root@pe-201819-master manifests]# puppet agent --testInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Retrieving localesInfo: Loading factsInfo: Caching catalog for pe-201819-master.puppetdebug.vlanInfo: Applying configuration version '1570644420'Notice: /Stage[main]/Main/Node[default]/File[/tmp/test]/content: Received a Log attribute with invalid encoding:"\n--- /tmp/test\t2019-10-09 18:06:34.850138853 +\n+++ /tmp/puppet-file20191009-20057-12z3c2w\t2019-10-09 18:07:15.397076080 +\n@@ -1 +1 @@\n-\xC7\xD1\xFC\x84\n\\ No newline at end of file\n+x9H8hA==\n\\ No newline at end of file\n"\nBacktrace:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:190:in `newmessage'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:313:in `initialize'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:88:in `new'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:88:in `create'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/logging.rb:11:in `send_log'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/logging.rb:20:in `block (2 levels) in '/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/data_sync.rb:45:in `block in checksum_insync?'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/data_sync.rb:19:in `write_temporarily'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/data_sync.rb:44:in `checksum_in
Jira (PUP-10097) Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Title: Message Title
Garrett Guillotte created an issue
Puppet / PUP-10097
Using Binary type as a File resource's contents works in puppet apply, but not in puppet agent
Issue Type:
Bug
Affects Versions:
PUP 5.5.16
Assignee:
Unassigned
Created:
2019/10/09 11:15 AM
Priority:
Normal
Reporter:
Garrett Guillotte
Puppet Version: 5.5.16 Puppet Server Version: PE 2018.1.9 OS Name/Version: RHEL 7.6 Desired Behavior: puppet agent can manage the contents of a file resource that uses a Binary type for its contents, with behavior consistent with puppet apply running the same manifest. Actual Behavior: Attempting to write binary file content represented in hex as c7 d1 fc 84, converted to base64 and passed as Binary('x9H8hA=='), editing /etc/puppetlabs/code/environments/production/manifests/site.pp:
[root@pe-201819-master manifests]# cat site.pp
## site.pp ##
# This file (/etc/puppetlabs/puppet/manifests/site.pp) is the main entry point
Jira (PUP-10096) Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions
Title: Message Title Josh Cooper commented on PUP-10096 Re: Parameters of resources are base64 encoded in puppetdb if created as raw byte strings by ruby functions From https://en.wikipedia.org/wiki/Punycode: While the Domain Name System (DNS) technically supports arbitrary sequences of octets in domain name labels, the DNS standards recommend the use of the LDH subset of ASCII conventionally used for host names, and require that string comparisons between DNS domain names should be case-insensitive. Given that I'd recommend coercing the name as US-ASCII not UTF-8: result = Resolv.new.getname(args[0]) result.force_encoding(Encoding::US_ASCII) result.scrub! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10028) yumrepo misses support for minrate
Title: Message Title Josh Cooper commented on PUP-10028 Re: yumrepo misses support for minrate Merged to master in https://github.com/puppetlabs/puppetlabs-yumrepo_core/commit/e4c204354e6e37d44e0cc6a9507c6e99fcfd2834 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325379.1568897737000.136267.1570641360350%40Atlassian.JIRA.
Jira (PDB-4506) Don't hang on C-c during migration
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4506 Don't hang on C-c during migration Change By: Rob Browning Assignee: Rob Browning 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324995.156873961.136024.1570635421786%40Atlassian.JIRA.
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title Josh Cooper commented on PUP-9295 Re: Notify resource exposes Sensitive data when message is a Sensitive data Passed CI in 36c35404b8474b5949c87c49e0b360d426b64cbb 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.283215.1540998541000.135961.1570634702023%40Atlassian.JIRA.
Jira (FACT-2055) Facter fails if its working directory does not exist
Title: Message Title John Bollinger commented on FACT-2055 Re: Facter fails if its working directory does not exist I'm not sure about the "great many" Unix utilities that fail if the working directory is unlinked, James Ralston. Of the several that I selected for testing on a CentOS 7 system, the only one that failed was Bash, and even Bash ran successfully (albeit after emitting a warning) when launched as /bin/sh – both interactively and non-interactively. No other that I tested even warned. Ruby (irb), Python, and Perl were all ok. Sed was ok. /bin/cat was ok. Even /bin/ls with no arguments just silently emitted a completely empty listing. Thus, no, I don't think it's reasonable to characterize this as a Unix feature. Moreover, since I can't come up with anything that the Facter core ought to be doing that would require working-directory access, yes, it is a bug in Facter. Whether it is a bug that should be fixed is a different question. I know I can come up with scenarios where the faulty behavior is a genuine real-world problem, but it remains to be seen how contrived they would end up being. I am imagining applications in highly dynamic environments where "don't do that" is not a viable alternative. Nevertheless, I discovered this issue while trying to reproduce and characterize the inaccessible working directory case originally reported in PUP-10080. My own uses of Puppet do not ordinarily run into the unlinked working directory 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 th
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title John Bollinger commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible For the record, I'm fine with this resolution. I agree that my example 1 is among the cases covered by PUP-9997, but not necessarily the only such case. My example #2 has already been reassigned to FACT-2055. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.135863.1570627980142%40Atlassian.JIRA.
Jira (PUP-10021) User resource always reports password changed when account disabled for Win 2012 R2
Title: Message Title Dorin Pleava commented on PUP-10021 Re: User resource always reports password changed when account disabled for Win 2012 R2 After some debugging, found the following: puppet does not change the password of a disabled account even though it reports so [disable check|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/user/windows_adsi.rb#L126]. the ending notice that reports a change in passwords is only shown when the password is wrong ([password check |https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/user.rb#L72]), and this triggers the sync mechanism windows allows password changes of a disabled account, I think that this is also true for locked out/expired users I debugged and testing this on windows 2012r2. If windows supports password changes of disabled user, shouldn't puppet also change the password and display a notice/warning that the user is disabled? This way the command will become idempotent, and the ending notice will be true. Should I continue using this logic, or just try to remove the password change notice in case of a disabled user? 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 fro
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title George Mrejea commented on PUP-9295 Re: Notify resource exposes Sensitive data when message is a Sensitive data I believe this can be closed since the commit was promoted and tested in master. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.283215.1540998541000.135778.1570622340434%40Atlassian.JIRA.
Jira (FACT-2060) Windows: Add the scope of found ipv6 addresses (global/linklocal/...) as a fact
Title: Message Title Karsten Heymann created an issue Facter / FACT-2060 Windows: Add the scope of found ipv6 addresses (global/linklocal/...) as a fact Issue Type: Improvement Assignee: Ciprian Badescu Created: 2019/10/09 3:48 AM Priority: Minor Reporter: Karsten Heymann Puppet Version: any Puppet Server Version: any OS Name/Version: any For certain configuration tasks, it is important to know not only if a host has an IPv6 address (networking.ip6 is not empty), but also if that address is a globally routable address or a link-local address. Desired Behavior: **facter returns the scope for the ip6 address it finds: $ facter -p networking.ip6 2001:4860:4860:: $ facter -p networking.ip6_scope global $ facter -p networking.ip6 fe80::a800:ff:fe63:14d5
