Jira (FACT-1115) Treats non-zero responses as failures
Title: Message Title
Joshua Spence commented on FACT-1115
Re: Treats non-zero responses as failures
This doesn't seem to be fixed for me...
``` > /opt/puppetlabs/puppet/bin/ruby -rfacter -e 'puts Facter.version' 3.0.2
> /opt/puppetlabs/puppet/bin/ruby -rfacter -e 'puts Facter::Core::Execution.exec("sshd -V 2>&1").inspect' nil
> /opt/puppetlabs/puppet/bin/ruby -rfacter -e 'puts Facter::Util::Resolution.exec("sshd -V 2>&1").inspect' nil ```
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-469) Can't escape twice in a single hierarchy level
Title: Message Title
Brett Swift created an issue
Hiera / HI-469
Can't escape twice in a single hierarchy level
Issue Type:
Bug
Affects Versions:
HI 3.0.1
Assignee:
Aaron Armstrong
Components:
PE
Created:
2015/09/14 6:01 AM
Priority:
Normal
Reporter:
Brett Swift
I get an error when this literal function appears twice in the same hierarchy tier. I have this:
"cluster/% {literal('%')}{::cluster}/%{literal('%')} {role}
" and the error I get is: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, Error from DataBinding 'hiera' while looking up 'puppet::data_hierarchy': Detected in [literal('%')] at ~(class that is doing the lookup~ If i take either the first literal function or the last literal function out it fails.
Reference ticket: https://tickets.puppetlabs.com/browse/HI-127
Jira (HI-469) Can't escape twice in a single hierarchy level
Title: Message Title Henrik Lindberg commented on HI-469 Re: Can't escape twice in a single hierarchy level Ping Thomas Hallgren should check if we have an issue with this in the new hiera for data in modules as well. Should be fixed for both. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1115) Treats non-zero responses as failures
Title: Message Title
Charlie Sharpsteen commented on FACT-1115
Re: Treats non-zero responses as failures
Everything appears to be working on CentOS 6.6:
# /opt/puppetlabs/puppet/bin/ruby -rfacter -e 'puts Facter.version'
3.0.2
# /opt/puppetlabs/puppet/bin/ruby -rfacter -e 'puts Facter::Core::Execution.exec("sshd -V 2>&1").inspect'
"sshd: illegal option -- V\nOpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013\nusage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file]\n[-f config_file] [-g login_grace_time] [-h host_key_file]\n[-k key_gen_time] [-o option] [-p port] [-u len]"
# /opt/puppetlabs/puppet/bin/ruby -rfacter -e 'puts Facter::Util::Resolution.exec("sshd -V 2>&1").inspect'
"sshd: illegal option -- V\nOpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013\nusage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file]\n[-f config_file] [-g login_grace_time] [-h host_key_file]\n[-k key_gen_time] [-o option] [-p port] [-u len]"
Jira (HI-469) Can't escape twice in a single hierarchy level
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-469
Can't escape twice in a single hierarchy level
Change By:
Henrik Lindberg
I get an error when this literal function appears twice in the same hierarchy tier.I have this:{code} - "cluster/%{literal('%')}{::cluster}/%{literal('%')}{role}"{code}and the error I get is: {code} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, Error from DataBinding 'hiera' while looking up 'puppet::data_hierarchy': Detected in [literal('%')] at ~~(class that is doing the lookup~~ {code} If i take either the first literal function or the last literal function out it fails.Reference ticket: https://tickets.puppetlabs.com/browse/HI-127
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title mike jeski commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter We use audit extensively as well, and would be quite disappointed were it to go away. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-469) Can't escape twice in a single hierarchy level
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-469
Can't escape twice in a single hierarchy level
Change By:
Henrik Lindberg
I get an error when this literal function appears twice in the same hierarchy tier.I have this:{code} - "cluster/%{literal('%')}{::cluster}/%{literal('%')}{role}"{code}and the error I get is:{code}Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, Error from DataBinding 'hiera' while looking up 'puppet::data_hierarchy': Detected in [literal('%')] at ~~(class that is doing the lookup~~{code}If i take either the first literal function or the last literal function out it fails. Reference ticket: https://tickets.puppetlabs.com/browse/ The '%' escape function was implemented in HI-127
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1963) Generated resources never receive dependency edges
Title: Message Title Branan Riley updated an issue Puppet / PUP-1963 Generated resources never receive dependency edges Change By: Branan Riley Sprint: Client 2015-09- 30 16 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1963) Generated resources never receive dependency edges
Title: Message Title Branan Riley assigned an issue to Branan Riley Puppet / PUP-1963 Generated resources never receive dependency edges Change By: Branan Riley Assignee: Kylo Ginsberg Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1963) Add command rate monitor to benchmark tool
Title: Message Title Russell Mull created an issue PuppetDB / PDB-1963 Add command rate monitor to benchmark tool Issue Type: New Feature Assignee: Unassigned Created: 2015/09/14 9:26 AM Priority: Normal Reporter: Russell Mull It's easy to configure the benchmark tool to create an absurd amount of traffic, but it's hard to tell if it's actually running as fast as you want. When running the benchmark tool, show the user how many commands/sec are actually being submitted. This should be printed every 15-30s or so. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5057) Add an acceptance test to manage the 'puppet' and 'mcollective' services
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5057 Add an acceptance test to manage the 'puppet' and 'mcollective' services Change By: Josh Cooper Fix Version/s: PUP 4.2.3 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5235) New diagnostics meta-paramater requested for all resource types
Title: Message Title Heidi Pio moved an issue Puppet / PUP-5235 New diagnostics meta-paramater requested for all resource types Change By: Heidi Pio Key: MODULES PUP - 2570 5235 Project: Forge Modules Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-469) Can't escape twice in a single hierarchy level
Title: Message Title Aaron Armstrong assigned an issue to Unassigned Hiera / HI-469 Can't escape twice in a single hierarchy level Change By: Aaron Armstrong Assignee: Aaron Armstrong Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5057) Add an acceptance test to manage the 'puppet' and 'mcollective' services
Title: Message Title Joshua Partlow commented on PUP-5057 Re: Add an acceptance test to manage the 'puppet' and 'mcollective' services +1 for the addition of mcollective service test as well; it would be great to catch any issues in the service scripts earlier. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5057) Add an acceptance test to manage the 'puppet' and 'mcollective' services
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5057 Add an acceptance test to manage the 'puppet' and 'mcollective' services We've been bitten twice by failure to manage the mcollective service: PUP-5053 PUP-5057 Change By: Josh Cooper Sprint: Client 2015-09-30 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Kylo Ginsberg commented on PDB-1210 Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger Thanks for spiking that Wyatt Alt! I'm glad to hear that perf/storage costs are negligible. Is there more work needed to validate that completely? Philosophically, I also like the idea of a consistent limit throughout the ecosystem (and enforcing that throughout), but OTOH I don't know how practical it is to settle on, especially given the number of JSON-based APIs that the system may use indirectly. E.g. any limits we settle on may have a case that argues for something outside the range. Which would lead back to your spike, which is basically "as much range as the underlying tech supports". /cc Henrik Lindberg who, IIRC, put some thought into how we might specify behavior around really big numbers a year or two ago. Also /cc Peter Huene: does facter 3 have any support for numbers outside the range of unsigned or signed 64-bit min/max? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5057) Add an acceptance test to manage the 'puppet' and 'mcollective' services
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5057 Add an acceptance test to manage the 'puppet' and 'mcollective' services Change By: Josh Cooper Summary: Add an acceptance test to manage the 'puppet' service and 'mcollective' services Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1235) negative ints are replaced by max unsigned 64 bit integer unless -j is specified
Title: Message Title Peter Huene commented on FACT-1235 Re: negative ints are replaced by max unsigned 64 bit integer unless -j is specified This is a result of incorrectly calling rb_num2ulong instead of rb_num2long when writing the value out. It only affects the command line output. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1235) negative ints are replaced by max unsigned 64 bit integer unless -j is specified
Title: Message Title Peter Huene updated an issue Facter / FACT-1235 negative ints are replaced by max unsigned 64 bit integer unless -j is specified Change By: Peter Huene Fix Version/s: FACT 3.1.1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1235) negative ints are replaced by max unsigned 64 bit integer unless -j is specified
Title: Message Title Peter Huene updated an issue Facter / FACT-1235 negative ints are replaced by max unsigned 64 bit integer unless -j is specified Change By: Peter Huene Affects Version/s: FACT 3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1230) Facter on AIX should not attempt to use locales
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1230 Facter on AIX should not attempt to use locales Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1232) AIX 5.3 kernelrelease and operatingsystemrelease incorrect
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1232 AIX 5.3 kernelrelease and operatingsystemrelease incorrect Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Kylo Ginsberg commented on PDB-1210 Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger Here's the thread I was remembering: https://groups.google.com/forum/#!msg/puppet-dev/KHUUTpdnYow/WHy7egOO7BoJ Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1965) Error when syncing deactivation status causes NPE
Title: Message Title Russell Mull created an issue PuppetDB / PDB-1965 Error when syncing deactivation status causes NPE Issue Type: Bug Assignee: Unassigned Created: 2015/09/14 2:38 PM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-1965) Error when syncing deactivation status causes NPE
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1965 Error when syncing deactivation status causes NPE Change By: Russell Mull Scope Change Category: Found Scope Change Reason: Seen intermittently in unit tests Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1965) Error when syncing deactivation status causes NPE
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1965 Error when syncing deactivation status causes NPE Change By: Russell Mull Sprint: PuppetDB 2015-09-23 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1965) Error when syncing deactivation status causes NPE
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1965 Error when syncing deactivation status causes NPE Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1086) Validate on el4
Title: Message Title Josh Cooper commented on FACT-1086 Re: Validate on el4 This passed per-commit CI in https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Stable/view/Facter/job/platform_aio-facter_pkg-promote_stable/93/ We won't be able to test this on EL4 in CI until we add that platform to the daily job: https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Stable/view/Puppet%20Agent%20Daily/, which we can't yet do because of failures in puppet#stable on EL4, e.g. PUP-5225 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4916) fix hiera documentation in relation to deep_merge_options in hiera.yaml
Title: Message Title Nicholas Fagerlund commented on PUP-4916 Re: fix hiera documentation in relation to deep_merge_options in hiera.yaml Yup, good eye. In fact, I think we should make it even more vanilla yaml, and use a colon: :deep_merge_options: :merge_hash_arrays: true Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5221) Ankeny Direct Puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5221 Ankeny Direct Puppet Change By: Josh Cooper Fix Version/s: PUP 4.30 Fix Version/s: PUP 4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1963) Add command rate monitor to benchmark tool
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1963 Add command rate monitor to benchmark tool Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-463) Close all resolved tickets in Jira
Title: Message Title Josh Cooper updated an issue Hiera / HI-463 Close all resolved tickets in Jira Change By: Josh Cooper Close any tickets that have been resolved for the release.https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20HI%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20% 223 22HI%203 .0.3%22%20AND%20status%20%3D%20ResolvedThere is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: * Select Bulk Change - All # issues * Step 1 - choose all relevant issues (likely all of them) * Step 2 - Select "Transition Issues" * Step 3 - Select "Closed" * Step 4 - Select "Fixed" in Change Resolution. * View what is about to change and confirm it. Then commit the change.Dependencies: * Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5236) defined() not working with variables as documented
Title: Message Title Nicholas Fagerlund commented on PUP-5236 Re: defined() not working with variables as documented Neither; it's failure to correctly escape everything on the command line. Paste it into a file, it works fine. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1963) Add command rate monitor to benchmark tool
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1963 Add command rate monitor to benchmark tool Change By: Russell Mull Sprint: PuppetDB 2015-09-23 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1963) Add command rate monitor to benchmark tool
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1963 Add command rate monitor to benchmark tool Change By: Russell Mull Scope Change Category: Adopted Scope Change Reason: Opportunistic improvement while working in the benchmark code Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1235) negative ints are replaced by max unsigned 64 bit integer unless -j is specified
Title: Message Title
Wyatt Alt created an issue
Facter / FACT-1235
negative ints are replaced by max unsigned 64 bit integer unless -j is specified
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/09/14 1:26 PM
Priority:
Normal
Reporter:
Wyatt Alt
If I create this custom fact
Facter.add('negative-one') do
setcode do
-1
end
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Wyatt Alt commented on PDB-1210 Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger Kylo Ginsberg Peter Huene I've created FACT-1235 to track the second issue described above Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-549) serialnumber fact for AIX
Title: Message Title Josh Cooper updated an issue Facter / FACT-549 serialnumber fact for AIX Change By: Josh Cooper Fix Version/s: FACT 3.1.1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Peter Huene commented on PDB-1210 Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger Nice catch on the last bug. It's a result of incorrectly calling rb_num2ulong instead of rb_num2long when writing the value out. It only affects the command line output. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5225) EL4 cert bundle does not include geotrust forge root cert
Title: Message Title Josh Cooper commented on PUP-5225 Re: EL4 cert bundle does not include geotrust forge root cert Merged to stable in https://github.com/puppetlabs/puppet-agent/commit/dc95b9ab370324cad0dd294bedc7e168adf8e3da. We'll need to bring this over to aardwolf at some point after puppet-agent 1.2.5, so probably best to leave this open until then? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1124) Facter segfaults on el4
Title: Message Title Josh Cooper commented on FACT-1124 Re: Facter segfaults on el4 Verified against i386 with puppet-agent 1.2.4: [root@pku51fckgzrxyyk ~]# wget http://builds.puppetlabs.lan/puppet-agent/1.2.4/artifacts/el/4/PC1/i386/puppet-agent-1.2.4-1.el4.i386.rpm --14:21:55-- http://builds.puppetlabs.lan/puppet-agent/1.2.4/artifacts/el/4/PC1/i386/puppet-agent-1.2.4-1.el4.i386.rpm => `puppet-agent-1.2.4-1.el4.i386.rpm' Resolving builds.puppetlabs.lan... 10.32.77.131 Connecting to builds.puppetlabs.lan|10.32.77.131|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 32,861,259 (31M) [application/x-redhat-package-manager] 100%[>] 32,861,25926.60M/s
Jira (FACT-1124) Facter segfaults on el4
Title: Message Title Josh Cooper commented on FACT-1124 Re: Facter segfaults on el4 Verified against puppet-agent 1.2.4: [root@haocdu9tew4qofx ~]# wget http://builds.puppetlabs.lan/puppet-agent/1.2.4/artifacts/el/4/PC1/x86_64/puppet-agent-1.2.4-1.el4.x86_64.rpm --14:17:39-- http://builds.puppetlabs.lan/puppet-agent/1.2.4/artifacts/el/4/PC1/x86_64/puppet-agent-1.2.4-1.el4.x86_64.rpm => `puppet-agent-1.2.4-1.el4.x86_64.rpm' Resolving builds.puppetlabs.lan... 10.32.77.131 Connecting to builds.puppetlabs.lan|10.32.77.131|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 33,102,658 (32M) [application/x-redhat-package-manager] 100%[>] 33,102,65819.89M/s
Jira (PDB-1913) Puppetdb module 5.0.0 leaves config.ini empty
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1913 Puppetdb module 5.0.0 leaves config.ini empty Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4495) Puppet 3.5.0 introduced a regression in tag filtering for catalog runs
Title: Message Title David Danzilio commented on PUP-4495 Re: Puppet 3.5.0 introduced a regression in tag filtering for catalog runs Wondering if there's any update on this ticket. This issue is still present in 3.8.2. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title
Wyatt Alt commented on PDB-1210
Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Peter Huene Kylo Ginsberg
This testing was all done on facter 2.4.4, rather than facter 3. On facter 2, if I define this custom fact
Facter.add('big-int') do
setcode do
2134567876543245678765434567876543456787618476324857320457945873409573498
end
end
facter handles it fine, but PuppetDB will choke on submission as described in this ticket.
[~] $ facter big-int
2134567876543245678765434567876543456787618476324857320457945873409573498
Jira (FACT-1235) negative ints are replaced by max unsigned 64 bit integer unless -j is specified
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-1235 negative ints are replaced by max unsigned 64 bit integer unless -j is specified Change By: Peter Huene Assignee: Peter Huene Story Points: 1 Sprint: Client 2015-10-14 Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Peter Huene commented on PDB-1210 Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger So Facter 3 will preserve the Bignum if returned from a setcode block, so from the context of Puppet, it should behave the same as Facter 2.x. The Facter code that writes out the ruby values into JSON/YAML/console is treating values it doesn't understand as "null", which is incorrect. It should either to_s the value, raise an error, or potentially print Bignum values out (seems RapidJSON supports big integers; will need to check on yaml-cpp). Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5172) Close all resolved tickets in Jira
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5172 Close all resolved tickets in Jira Change By: Josh Cooper Close any tickets that have been resolved for the release.https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20% 224 22PUP%204 .2.2%22%20AND%20status%20%3D%20ResolvedThere is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: * Select Bulk Change - All # issues * Step 1 - choose all relevant issues (likely all of them) * Step 2 - Select "Transition Issues" * Step 3 - Select "Closed" * Step 4 - Select "Fixed" in Change Resolution. * View what is about to change and confirm it. Then commit the change.Dependencies: * Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1220) Close all resolved tickets in Jira
Title: Message Title Josh Cooper updated an issue Facter / FACT-1220 Close all resolved tickets in Jira Change By: Josh Cooper Close any tickets that have been resolved for the release.https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20FACT%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20% 223 22FACT%203 .1.0%22%20AND%20status%20%3D%20ResolvedThere is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: * Select Bulk Change - All # issues * Step 1 - choose all relevant issues (likely all of them) * Step 2 - Select "Transition Issues" * Step 3 - Select "Closed" * Step 4 - Select "Fixed" in Change Resolution. * View what is about to change and confirm it. Then commit the change.Dependencies: * Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1965) Error when syncing deactivation status causes NPE
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1965 Error when syncing deactivation status causes NPE Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1627) minimal clojure tests for benchmark functionality
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1627 minimal clojure tests for benchmark functionality Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1963) Add command rate monitor to benchmark tool
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1963 Add command rate monitor to benchmark tool Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5237) Have Package resource to lock versions of Packages
Title: Message Title Anandkumar Asokan updated an issue Puppet / PUP-5237 Have Package resource to lock versions of Packages Change By: Anandkumar Asokan Affects Version/s: PUP 3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5237) Have Package resource to lock versions of Package
Title: Message Title
Anandkumar Asokan created an issue
Puppet / PUP-5237
Have Package resource to lock versions of Package
Issue Type:
New Feature
Assignee:
Aaron Armstrong
Components:
PE
Created:
2015/09/14 10:29 PM
Priority:
Normal
Reporter:
Anandkumar Asokan
Ok, in summary can we use puppet's package resource to lock in a version update of a package using yum version lock (RHEL, CentOS) or Apt-mark hold (Ubuntu). This is so that puppet doesn't update a package when an agent run is initiated. EG:
So let’s say you have a package resource defined as follows:
package { 'puppet': ensure => '3.7.5-1.el7', }
Then if you do a system update (this could be via command line, mCollective, exec resource of “yum update -y”, etc) you end up with this:
puppet resource package puppet
package { 'puppet': ensure => '3.8.2-1.el7', }
Add Comment
Jira (PUP-5237) Have Package resource to lock versions of Packages
Title: Message Title Anandkumar Asokan updated an issue Puppet / PUP-5237 Have Package resource to lock versions of Packages Change By: Anandkumar Asokan Summary: Have Package resource to lock versions of Package Packages Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5237) Have Package resource to lock versions of Packages
Title: Message Title
Anandkumar Asokan updated an issue
Puppet / PUP-5237
Have Package resource to lock versions of Packages
Change By:
Anandkumar Asokan
Ok, in summary can we use puppet's package resource to lock in a version update of a package using yum version lock (RHEL, CentOS) or Apt-mark hold (Ubuntu).This is so that puppet doesn't update a package when an agent run is initiated. EG:So let’s say you have a package resource defined as follows:package { 'puppet':ensure => '3.7.5-1.el7',}Then if you do a system update (this could be via command line, mCollective, exec resource of “yum update -y”, etc) you end up with this:puppet resource package puppetpackage { 'puppet':ensure => '3.8.2-1.el7',} We want to avoid this from happening by having a package resource pinning of locking a package to that version.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5237) Have Package resource to lock versions of Packages
Title: Message Title Aaron Armstrong assigned an issue to Unassigned Puppet / PUP-5237 Have Package resource to lock versions of Packages Change By: Aaron Armstrong Assignee: Aaron Armstrong Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1086) Validate on el4
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-1086 Validate on el4 Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter Please, please, please don't do this. This is used extensively by many of my clients. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett created an issue Puppet / PUP-5233 puppet inspect is using wrong path for catalog data Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Created: 2015/09/14 12:35 AM Priority: Major Reporter: Jo Rhett Deploying Puppet 4 at a client which makes heavy use of puppet inspect and found that Puppet 4 uses the wrong path to find the client catalog. [vagrant@client ~]$ sudo puppet agent --test Info: Retrieving pluginfacts Info: Retrieving plugin
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title
Jo Rhett updated an issue
Puppet / PUP-5233
puppet inspect is using wrong path for catalog data
Change By:
Jo Rhett
Deploying Puppet 4 at a client which makes heavy use of {{puppet inspect}} and found that Puppet 4 uses the wrong path to find the client catalog.{code}[vagrant@client ~]$ sudo puppet agent --testInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for client.example.comInfo: Applying configuration version '1442215415'Notice: /Stage[main]/Main/File[/etc/hosts]/content: audit change: previously recorded value {md5}e2b06541983600068fff455f8c11861a has been changed to {md5}28c9f9f5a3d060a500d4b57f9875ba32Notice: Applied catalog in 0.39 seconds[vagrant@client ~]$ sudo puppet inspectError: Could not run: Could not find catalog for client.example.com{code}Strace shows us that it's looking in the {{client_yaml}} directory instead of {{client_data}}.{code}[pid 7817] lstat("/opt/puppetlabs", {st_mode=S_IFDIR|0755, st_size=42, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet", {st_mode=S_IFDIR|0755, st_size=102, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby", {st_mode=S_IFDIR|0755, st_size=47, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0[pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/yaml.rb", {st_mode=S_IFREG|0644, st_size=1940, ...}) = 0[pid 7817] stat("/etc/puppetlabs/puppet/routes.yaml", 0x7fff96c96bd0) = -1 ENOENT (No such file or directory)[pid 7817] stat("/opt/puppetlabs/puppet/cache/client_yaml/catalog/client.example.com.yaml", 0x7fff96c96bd0) = -1 ENOENT (No such file or directory)[pid 7817] write(2, "\33[1;31mError: Could not run: Cou"..., 78Error: Could not run: Could not find catalog for client.example.com) = 78{code}The catalog is actually stored in {{/opt/puppetlabs/puppet/cache/client_data/catalog/}}. Workaround implemented for Furthermore, the client: catalog is now in JSON format not YAML, and there's no documented command line option to read this properly. {code} file { ' $ ls -la /opt/puppetlabs/puppet/cache/ client_yaml client_data /catalog ': / ensure => link, total 24 target => '/opt/puppetlabs/puppet/cache/client_data/catalog', drwxr-xr-x 2 root root64 Sep 14 07:46 . } drwxr-x--- 3 root root20 Aug 2 22:49 .. -rw-rw 1 root root 16947 Sep 14 07:46 client.example.com.json {code}
Jira (PDB-1964) applied-migrations swallows exceptions and returns an empty set
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1964 applied-migrations swallows exceptions and returns an empty set Issue Type: Bug Assignee: Unassigned Created: 2015/09/14 11:39 AM Priority: Normal Reporter: Wyatt Alt We should get more granular around what we do here for what exceptions. If your database is improperly permissioned we'll try to migrate on top of it and fail mysteriously because the certnames table exists already. I'd guess the exception we mean to let through is where the schema_migrations table doesn't exist. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Peter Huene commented on PDB-1210 Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger Facter supports signed 64-bit integers and 64-bit floating point numbers. There's no "big int" implementation currently, but we could potentially add one (may require additional plumbing to "play nice" with Ruby/JRuby, though). Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5225) EL4 cert bundle does not include geotrust forge root cert
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5225 EL4 cert bundle does not include geotrust forge root cert Change By: Matthaus Owens Scope Change Reason: I was near this code already with solaris 11 work so I just did it. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5225) EL4 cert bundle does not include geotrust forge root cert
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-5225 EL4 cert bundle does not include geotrust forge root cert Change By: Matthaus Owens Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5171) Send out announcements
Title: Message Title Eric Sorenson commented on PUP-5171 Re: Send out announcements Draft announcement: Puppet Agent 1.2.4 is out! This is a new minor release of the All-in-One agent bundle which incorporates updates to Puppet, Facter, Hiera, and Mcollective. * Puppet 4.2.2, a bugfix release which includes an important Windows security fix: https://docs.puppetlabs.com/puppet/4.2/reference/release_notes.html#puppet-422 * Facter 3.1.0, a backwards-compatible feature release of Facter which adds support for OpenBSD and Solaris facts, improves the network interface facts, and fixes a regression that caused Docker containers on systemd hosts to
Jira (PUP-4476) Add a 'puppet lookup' command line application as UI to lookup function
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Puppet / PUP-4476 Add a 'puppet lookup' command line application as UI to lookup function Change By: Shaigy Nixon Assignee: qa Shaigy Nixon Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Kenneth Barber commented on PDB-1210 Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger Peter Huene now I'm confused, I thought facter would support at least up to 64 bit unsigned integers, because that's definitely the kind of number we saw that triggered this issue in the first place (with the gce instance id # PDB only supported 64-bit signed, which made it overflow upon receiving a higher number). Are you absolutely sure its 64 signed integers for facter only? If that's true, I'm missing a piece of the puzzle here. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5236) defined() not working with variables as documented
Title: Message Title
Ben Ford created an issue
Puppet / PUP-5236
defined() not working with variables as documented
Issue Type:
Bug
Assignee:
Nicholas Fagerlund
Components:
DOCS, Language
Created:
2015/09/14 12:06 PM
Priority:
Normal
Reporter:
Ben Ford
Not sure if this is a docs thing or a language bug. https://docs.puppetlabs.com/references/latest/function.html#defined
root@master:/etc/puppetlabs/code # puppet apply -e 'if defined('$custom_fact') { notice("foo") }'
Error: Evaluation Error: Error while evaluating a Function Call, function 'defined' called with mis-matched arguments
expected:
Jira (PDB-1210) SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Peter Huene commented on PDB-1210 Re: SPIKE: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger I don't quite know where a BigInteger is coming from, as Facter's Java interop creates Longs :/ Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-931) Leatherman gets cranky when building for FreeBSD
Title: Message Title Michael Moll assigned an issue to Michael Moll this should be fixed by LTH-28 Facter / FACT-931 Leatherman gets cranky when building for FreeBSD Change By: Michael Moll Resolution: Fixed Assignee: Michael Moll Fix Version/s: FACT 3.1.0 Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Believe it or not, this is a potential fail for the Puppet 4 upgrade at this client. I'm digging around with the puppet report and puppet catalog commands trying to find a way to generate a yaml report so that the inspect command can work. If I am unable to resolve this within 24 hours, I'll be forced to revert this customer back to Puppet 3. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Jo Rhett commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter The PUP-5233 issue relates to a customer who depends extensively on audit functionality, and is prepared to revert back from Puppet 4 to Puppet 3 if I cannot get inspect working tomorrow. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data It would appear that the following would be a viable workaround, however inspect fails to notice the differences: [root@client catalog]# puppet agent --catalog_cache_terminus=yaml [root@client catalog]# ls -la /opt/puppetlabs/puppet/cache/client_yaml/catalog total 36 drwxr-xr-x 2 root root36 Sep 14 08:42 . drwxr-x--- 3 root root20 Sep 14 08:11 .. -rw-rw 1 root root 36582 Sep 14 08:42 client.example.com.yaml [root@client catalog]# puppet inspect --verbose Notice: Finished inspection in 1.41 seconds [root@client catalog]# echo "#junk" >> /etc/hosts [root@client catalog]# puppet inspect --verbose
Jira (PUP-5234) Puppet should be able to change a role's shell
Title: Message Title sowrabha hg created an issue Puppet / PUP-5234 Puppet should be able to change a role's shell Issue Type: Bug Affects Versions: PUP 3.6.2 Assignee: Unassigned Attachments: shell.patch Components: Puppet Server Created: 2015/09/14 2:11 AM Environment: Solaris Operating System Priority: Normal Reporter: sowrabha hg It is not possible to set the shell explicitly while creating user or a role in solaris. The attribute "shell" of the type "User" is not implemeted. Because /usr/ruby/1.9/lib/ruby/vendor_ruby/1.9.1/puppet/provider/user/user_role_add.rb has no code to change a roles shell I have attached the patch which fixes
