date:20161220

Jira (FACT-1466) Facter warns aboutIt difficulty parsing routing entries on Fedora 24

2016-12-20 Thread Lee Whalen (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lee Whalen commented on  FACT-1466 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter warns aboutIt difficulty parsing routing entries on Fedora 24  
 
 
 
 
 
 
 
 
 
 
This also happens on Ubuntu 16.04, with the following:  puppet-agent 1.8.2-1xenial (package) $ facter -v: 3.5.0 (commit 872c5707799c1c30925b632f20eab763ec03b5a4) $ puppet --version: 4.8.1 
$ ip route default via 172.33.0.1 dev eth0  172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown  172.33.0.0/24 dev eth0 proto kernel scope link src 172.33.0.91  
The actual warning message on my systes is:  $ facter 2016-12-21 07:53:01.621537 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got '172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown' 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-7037) lookup_options get not honored across Data Provider [classic hiera/]environment/module

2016-12-20 Thread cameris (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 cameris commented on  PUP-7037 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: lookup_options get not honored across Data Provider [classic hiera/]environment/module  
 
 
 
 
 
 
 
 
 
 
Omg, how can I have missed that. I'm so sorry for the trouble. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-7032) Data Type Error Messages are Overly Verbose

2016-12-20 Thread Trevor Vaughan (JIRA)

Title: Message Title

Trevor Vaughan commented on PUP-7032

Re: Data Type Error Messages are Overly Verbose

Henrik Lindberg and Thomas Hallgren I think that I would like to see a few levels of configuration for this.

Default

Truncate Patterns at 10 characters if it's over 20 characters or something like that

Add vertical spacing

Do not truncate anything else

--debug

What you have now with vertical spacing

Oneline (or something)

Generally for reporting, What would be sent to PuppetDB or a Log Server

Also, syntax highlighting would help a lot if possible. At least to help break up where the data types start and stop. This is particularly true of Structs and Tuples where the order and layout matters. Arrays and basic Hashes are easy.
I suppose that my main issue is just readability and being able to actually figure out what didn't match.
Since the Types are namespaced, I easily know where to find the Type definition. I get that it's difficult to debug but I need to quickly be able to hop in and figure out what's going on and I'm finding myself overwhelmed with the error messages. I basically need to break them out and format them manually to figure out what's actually wrong.
Spaced Example:

error during compilation: Evaluation Error: Error while evaluating a Resource Statement, Class[Simplib::Ip]: parameter 'param' expects a match for:

Jira (PUP-5717) Ruby crash when using Unicode codepage on windows when writing to STDOUT on a console

2016-12-20 Thread Ethan Brown (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-5717 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ruby crash when using Unicode codepage on windows when writing to STDOUT on a console  
 
 
 
 
 
 
 
 
 
 
Also - DBCS codepages should work (as they have historically) on Windows - https://www.curlybrace.com/words/2014/10/03/windows-console-and-doublemulti-byte-character-set/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-7033) Data Type Reuse in Patterns Should be Feasible

2016-12-20 Thread Trevor Vaughan (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Trevor Vaughan commented on  PUP-7033 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Data Type Reuse in Patterns Should be Feasible  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg An AND would probably work. 
String + String is easy. Regex combinations could be done as long as they are not anchored or if the first and last elements are the only ones that are anchored. 
String + Regex + String should also be easy as long as it's a bookend. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error

2016-12-20 Thread Ben Ford (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Ford commented on  PUP-6864 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2016-12-14 11:07:52,467 WARN  [qtp206485107-403] [p.e.s.f.file-sync-versioned-code-service] Environment 'oink' could not be found, code-id cannot be calculated. 
 
 
 
 
2016-12-14 11:07:52,750 INFO  [qtp206485107-403] [puppetserver] Puppet 'replace_facts' command for oink.puppetlabs.vm submitted to PuppetDB with UUID 827cb114-092c-4a2a-a1dd-16398cc2aff2 
 
 
 
 
2016-12-14 11:07:53,083 INFO  [qtp206485107-403] [puppetserver] Puppet Caching node for oink.puppetlabs.vm 
 
 
 
 
2016-12-14 11:07:53,116 WARN  [qtp206485107-403] [puppetserver] Puppet Class 'settings' is already defined; cannot redefine at : 
 
 
 
 
2016-12-14 11:07:53,159 ERROR [qtp206485107-403] [puppetserver] Puppet Puppet::Parser::Compiler failed with error NoMethodError: undefined method `environment_data_provider' for nil:NilClass on node oink.puppetlabs.vm 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/data_providers/lookup_adapter.rb:232:in `initialize_env_provider' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/data_providers/lookup_adapter.rb:188:in `env_provider' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/data_providers/lookup_adapter.rb:95:in `lookup_in_environment'

70 matches

Mail list logo