Jira (FACT-1408) Facter productname issue on Solaris
Title: Message Title Boyd Adamson commented on FACT-1408 Re: Facter productname issue on Solaris I've used Sparc systems for nearly 20 years, and I've never seen one without prtdiag. What I _have _seen is older systems (Solaris <=9) where it's not on the default path, but was instead at /usr/platform/$(uname -i)/sbin/prtdiag (phew!) Prtpicl looks like a promising option at first, but I think it could be problematic in certain environments - e.g. zones. Might require it's own investigation. Some examples: Solaris 11 guest LDOM: # /sbin/prtpicl -v -c chassis SYS (chassis, 2de2a6d) :FRU :ModelName 31016686+7+1 :MfgName Oracle Corporation :SerialNumber NN111A :FW-versionSun System Firmware 8.6.0.b 2014/11/13 19:47 :Label SYS :Description SPARC T4-1B
Jira (PUP-6314) Integer/Numeric.new does not accept whitespace between sign and leading digit
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6314 Integer/Numeric.new does not accept whitespace between sign and leading digit Change By: Henrik Lindberg Summary: Integer /Numeric .new does not accept whitespace between sign and leading digit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6314) Numeric.new (and subtypes) does not accept whitespace between sign and leading digit
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6314 Numeric.new (and subtypes) does not accept whitespace between sign and leading digit Change By: Henrik Lindberg Summary: Integer/ Numeric.new (and subtypes) does not accept whitespace between sign and leading digit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6312) Load XPP instead of .pp if present and feature flag is on
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6312
Load XPP instead of .pp if present and feature flag is on
Change By:
Henrik Lindberg
If an XPP file is present that is current and represents a given .pp file and the feature flag to use -xpp is on, then the parser should deserialize the content of the XPP file and either return the parsed result. If the result contains warnings and errors they should be reported and if it contains error, an error should be raised. * The boolean feature flag {{\--\[no]xpp}} should control the behavior* The loaders that load .pp should use the XPP instead of reading the .pp file and giving it to the Ruby parser implementation* The initial import of "site.pp" should use XPP* The autoloader's path to .pp files (that ends up in the ParserAdapter) should divert the calls to XPP
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6312) Load XPP instead of .pp if present and feature flag is on
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6312 Load XPP instead of .pp if present and feature flag is on Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6315) Setting log_level to debug causes SSL API calls to fail
Title: Message Title
Adam Bottchen updated an issue
Puppet / PUP-6315
Setting log_level to debug causes SSL API calls to fail
Change By:
Adam Bottchen
Setting the log_level to debug in Puppet causes curl commands against the APIs to fail. For example:{code:java}# curl -s https://$(puppet config print certname):8081/pdb/query/v4/resources --cert $(puppet config print hostcert) --key $(puppet config print hostprivkey) --cacert $(puppet config print cacert) |wc -l22914# puppet config set log_level debug# curl -s https://$(puppet config print certname):8081/pdb/query/v4/resources --cert $(puppet config print hostcert) --key $(puppet config print hostprivkey) --cacert $(puppet config print cacert) |wc -l0# puppet config set log_level noticeDebug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Caching environment 'production' (ttl = 0 sec)Debug: Evicting cache entry for environment 'production'Debug: Caching environment 'production' (ttl = 0 sec)Debug: Runtime environment: puppet_version=4.3.2, ruby_version=2.1.8, run_mode=user, default_encoding=UTF-8# curl -s https://$(puppet config print certname):8081/pdb/query/v4/resources --cert $(puppet config print hostcert) --key $(puppet config print hostprivkey) --cacert $(puppet config print cacert) |wc -l22914{code}This seems to be true for all API endpoints that require SSL certificates. API hits against endpoints that do not require SSL certificates or endpoints that accept the authentication token do not show the problem.Standard error shows curl related errors:{code:java}# puppet config set log_level debug# curl https://$(puppet config print certname):4433/rbac-api/v1/ds --cert $(puppet config print hostcert) --key $(puppet config print hostprivkey) --cacert $(puppet config print cacert)curl: (3) [globbing] error: bad range specification after pos 11curl: (6) Couldn't resolve host 'Caching'curl: (6) Couldn't resolve host 'environment'curl: (6) Couldn't resolve host ''production''curl: (6) Couldn't resolve host '(ttl'curl: (6) Couldn't resolve host '='curl: (7) couldn't connect to hostcurl: (3) [globbing] error: bad range specification after pos 7curl: (3) [globbing] error: bad range specification after pos 3curl: (6) Couldn't resolve host 'Evicting'curl: (6) Couldn't resolve host 'cache'curl: (6) Couldn't resolve host 'entry'curl: (6) Couldn't resolve host 'for'curl: (6) Couldn't resolve host 'environment'curl: (3) [globbing] error: bad range specification after pos 15curl: (3) [globbing] error: bad range specification after pos 3{code}
Add Comment
Jira (PUP-6315) Setting log_level to debug causes SSL API calls to fail
Title: Message Title Adam Bottchen created an issue Puppet / PUP-6315 Setting log_level to debug causes SSL API calls to fail Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 2016/05/16 5:29 PM Priority: Normal Reporter: Adam Bottchen Setting the log_level to debug in Puppet causes curl against the APIs to fail. For example: # curl -s https://$(puppet config print certname):8081/pdb/query/v4/resources --cert $(puppet config print hostcert) --key $(puppet config print hostprivkey) --cacert $(puppet config print cacert) |wc -l 22914 # puppet config set log_level debug
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic {{String}} to {{Integer}} conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect {{Integer.new}} to be consistent with that conversion. * Note: this also affects {{Float.new}} (and by extension {{Numeric.new}}). *
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic {{String}} to {{Integer}} conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect {{Integer.new}} to be consistent with that conversion. Note: this also affects {{Float.new}} (and by extension {{Numeric.new}}).
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title Peter Huene updated an issue Puppet / PUP-6314 Integer.new does not accept whitespace between sign and leading digit Change By: Peter Huene Summary: Numeric Integer .new does not accept whitespace between sign and leading digit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6314) Numeric.new does not accept whitespace between sign and leading digit
Title: Message Title Peter Huene updated an issue Puppet / PUP-6314 Numeric.new does not accept whitespace between sign and leading digit Change By: Peter Huene Summary: Integer Numeric .new does not accept whitespace between sign and leading digit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic {{String}} to {{Integer}} conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect ` {{ Integer.new ` }} to be consistent with that conversion.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic string \ -> integer conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect `Integer.new` to be consistent with that conversion.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene created an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Issue Type:
Bug
Affects Versions:
PUP 4.5.0
Assignee:
Unassigned
Created:
2016/05/16 5:13 PM
Fix Versions:
PUP 4.5.1
Priority:
Normal
Reporter:
Peter Huene
The following Puppet code:
notice Integer.new('+ 1')
results in the following error:
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic string \-> integer {{String}} to {{Integer}} conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect `Integer.new` to be consistent with that conversion.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-1408) Facter productname issue on Solaris
Title: Message Title Hailee Kenney commented on FACT-1408 Re: Facter productname issue on Solaris Okay! After some digging I found the commit that made the switch from ptrdiag to ptrconf: https://github.com/puppetlabs/facter/commit/7f36d65d7c62e225b6d915d2fce39aec240eec97 The comment suggests that the reason why we're not relying on ptrdiag anymore is because it doesn't exist on all sparc machines. I can try to do some digging about which machines it does/doesn't work on. We also could potentially try to use and then fall back to ptrconf if it isn't there. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1408) Facter productname issue on Solaris
Title: Message Title Hailee Kenney commented on FACT-1408 Re: Facter productname issue on Solaris It looks like we've changed the source we're using to get that fact between Facter 2 and Facter 3, curious as to why we switched. In Facter 2 it's coming from '/usr/sbin/prtdiag' https://github.com/puppetlabs/facter/blob/2.x/lib/facter/util/manufacturer.rb#L63 In Facter 3 it's coming from '/usr/sbin/prtconf' https://github.com/puppetlabs/facter/blob/4a495e877d68648b6315b1a68755627de4c3c52d/lib/src/facts/solaris/dmi_resolver.cc#L73 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6313) Add support for 0b/0B as base 2 (binary) number
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6313 Add support for 0b/0B as base 2 (binary) number Issue Type: New Feature Assignee: Unassigned Created: 2016/05/16 4:21 PM Fix Versions: PUP 4.6.0 Priority: Normal Reporter: Henrik Lindberg Some kinds of resources deal with information at the bit level and it is beneficial if puppet can support binary numeric values directly in the language. A prefix of 0b or 0B should be taken as the start of a binary number. The lexer should recognize this, as well as the automatic 'string to numeric' conversion that takes place when arithmetic is performed on numbers. String.new() already handles formatting of binary numeric with several formatting rules. Add Comment
Jira (PUP-6000) Puppet slowing down after calling Puppet.initialize_settings multiple times
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6000 Puppet slowing down after calling Puppet.initialize_settings multiple times Change By: Steve Barlow Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5545) Use rubocop in module generator
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5545 Use rubocop in module generator Change By: Steve Barlow Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5482) Should a not found resource type be marked as such?
Title: Message Title Ruth Linehan updated an issue Puppet / PUP-5482 Should a not found resource type be marked as such? Change By: Ruth Linehan Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5482) Should a not found resource type be marked as such?
Title: Message Title Jeremy Barlow assigned an issue to Matthaus Owens Puppet / PUP-5482 Should a not found resource type be marked as such? Change By: Jeremy Barlow Assignee: Jeremy Barlow Matthaus Owens Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2526) Query pdb metrics / replication status from the PDB cli
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2526 Query pdb metrics / replication status from the PDB cli Change By: Russell Mull Summary: Query pdb metrics / replication status from the PDB cli Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2704) Make sure functions registered with at-at don't silently swallow errors
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2704 Make sure functions registered with at-at don't silently swallow errors Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2704) Make sure functions registered with at-at don't silently swallow errors
Title: Message Title Rob Browning commented on PDB-2704 Re: Make sure functions registered with at-at don't silently swallow errors I have a PR up for this on stable, but not one for extensions yet. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1414) Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016
Title: Message Title Craig Gomes updated an issue Facter / FACT-1414 Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016 Change By: Craig Gomes Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1414) Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016
Title: Message Title Craig Gomes assigned an issue to Ethan Brown Facter / FACT-1414 Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016 Change By: Craig Gomes Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1414) Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016
Title: Message Title Craig Gomes updated an issue Facter / FACT-1414 Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016 Change By: Craig Gomes QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1414) Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016
Title: Message Title Craig Gomes updated an issue Facter / FACT-1414 Facter acceptance test facts/windows.rb doesn't account for Windows 10 / Windows Server 2016 Change By: Craig Gomes QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2704) Make sure functions registered with at-at don't silently swallow errors
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2704 Make sure functions registered with at-at don't silently swallow errors Issue Type: Bug Assignee: Unassigned Created: 2016/05/16 1:59 PM Priority: Normal Reporter: Rob Browning It looks like exceptions from functions registered with at-at might be silently swallowed. If so, fix it. If this is an issue, then it may have to do with differences between Java's Runnable and Callable interfaces, and one solution might be to add our own try/catch wrappers. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-4760) Service type should not retrieve ensure status when not needed
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4760 Service type should not retrieve ensure status when not needed Change By: Steve Barlow Fix Version/s: PUP 4.y Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6312) Load XPP instead of .pp if present and feature flag is on
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6312 Load XPP instead of .pp if present and feature flag is on Issue Type: New Feature Assignee: Unassigned Created: 2016/05/16 1:45 PM Priority: Normal Reporter: Henrik Lindberg If an XPP file is present that is current and represents a given .pp file and the feature flag to use -xpp is on, then the parser should deserialize the content of the XPP file and either return the parsed result. If the result contains warnings and errors they should be reported and if it contains error, an error should be raised. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6311) Define where XPP files should be written, and how resolution works
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6311 Define where XPP files should be written, and how resolution works Issue Type: Task Assignee: Unassigned Created: 2016/05/16 1:42 PM Priority: Normal Reporter: Henrik Lindberg The native parser needs to write XPP files in a defined location. The ruby runtime needs to find them. We need a specification of how this should work. The discussion around the XPP files ended with the conclusion that the xpp files should not be included in modules (and thus preferably not reside inside of them because of read/write permissions, and for the risk of including them in published modules). Instead they need to reside on disk. As the sources can be anywhere on the file system and referenced via a module path, this means the root needs to be the root of the system in a mirrored layout if we make a naive implementation. There are also concerns regarding garbage collection; when an environment is deleted and never to be used again, when a module path is rearranged, etc. Add Comment
Jira (PUP-6310) Specify the PCore Serialization formats
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6310 Specify the PCore Serialization formats Issue Type: Task Assignee: Unassigned Created: 2016/05/16 1:31 PM Priority: Normal Reporter: Henrik Lindberg Write a formal specification of the Pcore serialization formats. (PUP-5908 is the implementation of the MsgPack format). The concepts in serialization are written up in the Pcore Definition PUP-5907 and explored/discussed in various documents - to the point where in made more sense to go ahead with an implementation. Add Comment
Jira (NPUP-10) Implement automatic String to Numeric conversion for arithmetic operators.
Title: Message Title Henrik Lindberg assigned an issue to Peter Huene Native Puppet / NPUP-10 Implement automatic String to Numeric conversion for arithmetic operators. Change By: Henrik Lindberg Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6305) R spike w/Kylo on simplifying Puppet's settings logic
Title: Message Title Erik Dasher updated an issue Puppet / PUP-6305 R spike w/Kylo on simplifying Puppet's settings logic Change By: Erik Dasher QA Risk Assessment Reason: QA RA=N/A; No functional code change associated with this ticket. QA Status: Reviewed QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6307) Theme: Native Parsing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6307 Theme: Native Parsing Change By: Henrik Lindberg This is a cross team / project / version epic for Native Parser (the puppet language parser in C++ and its integration into a complete puppet runtime).This Theme includes:* Native Parser* * Lexing/Parsing** Static Validation* XPP - the output of native parsing* Changes on the Ruby side to make use of XPP Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6308) Theme: Native Compiling
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6308 Theme: Native Compiling Change By: Henrik Lindberg This is a cross team / project / version epic for Native Compiling (the puppet catalog compiler in C++ and its integration into a complete puppet runtime). This consists of:* Native Evaluator* Calling functions implemented in Ruby* Using resource types defined in modules* T.B completed... Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6307) Theme: Native Parsing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6307 Theme: Native Parsing Change By: Henrik Lindberg This is a cross team / project / version epic for Native Parser (the puppet language parser in C++ and its integration into a complete puppet runtime). This Theme includes:* Native Parser* XPP - the output of native parsing* Changes on the Ruby side to make use of XPP Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6309) Theme: Native Puppet
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6309 Theme: Native Puppet Issue Type: Epic Assignee: Unassigned Created: 2016/05/16 12:19 PM Priority: Normal Reporter: Henrik Lindberg This is a cross team / project / version thematic epic for the native (C++) implementation of puppet. The native puppet implementation consists of three major themes: Native Parsing Native Compiling Native Agent (not yet ticketed) Add Comment
Jira (PUP-6308) Theme: Native Compiling
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6308 Theme: Native Compiling Issue Type: Epic Assignee: Unassigned Created: 2016/05/16 12:13 PM Priority: Normal Reporter: Henrik Lindberg This is a cross team / project / version epic for Native Compiling (the puppet catalog compiler in C++ and its integration into a complete puppet runtime). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6307) Theme: Native Parsing
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6307 Theme: Native Parsing Issue Type: Epic Assignee: Unassigned Created: 2016/05/16 12:07 PM Priority: Normal Reporter: Henrik Lindberg This is a cross team / project / version epic for Native Parser (the puppet language parser in C++ and its integration into a complete puppet runtime). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2703) (maint) Make PE_VER configurable
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2703 (maint) Make PE_VER configurable Issue Type: Bug Assignee: Unassigned Created: 2016/05/16 11:48 AM Priority: Normal Reporter: gepetto-bot The job will fail when running against platforms added since 2015.2. This doesn't change default behavior. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6301) Acceptance: AIX_service_provider test failing during setup
Title: Message Title William Hopper assigned an issue to Unassigned Puppet / PUP-6301 Acceptance: AIX_service_provider test failing during setup Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5992) Systemd service provider do not support custom status command
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-5992 Systemd service provider do not support custom status command Change By: Jorie Tappa Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5802) Yum provider incorrectly computes epoch for RPM package versions
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-5802 Yum provider incorrectly computes epoch for RPM package versions Change By: Jorie Tappa Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6050) lookup cli --unpack-arrays broken
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-6050 lookup cli --unpack-arrays broken Change By: Jorie Tappa Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6306) Update puppet-agent's Ruby to 2.1.9
Title: Message Title Geoff Nichols created an issue Puppet / PUP-6306 Update puppet-agent's Ruby to 2.1.9 Issue Type: Task Assignee: Unassigned Created: 2016/05/16 10:40 AM Priority: Normal Reporter: Geoff Nichols This ticket tracks the update of puppet-agent's included Ruby to 2.1.9 (except for Windows and AIX.) For AIX, we updated to Ruby 2.1.9 in puppet-agent 1.4.2. For Windows, we will update to Ruby 2.1.9 in an upcoming release. Add Comment
Jira (PDB-2702) (maint) Add example config file for running PDB and RBAC together
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2702 (maint) Add example config file for running PDB and RBAC together Issue Type: Bug Assignee: Unassigned Created: 2016/05/16 9:36 AM Priority: Normal Reporter: gepetto-bot This commit adds an example.conf for running PDB and RBAC together in the same JVM (available for ease of use under the `lein pdb` alias). This commit also relinks the old bootstrap.cfg to test-resources/bootstrap.cfg such that anyone running `lein run services` won't pick up the RBAC bootstrap.cfg and fail with odd error messages about missing configuration. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6305) R spike w/Kylo on simplifying Puppet's settings logic
Title: Message Title Chris Price assigned an issue to Chris Price Puppet / PUP-6305 R spike w/Kylo on simplifying Puppet's settings logic Change By: Chris Price Assignee: Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6305) R spike w/Kylo on simplifying Puppet's settings logic
Title: Message Title Chris Price updated an issue Puppet / PUP-6305 R spike w/Kylo on simplifying Puppet's settings logic Change By: Chris Price Sprint: Server Emerald 2016-05-18 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6305) R spike w/Kylo on simplifying Puppet's settings logic
Title: Message Title Chris Price created an issue Puppet / PUP-6305 R spike w/Kylo on simplifying Puppet's settings logic Issue Type: Task Assignee: Unassigned Created: 2016/05/16 9:28 AM Priority: Normal Reporter: Chris Price This ticket is just to track time for another half-day R spike with Kylo on how we might be able to simplify Puppet's settings logic and make the configuration readable from languages other than Ruby. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2701) fail gracefully for all missing postgres extensions
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2701 fail gracefully for all missing postgres extensions Issue Type: Improvement Assignee: Unassigned Created: 2016/05/16 8:57 AM Priority: Normal Reporter: Wyatt Alt PE PDB should fail with a meaningful error if one of the required extensions is missing. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-4488) Support global data lookup using data providers
Title: Message Title Henrik Lindberg commented on PUP-4488 Re: Support global data lookup using data providers James Kenney Since you have an open support case - they will help you sort out any configuration issues and help finding relevant tickets to see if an upgrade will solve the issue. Also, if needed, they will escalate the issue to engineering, open a ticket and follow up until it is solved. Sounds like you are in good hands Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6304) Add string formatting rules to String.new
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6304 Add string formatting rules to String.new Issue Type: New Feature Assignee: Unassigned Created: 2016/05/16 8:37 AM Fix Versions: PUP 4.6.0 Priority: Normal Reporter: Henrik Lindberg String.new supports many formatting options. One group of features that deal with chomp/chop and line endings is missing. Suggest that the following formats are added: # | Format | String # | -- | -- # | n | removes trailing \r\n or \n (i.e. 'chop'/'chomp')
Jira (PUP-6303) Acceptance: nim_package_provider test fails on AIX 5.3
Title: Message Title
John Duarte created an issue
Puppet / PUP-6303
Acceptance: nim_package_provider test fails on AIX 5.3
Issue Type:
Bug
Affects Versions:
PUP 4.5.0
Assignee:
Unassigned
Created:
2016/05/16 8:27 AM
Priority:
Normal
Reporter:
John Duarte
In our acceptance test run in CI, attempting to install a nim package on AIX 5.3 results in the following error.
[0] [AIX] root@pe-aix-53-acceptance:~ # /opt/puppetlabs/puppet/bin/puppet apply -e "package {'cdrecord': ensure => 'present', source => 'lpp_custom', provider => nim, }"
Notice: Compiled catalog for pe-aix-53-acceptance.delivery.puppetlabs.net in environment production in 1.37 seconds
Error: Execution of '/usr/sbin/nimclient -o
Jira (PUP-4488) Support global data lookup using data providers
Title: Message Title Henrik Lindberg commented on PUP-4488 Re: Support global data lookup using data providers James Kenney Think it is best to open a separate ticket for your case (also if you can, try later version 2016.1.2 which is Puppet 4.4.0) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6302) stdlib dirname does not understand Windows paths
Title: Message Title
c sights created an issue
Puppet / PUP-6302
stdlib dirname does not understand Windows paths
Issue Type:
Bug
Affects Versions:
PUP 3.8.5
Assignee:
Unassigned
Components:
Modules
Created:
2016/05/16 8:05 AM
Environment:
stdlib 4.12 Windows 7 client, Puppet 3.8.6 Debian 7 Wheezy server, Puppet 3.8.5
Priority:
Normal
Reporter:
c sights
dirname does not remove the last part of Windows paths:
In the example below dirname(C:\Windows\system32) is '.' . I think the output should be "C:\Windows"
notify { "\$::system32 $::system32" : }
$dirname32 = dirname($::system32) notify { "\$dirname32 $dirname32" : }
Output.
Notice: $dirname32 . Notice: /Stage[main]/Winnodes/Notify[$dirname32 .]/message: defined 'message' as '$dirname32 .' Notice: $::system32 C:\Windows\system32 Notice:
Jira (PUP-6301) Acceptance: AIX_service_provider test failing during setup
Title: Message Title John Duarte commented on PUP-6301 Re: Acceptance: AIX_service_provider test failing during setup William Hopper can I get your eyes on this test change? Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6301) Acceptance: AIX_service_provider test failing during setup
Title: Message Title John Duarte updated an issue Puppet / PUP-6301 Acceptance: AIX_service_provider test failing during setup Change By: John Duarte Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6301) Acceptance: AIX_service_provider test failing during setup
Title: Message Title John Duarte updated an issue Puppet / PUP-6301 Acceptance: AIX_service_provider test failing during setup Change By: John Duarte Scope Change Reason: test failing in ci Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6301) Acceptance: AIX_service_provider test failing during setup
Title: Message Title John Duarte assigned an issue to William Hopper Puppet / PUP-6301 Acceptance: AIX_service_provider test failing during setup Change By: John Duarte Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6301) Acceptance: AIX_service_provider test failing during setup
Title: Message Title John Duarte updated an issue Puppet / PUP-6301 Acceptance: AIX_service_provider test failing during setup Change By: John Duarte Sprint: Client 2016-05-18 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4488) Support global data lookup using data providers
Title: Message Title James Kenney commented on PUP-4488 Re: Support global data lookup using data providers Am using Puppet Enterprise 2015.3.3, Which seems to have: Hiera version 3.0.6 Puppet 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6301) Acceptance: AIX_service_provider test failing during setup
Title: Message Title John Duarte commented on PUP-6301 Re: Acceptance: AIX_service_provider test failing during setup Example of failure in CI Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2700) Migrate to trapperkeeper testutils/logging
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2700 Migrate to trapperkeeper testutils/logging Issue Type: Bug Assignee: Unassigned Created: 2016/05/16 7:38 AM Priority: Normal Reporter: Rob Browning Now that the logging functions we use are in trapperkeeper...testutils.logging, switch to those. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5000 acceptance: test agent_specified environment, ENC, and related facts Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6301) Acceptance: AIX_service_provider test failing during setup
Title: Message Title
John Duarte created an issue
Puppet / PUP-6301
Acceptance: AIX_service_provider test failing during setup
Issue Type:
Bug
Assignee:
John Duarte
Created:
2016/05/16 7:30 AM
Priority:
Normal
Reporter:
John Duarte
The acceptance/tests/resource/service/AIX_service_provider.rb test is failing in current CI run.
The AIX system is no longer automatically starting the service under test when it is created as seen in the example below.
[0] [AIX] root@pe-aix-61-acceptance:~ # mkssys -s sloth_daemon -p /tmp/sloth_daemon.sh.8996 -u 0 -S -n 15 -f 9
0513-071 The sloth_daemon Subsystem has been added.
[0] [AIX] root@pe-aix-61-acceptance:~ # /opt/puppetlabs/bin/puppet resource service sloth_daemon
service {
Jira (PUP-4488) Support global data lookup using data providers
Title: Message Title Henrik Lindberg commented on PUP-4488 Re: Support global data lookup using data providers James Kenney Which version of Puppet are you using? In some of the early versions supporting lookup there were errors in how hiera was handled - it bound data / the config to the first environment that used hiera (and caused a memory leak). If you are seeing this problem on Puppet 4.4.x please file a separate ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4488) Support global data lookup using data providers
Title: Message Title
James Kenney commented on PUP-4488
Re: Support global data lookup using data providers
In our case, the "puppet lookup" command only finds hiera data within the default 'production' environment, but it refuses to search through any hiera data in non-production environments ( with the datadir in hiera configured in the format of "code dir/environments/%{::environment}/hieradata" ).
We can retrieve the same data using the older method of a puppet apply + hiera lookup. Maybe the lookup function needs something extra to be environment-aware?
Using older method: [root@lpadma02 environments]# puppet apply --environment=devtest --certname=ldadma01.upgf.com -e '$somevar = hiera(ntp::package_ensure) notify { $somevar: }
' Notice: Compiled catalog for ldadma01.upgf.com in environment devtest in 0.10 seconds Notice: present Notice: /Stage[main]/Main/Notify[present]/message: defined 'message' as 'present'
Using newer method:
[root@lpadma02 ~]# puppet lookup ntp::package_ensure --node ldadma01.upgf.com Error: Could not run: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Could not find data item ntp::package_ensure in any Hiera data file and no default supplied at /u003/app/puppetlabs/code/environments/production/modules/profiles/manifests/base_rhel6.pp:81:23
Note we are using classic hiera, and have not made any changes to enable / use hiera 4.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (PDB-2699) Upgrade test dependency to RBAC 1.2.17
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2699 Upgrade test dependency to RBAC 1.2.17 Issue Type: Task Assignee: Unassigned Created: 2016/05/16 6:54 AM Fix Versions: PDB 4.1.0 Priority: Normal Reporter: Ryan Senior We added some tech debt to merge in RBAC support due to the RBAC service extending a java.jdbc protocol that altered our results. We should be able to remove that hack now that it has been fixed and released. Add Comment
Jira (FACT-1415) Replace Facter 3.x Windows Operating System kernel query with Windows Kernel API call RtlGetVersion
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1415 Replace Facter 3.x Windows Operating System kernel query with Windows Kernel API call RtlGetVersion Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6300) Float from hiera is not auto converted into string
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6300 Float from hiera is not auto converted into string Change By: Henrik Lindberg Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6300) Float from hiera is not auto converted into string
Title: Message Title
Henrik Lindberg commented on PUP-6300
Re: Float from hiera is not auto converted into string
It behaves as expected. If you want something to be a string use quotes. A version "number" is always a string since it can be something like "4.4.0.alpha.42".
The documentation points out that if you are using numbers (that is integer and float values), and you then interpolate them, then that numeric to string conversion will use base 10 (decimal) for the conversion. That has nothing to do with what you are doing here. What it is pointing out is the effect of doing something like this:
[code:puppet} $octal_value = 0777 notice "The value is $ {octal_value}
"
Will notice "The value is 511"
I am closing this ticket as puppet/hiera works as intended.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To
Jira (PUP-6297) puppet agent not using SRV record to resolve puppet master while retriving pluginfacts and plugin
Title: Message Title Sinux Shen commented on PUP-6297 Re: puppet agent not using SRV record to resolve puppet master while retriving pluginfacts and plugin Hi, as a first step, can we identify if this is a bug or mis-configuration, basically, I can re-produce it very easily. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6300) Float from hiera is not auto converted into string
Title: Message Title Poil created an issue Puppet / PUP-6300 Float from hiera is not auto converted into string Issue Type: Bug Affects Versions: PUP 3.8.7 Assignee: Unassigned Components: Puppet Server Created: 2016/05/16 6:06 AM Environment: CentOS 7 Priority: Normal Reporter: Poil In hiera I have mysql::version: 4.4
