Jira (PUP-8365) Zone creation acceptance tests fail on Solaris 11 SPARC after failed package downloads

2018-01-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-8365 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Zone creation acceptance tests fail on Solaris 11 SPARC after failed package downloads  
 
 
 
 
 
 
 
 
 
 
More failures https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/Public%20Suites/view/5.3.x/view/Suite/job/platform_puppet-agent_puppet-agent-integration-suite_daily-5.3.x/78/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

2018-01-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8337 
 
 
 
  Package source on Windows errors out on deduped installation files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Fix Version/s:
 
 PUP 5.3.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8337) Package source on Windows errors out on deduped installation files

2018-01-22 Thread Michael Lombardi (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Lombardi updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8337 
 
 
 
  Package source on Windows errors out on deduped installation files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Lombardi 
 
 
 

Attachment:
 
 irb.logs 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8368) Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server

2018-01-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-8368 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server  
 
 
 
 
 
 
 
 
 
 
This is a smaller reproduction, which more closely matches the agent behavior where the format string is a valid "UTF-8" encoded string: 
 
 
 
 
 
 
# coding: utf-8 
 
 
 
 
require 'socket' 
 
 
 
 
begin 
 
 
 
 
  TCPSocket.open('nowhere', 80) 
 
 
 
 
rescue => e 
 
 
 
 
  puts "証明書をリクエストできませんでした: %s" % e.message 
 
 
 
 
end
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

Jira (PUP-8368) Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server

2018-01-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-8368 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server  
 
 
 
 
 
 
 
 
 
 
I can reproduce the problem using just ruby on non-Windows platforms. It appears ruby will barf if given a non-ascii *format* string and an ASCII_8BIT encoded argument string.  
 
 
 
 
 
 
# coding: cp932 
 
 
 
 
# 
 
 
 
 
# TCP.connect raises an exception whose message is ASCII_8BIT 
 
 
 
 
message = "Failed to open TCP connection to nowhere (getaddrinfo: そのようなホストは不明です。 )" 
 
 
 
 
message.force_encoding(Encoding::ASCII_8BIT) 
 
 
 
 
puts "Error: %{message}" % {message: message} 
 
 
 
 
  
 
 
 
 
# this doesn't 
 
 
 
 
begin 
 
 
 
 
  puts "証明書をリクエストできませんでした: %s" % message 
 
   

Jira (PUP-8337) Package source on Windows errors out on deduped installation files

2018-01-22 Thread Michael Lombardi (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Lombardi commented on  PUP-8337 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Package source on Windows errors out on deduped installation files  
 
 
 
 
 
 
 
 
 
 
Manually validated the fix with Glenn Sarti and Ethan Brown by: 
+ spinning up a Windows Server 2016 VM + enabling dedupe on the Z:\ drive + copying several instances of choco.exe to the Z:\ drive + Running a manual Dedupe job + Verifying that Puppet::Util::Windows::File.symlink? returns false for deduped files + Verifying that Puppet::Util::Windows::File.reparse_point? returns true for deduped files + Verifying that Puppet::Util::Windows::File.symlink_reparse_point? returns false for deduped files. + Verifying that Puppet Resource File on a deduped file fails on 4.10.x but succeeds with the fixed code + Verifying that we can point a Package resource at a deduped file successfully with the fixed code. 
See the irb.log, the example.pp, and the manual-validation.txt logs for detailed output. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

2018-01-22 Thread Michael Lombardi (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Lombardi updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8337 
 
 
 
  Package source on Windows errors out on deduped installation files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Lombardi 
 
 
 

Attachment:
 
 Manual-Validation.txt 
 
 
 

Attachment:
 
 Example.pp 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8365) Zone creation acceptance tests fail on Solaris 11 SPARC after failed package downloads

2018-01-22 Thread Casey Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey Williams commented on  PUP-8365 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Zone creation acceptance tests fail on Solaris 11 SPARC after failed package downloads  
 
 
 
 
 
 
 
 
 
 
CI is still red on this cell - RE-10060 has been filed to see if mirroring the Solaris repos will help us here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-311) Error from run_task plan causes uncaught exception

2018-01-22 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-311 
 
 
 
  Error from run_task plan causes uncaught exception  
 
 
 
 
 
 
 
 
 

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-277) SSL default makes winrm harder to use

2018-01-22 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-277 
 
 
 
  SSL default makes winrm harder to use  
 
 
 
 
 
 
 
 
 

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 (PUP-8368) Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server

2018-01-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8368 
 
 
 
  Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 
 
 
 
 
 
 
 On a Windows Japanese box if you run 'puppet agent -t  -- sever server  no_such_host' the agent prints errors about incompatible encodings:{code}$ puppet.bat agent -t --server no_such_hostWarning: ノード定義を取得できませんが、agent実行を続行します:Warning: Failed to open TCP connection to no_such_host:8140 (getaddrinfo: そのようなホストは不明です。 )Info: pluginfactsを取得しています。Warning: detail.class: SocketErrorWarning: detail.to_s.encoding: ASCII-8BITError: カタログ適用に失敗しました: incompatible character encodings: UTF-8 and ASCII-8BITError: Puppet設定クライアントを実行できません: incompatible character encodings: UTF-8 and ASCII-8BIT{code}The underlying issue appears to be when an error has be rescued, and as the error string is ASCII-8BIT and the formatting of the string blows up:{code}  def eval_generate(resource)return false unless resource.respond_to?(:eval_generate)raise Puppet::DevError, _("Depthfirst resources are not supported by eval_generate") if resource.depthfirst?begin  generated = replace_duplicates_with_catalog_resources(resource.eval_generate)  return false if generated.empty?rescue => detail  @resources_failed_to_generate = true  #TRANSLATORS eval_generate is a method name and should be left untranslated  resource.log_exception(detail, _("Failed to generate additional resources using 'eval_generate': %{detail}") % { detail: detail }){code}If you print out the class and string encoding value:{code}Warning: detail.class: SocketErrorWarning: detail.to_s: Failed to open TCP connection to no_such_host:8140 (getaddrinfo: そのようなホストは不明です。 )Warning: detail.to_s.encoding: ASCII-8BIT{code}Here is the stack trace:{code}C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/2.4.0/gems/fast_gettext-1.1.1/lib/fast_gettext/vendor/string.rb:70:in `%'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/2.4.0/gems/fast_gettext-1.1.1/lib/fast_gettext/vendor/string.rb:70:in `%'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/additional_resource_generator.rb:64:in `rescue in eval_generate'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/additional_resource_generator.rb:55:in `eval_generate'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:112:in `block in evaluate'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:119:in `traverse'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:169:in `evaluate'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:231:in `block in apply'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/log.rb:160:in `with_destination'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/report.rb:144:in `as_logging_destination'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:230:in `apply'C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer/downloader.rb:13:in `evaluate'C:/Program 

Jira (BOLT-312) Improve plan acceptance tests

2018-01-22 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-312 
 
 
 
  Improve plan acceptance tests  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Key:
 
 PCP BOLT - 827 312 
 
 
 

Project:
 
 Puppet  Communications Protocol  Task Runner 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7164) The yaml_data function used by lookup should return empty hash for empty yaml files

2018-01-22 Thread BellaX (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 BellaX commented on  PUP-7164 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The yaml_data function used by lookup should return empty hash for empty yaml files  
 
 
 
 
 
 
 
 
 
 
Hi Henrik Lindberg, is it same fix to the error of Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Function lookup() did not find a value for the name 'profile::webserver_lnp::logrotate_rules' on node ***? I didn't specify any key 'profile::webserver_lnp::logrotate_rules' yet in any yaml file, I just wanted to see how it would behave if the key does not exist. In the manifest file, I did: $real_logrotate_rules = deep_merge($logrotate_rules, lookup('profile::webserver_lnp::logrotate_rules',  {merge => 'deep'} 
)) however, when I replacing "lookup" with "hiera_hash", it did not throw error.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8369) test direct_puppet/supports_utf8.rb is always skipped

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8369 
 
 
 
  test direct_puppet/supports_utf8.rb is always skipped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Fix Version/s:
 
 PUP 5.4.0 
 
 
 

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-8252) re-enable i18n test after translation updated for 5.3.4 release

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8252 
 
 
 
  re-enable i18n test after translation updated for 5.3.4 release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

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-8252) re-enable i18n test after translation updated for 5.3.4 release

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney assigned an issue to Eric Delaney 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8252 
 
 
 
  re-enable i18n test after translation updated for 5.3.4 release  
 
 
 
 
 
 
 
 
 

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-5426) config set ignores --section and can insert duplicate settings if they are in [main]

2018-01-22 Thread Jacob Helwig (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Helwig commented on  PUP-5426 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: config set ignores --section and can insert duplicate settings if they are in [main]  
 
 
 
 
 
 
 
 
 
 
So, the reason the order of the settings in the [agent] section matters, is that our IniFile implementation is trying to add the new environment setting after the last line in the [agent] section, but is unable to tell the difference between the server line in [main], and the one in [agent] as it's only keying off of the setting's name & values. When the certname setting is last, it's unique, so adding the new line doesn't get confused about which instance to add environment after. 
So, this bug has the general form of: If a setting would be inserted after an existing setting that has the same value as one in a previous section (according to line number) in puppet.conf, the new setting will be inserted after the first occurrence of the name/value, instead of the one in the desired section. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-8353) Investigate: Some of the node termini are not calling fact_merge (facts may not be accessible through a manifest when using these termini)

2018-01-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8353 
 
 
 
  Investigate: Some of the node termini are not calling fact_merge (facts may not be accessible through a manifest when using these termini)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Team:
 
 Platform Core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8248) Make systemd the default service provider for Amazon Linux 2017.12

2018-01-22 Thread Scott Garman (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Garman commented on  PUP-8248 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make systemd the default service provider for Amazon Linux 2017.12  
 
 
 
 
 
 
 
 
 
 
Merged to 4.10.x at https://github.com/puppetlabs/puppet/commit/49fb94be71fe4ff447d1cc521c2d1095787fb973 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8080) Puppet i18n with Modules: Add basic modules tests

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney commented on  PUP-8080 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet i18n with Modules: Add basic modules tests  
 
 
 
 
 
 
 
 
 
 
Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/ba960b4a91c0388beb0c1be231b7a03cb256cc7e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5426) config set ignores --section and can insert duplicate settings if they are in [main]

2018-01-22 Thread Jacob Helwig (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Helwig updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5426 
 
 
 
  config set ignores --section and can insert duplicate settings if they are in [main]  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jacob Helwig 
 
 
 

Sprint:
 
 Platform Core  Hopper  KANBAN 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5426) config set ignores --section and can insert duplicate settings if they are in [main]

2018-01-22 Thread Jacob Helwig (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Helwig assigned an issue to Jacob Helwig 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5426 
 
 
 
  config set ignores --section and can insert duplicate settings if they are in [main]  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jacob Helwig 
 
 
 

Assignee:
 
 Jacob Helwig 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-277) SSL default makes winrm harder to use

2018-01-22 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-277 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SSL default makes winrm harder to use  
 
 
 
 
 
 
 
 
 
 
I see new messaging when a user runs a task. 
 
 
 
 
 
 
Started on sjgst1q2206djv5.delivery.puppetlabs.net... 
 
 
 
 
Failed on sjgst1q2206djv5.delivery.puppetlabs.net: 
 
 
 
 
  Timeout after 10 seconds connecting to https://sjgst1q2206djv5.delivery.puppetlabs.net:5986/wsman 
 
 
 
 
  Use --insecure if this host isn't configured to use SSL for WinRM
 
 
 
 
 
 
 
However I don't see any messaging when a task is run through a plan 
 
 
 
 
 
 
2018-01-22T12:43:38.273348 INFO   Bolt::Executor: Starting task /tmp/C100554.5fjVHH/modules/test/tasks/a_win.ps1 on ["winrm://sjgst1q2206djv5.delivery.puppetlabs.net"] 
 
 
 
 
2018-01-22T12:43:48.278445 INFO   Bolt::Executor: Ran task '/tmp/C100554.5fjVHH/modules/test/tasks/a_win.ps1' on 1 node with 1 failure 
 
 
 
 
Evaluation Error: Error while evaluating a Function Call, Plan aborted: run_task 'test::a_win' failed on 1 nodes at /tmp/C100554.5fjVHH/modules/test/plans/my_win_plan.pp:3:17
 
 
 
 
 
 

Jira (PUP-8368) Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server

2018-01-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to Josh Cooper 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8368 
 
 
 
  Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 Josh Cooper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8334) i18n add string decorations to Puppet::Util::Windows::Error usage

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8334 
 
 
 
  i18n add string decorations to Puppet::Util::Windows::Error usage  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Sprint:
 
 Platform Core  Hopper  Grooming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-120) Bolt doesn't work with IPv6 addresses

2018-01-22 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  BOLT-120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bolt doesn't work with IPv6 addresses  
 
 
 
 
 
 
 
 
 
 
At this point I believe the behavior is acceptable. I'd suggest we document it and resolve this issue. 
Documentation would highlight that IPv6 addresses can be passed as fe80::34eb:ff1:b584:d7c0:22 or [fe80::34eb:ff1:b584:d7c0]:22. If a port is not included, then square brackets must be used, i.e. [fe80::34eb:ff1:b584:d7c0]. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3812) puppetdb low catalog duplication page 404s

2018-01-22 Thread Christopher Wood (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Wood commented on  PDB-3812 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb low catalog duplication page 404s  
 
 
 
 
 
 
 
 
 
 
It was quite a useful page, was there a substitute somewhere else in the puppetdb 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-102) Loading params from file on powershell triggers splat operator error

2018-01-22 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-102 
 
 
 
  Loading params from file on powershell triggers splat operator error  
 
 
 
 
 
 
 
 
 

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-102) Loading params from file on powershell triggers splat operator error

2018-01-22 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  BOLT-102 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Loading params from file on powershell triggers splat operator error  
 
 
 
 
 
 
 
 
 
 
I suggest we document that single quote is needed to use it under powershell and resolve this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-120) Bolt doesn't work with IPv6 addresses

2018-01-22 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-120 
 
 
 
  Bolt doesn't work with IPv6 addresses  
 
 
 
 
 
 
 
 
 

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 (PDB-3812) puppetdb low catalog duplication page 404s

2018-01-22 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  PDB-3812 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb low catalog duplication page 404s  
 
 
 
 
 
 
 
 
 
 
I took a look - it seems like the file has been removed from 5.1, but not removed from the sidebar nav. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3812) puppetdb low catalog duplication page 404s

2018-01-22 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette assigned an issue to Russell Mull 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3812 
 
 
 
  puppetdb low catalog duplication page 404s  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Assignee:
 
 Russell Mull 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3812) puppetdb low catalog duplication page 404s

2018-01-22 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3812 
 
 
 
  puppetdb low catalog duplication page 404s  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Method Found:
 
 Needs Assessment 
 
 
 

Component/s:
 
 PuppetDB 
 
 
 

Component/s:
 
 PuppetDB 
 
 
 

Workflow:
 
 Documentation Scrum Team  Workflow 
 
 
 

Key:
 
 DOCUMENT PDB - 801 3812 
 
 
 

Project:
 
 Documentation PuppetDB 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
  

Jira (BOLT-311) Error from run_task plan causes uncaught exception

2018-01-22 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-311 
 
 
 
  Error from run_task plan causes uncaught exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Release Notes Summary:
 
 Details of some exceptions generated within plans will be lost when using Ruby 2.0. 
 
 
 

Release Notes:
 
 Known Issue 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8369) test direct_puppet/supports_utf8.rb is always skipped

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8369 
 
 
 
  test direct_puppet/supports_utf8.rb is always skipped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Fix Version/s:
 
 PUP 5.3.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8369) test direct_puppet/supports_utf8.rb is always skipped

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8369 
 
 
 
  test direct_puppet/supports_utf8.rb is always skipped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Affects Version/s:
 
 PUP 4.10.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8013) Translations should be stored in different text domains based on environment

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8013 
 
 
 
  Translations should be stored in different text domains based on environment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Affects Version/s:
 
 PUP 5.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3811) PDB 5.0 docs incorrectly list support for java7

2018-01-22 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3811 
 
 
 
  PDB 5.0 docs incorrectly list support for java7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Workflow:
 
 Documentation Scrum Team  Workflow 
 
 
 

Key:
 
 DOC PDB - 3455 3811 
 
 
 

Project:
 
 Documentation [Internal] PuppetDB 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8288 
 
 
 
  Exceptions during transaction evaluate reported as success  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Affects Version/s:
 
 PUP 5.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8288 
 
 
 
  Exceptions during transaction evaluate reported as success  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Fix Version/s:
 
 PUP 5.4.0 
 
 
 

Fix Version/s:
 
 PUP 5.3.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8249 
 
 
 
  Certain environments return "invalid byte sequence in " when parsing module PO files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

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-8314) i18n add string decorations to "raise ArgumentError" call

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8314 
 
 
 
  i18n add string decorations to "raise ArgumentError" call  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Release Notes:
 
 Not Needed Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8314) i18n add string decorations to "raise ArgumentError" call

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8314 
 
 
 
  i18n add string decorations to "raise ArgumentError" call  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Release Notes Summary:
 
 More warning, and error messages have been set up to be translated when Puppet is run under the Japanese locale 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8312 
 
 
 
  i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Release Notes Summary:
 
 For the release more warnings More warning , and  errors message will  error messages have been set up to  be translated when Puppet is run under the Japanese locale 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1810) 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata

2018-01-22 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1810 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata  
 
 
 
 
 
 
 
 
 
 
If you git clone https://github.com/puppetlabs/facter -b 2.x, you can run from source with 
 
 
 
 
 
 
cd facter 
 
 
 
 
gem install bundler 
 
 
 
 
bundle install --path=.bundle/gems 
 
 
 
 
bundle exec facter
 
 
 
 
 
 
 
You need to have Ruby 1.8.7+ with rubygems installed (it comes with most versions of Ruby and provides the gem command, but may be a separate package on some older platforms). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 

Jira (PUP-8288) Exceptions during transaction evaluate reported as success

2018-01-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes assigned an issue to Eric Delaney 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8288 
 
 
 
  Exceptions during transaction evaluate reported as success  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

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-8312) i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings

2018-01-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8312 
 
 
 
  i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Release Notes Summary:
 
 For the release more warnings, and errors message will be translated when Puppet is run under the Japanese locale 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8373) Lookup CLI should use RBAC token if available for PuppetDB

2018-01-22 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-8373 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Lookup CLI should use RBAC token if available for PuppetDB  
 
 
 
 
 
 
 
 
 
 
That makes sense. Bolt has gone with config-file only for now, as outlined in https://github.com/puppetlabs/bolt/#pcp-transport-configuration-options. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8376) Revert to production when agent-specified environment doesn't exist

2018-01-22 Thread Gene Liverman (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gene Liverman commented on  PUP-8376 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Revert to production when agent-specified environment doesn't exist  
 
 
 
 
 
 
 
 
 
 
I will let Daniel Parks answer your specific question Henrik Lindberg but, before coming to Puppet, we used FOSS puppet in a master-based environment and the inability for an agent to deal with its environment not existing caused us much pain. We did all of our work on our control repo and internal modules via the Git Flow workflow which is much the same as previously described. More than once we missed the step of moving a node back to production before deleting the branch and ended up having to connect directly to that node and manually change its branch back.
  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-303) Unable to connect over winrm HTTP with bolt task, but works with bolt command

2018-01-22 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-303 
 
 
 
  Unable to connect over winrm HTTP with bolt task, but works with bolt command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Sprint:
 
 Bolt  Ready for Grooming  Kanban 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files

2018-01-22 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8249 
 
 
 
  Certain environments return "invalid byte sequence in " when parsing module PO files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Release Notes Summary:
 
 Puppet will no longer have difficulty parsing module translation files in non-UTF-8 environments. 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8025) `puppet module install` does not correctly install locale files

2018-01-22 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8025 
 
 
 
  `puppet module install` does not correctly install locale files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Fix Version/s:
 
 PUP 5.3.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1810) 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata

2018-01-22 Thread Jan Willem (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Willem commented on  FACT-1810 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata  
 
 
 
 
 
 
 
 
 
 
I'm trying to find out at which version (or ideally at which commit) this problem manifests itself, but I can't make sense out of this rbenv/rvm/.. stuff. Is there a way to install it just from the sources that I can download from here https://github.com/puppetlabs/facter/releases?after=3.7.1, for the local user? ruby newbee signing off  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml

2018-01-22 Thread Pieter Loubser (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pieter Loubser updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8227 
 
 
 
  Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pieter Loubser 
 
 
 

Release Notes Summary:
 
 Running "puppet apply" or "puppet resource" to modify state would update the transaction.yaml file used to determine corrective vs intentional change. The transaction.yaml file will now only be updated during an agent run. 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3738) Reports sync summary query is very slow

2018-01-22 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3738 
 
 
 
  Reports sync summary query is very slow  
 
 
 
 
 
 
 
 
 
 
Russell Mull please add release notes for this issue, if needed. Thanks! 
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Team:
 
 Data Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml

2018-01-22 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-8227 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml  
 
 
 
 
 
 
 
 
 
 
Pieter Loubser please add release notes for this issue, if needed. Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files

2018-01-22 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-8249 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Certain environments return "invalid byte sequence in " when parsing module PO files  
 
 
 
 
 
 
 
 
 
 
Maggie Dreyer please add release notes for this issue, if needed. Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8312) i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings

2018-01-22 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-8312 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings  
 
 
 
 
 
 
 
 
 
 
Eric Delaney please add release notes for this issue, if needed. Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8025) `puppet module install` does not correctly install locale files

2018-01-22 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-8025 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: `puppet module install` does not correctly install locale files  
 
 
 
 
 
 
 
 
 
 
Maggie Dreyer please add release notes for this issue, if needed. Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8375) Amazon Linux v2 detection is broken (os.version is 2.0, not 2017.12)

2018-01-22 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8375 
 
 
 
  Amazon Linux v2 detection is broken (os.version is 2.0, not 2017.12)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Fix Version/s:
 
 PUP 5.4.0 
 
 
 

Fix Version/s:
 
 PUP 5.3.4 
 
 
 

Fix Version/s:
 
 PUP 4.10.10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8370) puppet runs generate a misleading error when hiera-eyaml is configured but not installed

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-8370 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet runs generate a misleading error when hiera-eyaml is configured but not installed  
 
 
 
 
 
 
 
 
 
 
The wrapping of the message could be improved. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8370) puppet runs generate a misleading error when hiera-eyaml is configured but not installed

2018-01-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-8370 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet runs generate a misleading error when hiera-eyaml is configured but not installed  
 
 
 
 
 
 
 
 
 
 
The "on the server" is also not correct if this is when you are doing an apply - it needs to be where the compiler is compiling. The best would be if it could say concretely where it needs to be present (hostname of "running compiler"). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8370) puppet runs generate a misleading error when hiera-eyaml is configured but not installed

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-8370 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet runs generate a misleading error when hiera-eyaml is configured but not installed  
 
 
 
 
 
 
 
 
 
 
Not sure I agree with that. It's clearly a server error which tells you that the lookup_key function is impaired because the hiera_eyaml library is missing. Without the confusing addition with "on node", it's rather easy to deduct that the library is missing on the server. Adding "not present on the server" will hence not make the message clearer, it will just repeat the term "server" a fourth time in the message. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8234) layer 3 data sources can not be overriden for unit testing purposes

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-8234 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: layer 3 data sources can not be overriden for unit testing purposes  
 
 
 
 
 
 
 
 
 
 
Brian Vanderbusch, are you unable to click on the title and change it? If so, let me know what would you like the title to be and I'll change it for you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8370) puppet runs generate a misleading error when hiera-eyaml is configured but not installed

2018-01-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-8370 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet runs generate a misleading error when hiera-eyaml is configured but not installed  
 
 
 
 
 
 
 
 
 
 
I think we should also update the specific error message to say eyaml support must be available to the compiler/where the compilation takes place. Just saying that it must be "present" leaves out all information where it is supposed to be present. (Then on top of that - there is the concatenation of "on node" - that is misleading). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8373) Lookup CLI should use RBAC token if available for PuppetDB

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8373 
 
 
 
  Lookup CLI should use RBAC token if available for PuppetDB  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8373) Lookup CLI should use RBAC token if available for PuppetDB

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-8373 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Lookup CLI should use RBAC token if available for PuppetDB  
 
 
 
 
 
 
 
 
 
 
Given that this is new design and might add options to the CLI which might be of interest for other commands as well, I'd like to see a more concrete spec of what the implementation should entail. UX might have opinions on this. Should this be consistently implemented and affect other commands than lookup? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8373) Lookup CLI should use RBAC token if available for PuppetDB

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8373 
 
 
 
  Lookup CLI should use RBAC token if available for PuppetDB  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8370) puppet runs generate a misleading error when hiera-eyaml is configured but not installed

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8370 
 
 
 
  puppet runs generate a misleading error when hiera-eyaml is configured but not installed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8370) puppet runs generate a misleading error when hiera-eyaml is configured but not installed

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-8370 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet runs generate a misleading error when hiera-eyaml is configured but not installed  
 
 
 
 
 
 
 
 
 
 
Yes, the text "on node xxx" is indeed concatenated to the message (which clearly stems from the server) in a very bad way. We have work in progress to change this in PUP-8284. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8284) i18n need to change "on node #{node}" code to be translation friendly

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-8284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: i18n need to change "on node #{node}" code to be translation friendly  
 
 
 
 
 
 
 
 
 
 
Another thing to take into account here is that the wording "on node ..." can be gravely misleading. It should say something like "during compile for node ..." instead. PUP-8370 can serve as a good example of 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-6977) Add a find_module function that returns a module's directory path

2018-01-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6977 
 
 
 
  Add a find_module function that returns a module's directory path  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3600) Create support for binary content on the File type

2018-01-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3600 
 
 
 
  Create support for binary content on the File type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 Once the catalog is transferred in JSON, non-UTF-8 sequences will no longer be allowed in the content. This means that Files that have a {{content}} of some arbitrary data may or may not be able to be transferred. [~henrik.lindberg] suggested a solution to this that will allow us to do our switch to JSON but not require an entirely new catalog format. The idea is to create a function called {{binary(str)}} that takes a {{String}} and returns a {{Struct[data => String]}} where {{data}} is a UTF-8 compatible encoding of the *bytes* (not the characters) of the input {{String}}. The {{content}} parameter of {{File}} is then changed to accept either a {{String}} or a {{Struct[data => String]}}. When it receives a {{Struct[data => String]}} then the {{data}} element is decoded with the algorithm decided for the implementation of the {{binary(str)}} function.This solution should allow the follow manifests to continue to work:{code}file { "/tmp/binary": content => binary(file("/local/binary")) }{code}{code}define my_file($content) {  file { "/tmp/binary": content =>  $  content }}my_file { "yep": content => binary(file("/local/binary")) }{code}At least one variation on those will not work (because binary data will end up in the catalog):{code}define my_file($content) {  file { "/tmp/binary": content => binary(content) }}my_file { "yep": content => file("/local/binary") }{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 

Jira (PUP-3600) Create support for binary content on the File type

2018-01-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3600 
 
 
 
  Create support for binary content on the File type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 Once the catalog is transferred in JSON, non-UTF-8 sequences will no longer be allowed in the content. This means that Files that have a {{content}} of some arbitrary data may or may not be able to be transferred. [~henrik.lindberg] suggested a solution to this that will allow us to do our switch to JSON but not require an entirely new catalog format. The idea is to create a function called {{binary(str)}} that takes a {{String}} and returns a {{Struct[data => String]}} where {{data}} is a UTF-8 compatible encoding of the *bytes* (not the characters) of the input {{String}}. The {{content}} parameter of {{File}} is then changed to accept either a {{String}} or a {{Struct[data => String]}}. When it receives a {{Struct[data => String]}} then the {{data}} element is decoded with the algorithm decided for the implementation of the {{binary(str)}} function.This solution should allow the follow manifests to continue to work:{code}file { "/tmp/binary": content => binary(file("/local/binary")) }{code}{code}define my_file($content) {  file { "/tmp/binary": content => $content }}my_file { "yep": content => binary(file("/local/binary")) }{code}At least one variation on those will not work (because binary data will end up in the catalog):{code}define my_file($content) {  file { "/tmp/binary": content => binary( $ content) }}my_file { "yep": content => file("/local/binary") }{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 

Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist

2018-01-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-8376 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Revert to production when agent-specified environment doesn't exist  
 
 
 
 
 
 
 
 
 
 
I assume you are doing this in a master scenario (agents get their catalog from the master). If that is the case, why use agent specified environment instead of using an ENC? You could then do this yourself in the ENC script, and you would not need to change the env on the agent as you would determine the mapping node => env on the master side. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8376) Revert to production when agent-specified environment doesn't exist

2018-01-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Daniel Parks 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8376 
 
 
 
  Revert to production when agent-specified environment doesn't exist  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Daniel Parks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.