Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Michal Zubac commented on PUP-4516 Re: Agent does not stop with Ctrl-C as a workaround of this issue, you can use SIGQUIT (CTRL+\ interactively) to stop puppet agent run. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5585) agent asking for invalid environment does not honor no-usecacheonfailure
Title: Message Title Michal Zubac created an issue Puppet / PUP-5585 agent asking for invalid environment does not honor no-usecacheonfailure Issue Type: Bug Affects Versions: PUP 3.8.1 Assignee: Kylo Ginsberg Components: Client Created: 2015/12/08 4:00 AM Environment: puppet-3.8.1-1.el6.noarch @ CentOS 6.7 Priority: Normal Reporter: Michal Zubac When I try running puppet agent against non-existing environment, it does not skip the run as I expect while using - test ( -no-usecacheonfailure). Everything is as expected, when the catalog compilation error occurs. Not in the invalid environment scenario. Here are some examples: everything ok in catalog [root@test-machine ~]# puppet agent --test --environment my_env --noop Info: Retrieving pluginfa
Jira (PUP-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5578
parse_string doesnt interpolate %{key} with Puppet 4.0
Change By:
Henrik Lindberg
Several backends need to pass {{ % \ {key \ } }} to `Backend.parse_string` in order for it to get interpolated, hiera-http and hiera-mysql are both examples of this. In Puppet 4.0 the {{ % \ {key \ } }} does not get interpolated (regardless of the hiera version) but running hiera from the command line does work. So I'm unsure if this is a PUPPET or HIERA issue, but I'm filing it here to start with.Please see https://github.com/crayfishx/hiera-http/issues/38 for a detailed description
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5578
parse_string doesnt interpolate %{key} with Puppet 4.0
Change By:
Henrik Lindberg
Release Notes Summary:
Interpolation of values stemming from keys where the value was expected to be missing and instead supplied from defaults stopped working in Puppet 4.x due to the distinction it makes between empty string and undefined. This problem occurred for lookups of missing variables in puppet.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5586) Yum package installation with an epoch fails
Title: Message Title
Chris Spence created an issue
Puppet / PUP-5586
Yum package installation with an epoch fails
Issue Type:
Bug
Affects Versions:
PUP 4.3.1
Assignee:
Unassigned
Created:
2015/12/08 6:39 AM
Priority:
Normal
Reporter:
Chris Spence
After this commit https://github.com/puppetlabs/puppet/commit/1fdaeae9fa4f18c1c96da3d6fd84613dab6024f8 it is no longer possible to ensure the version at first install of a package where the package has a non-zero epoch set:
[root@acceptance ~]# cat foo.pp
package { 'mod_ssl': ensure => '1:2.4.16' }
Jira (PDB-2215) Intermittent test failures on pe-puppetdb: Failed to perform blocking sync
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-2215 Intermittent test failures on pe-puppetdb: Failed to perform blocking sync Change By: Ryan Senior Assignee: Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1796) File resource fails for root(/) directory.
Title: Message Title
Joshuatly Tee commented on PUP-1796
Re: File resource fails for root(/) directory.
Still getting this for PE 2015.2.3
[root@puppet ~]# cat file.pp file { '/root': ensure => 'directory', owner => 'root', group => 'root', mode => '0700', }
[root@puppet ~]# puppet apply file.pp Notice: Compiled catalog for puppet in environment production in 0.37 seconds Notice: Applied catalog in 0.63 seconds
Trying the same thing for / (root) it fails with this error:
[root@puppet ~]# cat file.pp file { '/': ensure => 'directory', owner => 'root', group => 'root', mode => '0555', }
[root@puppet ~]# puppet apply file.pp Notice: Compiled catalog for puppet in environment production in 0.36 seconds Error: Parameter path failed on File[/]: File paths must be fully qualified, not '' at /root/file.pp:1
This is coming from the title_patterns regexp for the file type, which attempts to strip trailing slashes: def self.title_patterns [ [ /^(.?)\/\Z/m, [ [ :path ] ] ] ] end
Now implementing the workaround, the file resource for / (root) gets applied just fine: [root@puppet ~]# cat file.pp file { '/.': ensure => 'directory', owner => 'root', group => 'root', mode => '0555', }
[root@puppet ~]# puppet apply file.pp Notice: Compiled catalog for puppet in environment production in 0.37 seconds Notice: Applied catalog in 0.63 seconds
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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.googl
Jira (PUP-5554) Improve lexer speed on jruby
Title: Message Title Henrik Lindberg commented on PUP-5554 Re: Improve lexer speed on jruby Merged to stable at: ffab0b8 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5554) Improve lexer speed on jruby
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5554 Improve lexer speed on jruby Change By: Henrik Lindberg Release Notes Summary: Performance improvements were made to the lexer and parser that gives aprox 10% reduced parse time on MRI, and a substantial reduction on JRuby. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5554) Improve lexer speed on jruby
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5554 Improve lexer speed on jruby Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5585) agent asking for invalid environment does not honor no-usecacheonfailure
Title: Message Title
Michal Zubac updated an issue
Puppet / PUP-5585
agent asking for invalid environment does not honor no-usecacheonfailure
Change By:
Michal Zubac
When I try running puppet agent against non-existing environment, it does not skip the run as I expect while using {{ ` --test ` ( ` --no-usecacheonfailure ` ) }} .Everything is as expected, when the catalog compilation error occurs. Not in the invalid environment scenario.Here are some examples:h3. everything ok in catalog{quote}[root@test-machine ~]# puppet agent --test --environment my_env --noopInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for test-machine.company-domain.comInfo: Applying configuration version '1234567890'...{quote}h3. invalid environment specified{quote}[root@test-machine ~]# puppet agent --test --environment my_non_existing_env --noopWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Find /my_non_existing_env/node/test-machine.company-domain.com?transaction_uuid=12345678-90ab-cdef-1234-567890abcde... resulted in 404 with the message: Not Found: Could not find environment 'my_non_existing_env'Info: Retrieving pluginfactsError: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment my_non_existing_env source(s) puppet://test-master/pluginfactsNotice: /File[/var/lib/puppet/facts.d/custom_fact_01.py]: Dependency File[/var/lib/puppet/facts.d] has failures: trueWarning: /File[/var/lib/puppet/facts.d/custom_fact_01.py]: Skipping because of failed dependenciesInfo: Retrieving pluginError: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from environment my_non_existing_env source(s) puppet://test-master/plugins...{quote}Same thing occurs without _--noop_ parameter.h3. catalog problem{quote}[root@test-machine ~]# puppet agent --test --environment my_env --noopInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid relationship: Package[pkg] { require => File[xxx] }, because File[xxx] doesn't seem to be in the catalogWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{quote}
Add Comment
Jira (PUP-5585) agent asking for invalid environment does not honor no-usecacheonfailure
Title: Message Title
Michal Zubac updated an issue
Puppet / PUP-5585
agent asking for invalid environment does not honor no-usecacheonfailure
Change By:
Michal Zubac
When I try running puppet agent against non-existing environment, it does not skip the run as I expect while using ` {{ --test ` }} (`--no-usecacheonfailure`).Everything is as expected, when the catalog compilation error occurs. Not in the invalid environment scenario.Here are some examples:h3. everything ok in catalog{quote}[root@test-machine ~]# puppet agent --test --environment my_env --noopInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for test-machine.company-domain.comInfo: Applying configuration version '1234567890'...{quote}h3. invalid environment specified{quote}[root@test-machine ~]# puppet agent --test --environment my_non_existing_env --noopWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Find /my_non_existing_env/node/test-machine.company-domain.com?transaction_uuid=12345678-90ab-cdef-1234-567890abcde... resulted in 404 with the message: Not Found: Could not find environment 'my_non_existing_env'Info: Retrieving pluginfactsError: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment my_non_existing_env source(s) puppet://test-master/pluginfactsNotice: /File[/var/lib/puppet/facts.d/custom_fact_01.py]: Dependency File[/var/lib/puppet/facts.d] has failures: trueWarning: /File[/var/lib/puppet/facts.d/custom_fact_01.py]: Skipping because of failed dependenciesInfo: Retrieving pluginError: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from environment my_non_existing_env source(s) puppet://test-master/plugins...{quote}Same thing occurs without _--noop_ parameter.h3. catalog problem{quote}[root@test-machine ~]# puppet agent --test --environment my_env --noopInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid relationship: Package[pkg] { require => File[xxx] }, because File[xxx] doesn't seem to be in the catalogWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{quote}
Add Comment
Jira (PUP-5585) agent asking for invalid environment does not honor no-usecacheonfailure
Title: Message Title
Michal Zubac updated an issue
Puppet / PUP-5585
agent asking for invalid environment does not honor no-usecacheonfailure
Change By:
Michal Zubac
When I try running puppet agent against non-existing environment, it does not skip the run as I expect while using {{ --test }} ( ` --no-usecacheonfailure ` ).Everything is as expected, when the catalog compilation error occurs. Not in the invalid environment scenario.Here are some examples:h3. everything ok in catalog{quote}[root@test-machine ~]# puppet agent --test --environment my_env --noopInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for test-machine.company-domain.comInfo: Applying configuration version '1234567890'...{quote}h3. invalid environment specified{quote}[root@test-machine ~]# puppet agent --test --environment my_non_existing_env --noopWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Find /my_non_existing_env/node/test-machine.company-domain.com?transaction_uuid=12345678-90ab-cdef-1234-567890abcde... resulted in 404 with the message: Not Found: Could not find environment 'my_non_existing_env'Info: Retrieving pluginfactsError: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment my_non_existing_env source(s) puppet://test-master/pluginfactsNotice: /File[/var/lib/puppet/facts.d/custom_fact_01.py]: Dependency File[/var/lib/puppet/facts.d] has failures: trueWarning: /File[/var/lib/puppet/facts.d/custom_fact_01.py]: Skipping because of failed dependenciesInfo: Retrieving pluginError: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from environment my_non_existing_env source(s) puppet://test-master/plugins...{quote}Same thing occurs without _--noop_ parameter.h3. catalog problem{quote}[root@test-machine ~]# puppet agent --test --environment my_env --noopInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid relationship: Package[pkg] { require => File[xxx] }, because File[xxx] doesn't seem to be in the catalogWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{quote}
Add Comment
Jira (FACT-1282) Incorrect ipaddress selection when default route points to L2 interface
Title: Message Title Glenn Matthews created an issue Facter / FACT-1282 Incorrect ipaddress selection when default route points to L2 interface Issue Type: Bug Affects Versions: FACT 3.1.2 Assignee: Unassigned Created: 2015/12/08 9:09 AM Priority: Normal Reporter: Glenn Matthews Somewhat similar to FACT-380. In our case we have a default route with a configured src address, pointing to an interface that doesn't itself have an IP address: bash-4.3# ip route show default dev fwdintf scope link src 192.168.122.222 bash-4.3# ifconfig fwdintf
Jira (FACT-1282) Incorrect ipaddress selection when default route points to L2 interface
Title: Message Title Glenn Matthews assigned an issue to Glenn Matthews Facter / FACT-1282 Incorrect ipaddress selection when default route points to L2 interface Change By: Glenn Matthews Assignee: Glenn Matthews Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Glenn Matthews updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: Glenn Matthews Summary: Incorrect ipaddress selection when networking.ip should fall back to default route points to L2 interface 'src' if networking.primary has no IP address Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5505) Reading services on Mac is very slow
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5505 Reading services on Mac is very slow Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5505) Reading services on Mac is very slow
Title: Message Title
John Duarte commented on PUP-5505
Re: Reading services on Mac is very slow
Verified speed increase on OS X 10.10 using puppet-agent at SHA master#e556a1266cc28c87a58809392f6a5126f4d02d16
2.8 seconds for service query
svwgu21edhj8uhk:~ root# puppet --version
4.3.2
svwgu21edhj8uhk:~ root# time puppet resource service puppet
service { 'puppet':
ensure => 'stopped',
enable => 'true',
}
real0m2.844s
user0m2.006s
Jira (PUP-5505) Reading services on Mac is very slow
Title: Message Title John Duarte updated an issue Puppet / PUP-5505 Reading services on Mac is very slow Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5505) Reading services on Mac is very slow
Title: Message Title John Duarte updated an issue Puppet / PUP-5505 Reading services on Mac is very slow Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5505) Reading services on Mac is very slow
Title: Message Title John Duarte updated an issue Puppet / PUP-5505 Reading services on Mac is very slow Change By: John Duarte QA Risk Assessment Reason: Low risk of regression Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5587) Unnecessary amount of dns requests with SRV records
Title: Message Title Josh Cooper created an issue Puppet / PUP-5587 Unnecessary amount of dns requests with SRV records Issue Type: Bug Assignee: Unassigned Created: 2015/12/08 9:43 AM Priority: Normal Reporter: Josh Cooper Originally filed in https://projects.puppetlabs.com/issues/19842 by Vincent Gallissot: I want to make you a feedback of using SRV records with Puppet 3.1.1 My architecture is : puppetca = puppet master acting as ca and able to manage all nodes files (centos 6.3 with Puppet server 3.1.1) puppet1 and puppet2 = puppet master not ca. They are configured the old way (not with SRV) with ca_server=puppetca, server=fqdn and ca=false mynode = desktop with puppet 3.1.1, under Fedora 16 Here are my DNS records : x-puppet.tcp IN SRV 0 50 8140 puppet1.foobar.fr. x-puppet.tcp IN SRV 0 50 8140 puppet2.foobar.fr. x-puppet.tcp IN SRV 10 100 8140 puppetca.foobar.fr. x-puppet-ca.tcp IN SRV 0 100 8140 puppetca.foobar.fr. x-puppet-report.tcp IN SRV 0 100 8140 puppetca.foobar.fr. First of all, thanks for correcting the bug in http://projects.puppetlabs.com/issues/18161, works fine now !
Jira (PUP-5587) Unnecessary amount of dns requests with SRV records
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5587 Unnecessary amount of dns requests with SRV records Change By: Josh Cooper Originally filed in https://projects.puppetlabs.com/issues/19842 by Vincent Gallissot:I want to make you a feedback of using SRV records with Puppet 3.1.1My architecture is :* puppetca = puppet master acting as ca and able to manage all nodes files (centos 6.3 with Puppet server 3.1.1)* puppet1 and puppet2 = puppet master not ca. They are configured the old way (not with SRV) with ca_server=puppetca, server=fqdn and ca=false* mynode = desktop with puppet 3.1.1, under Fedora 16 * Here are my DNS records : x-puppet.tcp IN SRV 0 50 8140 puppet1.foobar.fr.x-puppet.tcp IN SRV 0 50 8140 puppet2.foobar.fr.x-puppet.tcp IN SRV 10 100 8140 puppetca.foobar.fr.x-puppet-ca.tcp IN SRV 0 100 8140 puppetca.foobar.fr.x-puppet-report.tcp IN SRV 0 100 8140 puppetca.foobar.fr.First of all, thanks for correcting the bug in http://projects.puppetlabs.com/issues/18161, works fine now !Secondly, the tips given in http://projects.puppetlabs.com/issues/16840 work for me too.Thirdly, as you can see in logs (files mynode, puppet1 and puppet2 .foobar.fr), with SRV, nodes try to reach every masters and generate a lot of requests, not only dns ones. It tries to access all servers in “x-puppet.tcp.foobar.fr.” and it’s not the best way. It also continue to resolve SRV even if it’s downloading its configuration from the master. Using SRV records is for high availability and load distribution. It shouldn’t double the nodes connexions. In facts, the more masters you have the more your network is overloaded.Nodes should try to resolve “x-puppet.tcp.foobar.fr.” only one time and if the returned server is available to connect, the node shouldn’t do any other SRV request for “x-puppet.tcp.foobar.fr.” or tries to connect to the other masters.As it’s written in the doc, the amount of DNS requests is very high, but is not needed at all. Add Comment This message was sent by Atlassian JIR
Jira (PUP-5505) Reading services on Mac is very slow
Title: Message Title Michael Smith commented on PUP-5505 Re: Reading services on Mac is very slow Not really a release note category for 'made things better', going to go with "Bug Fix". Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5505) Reading services on Mac is very slow
Title: Message Title Michael Smith updated an issue Puppet / PUP-5505 Reading services on Mac is very slow Change By: Michael Smith Release Notes Summary: Querying service enablement status on Mac OS X is now significantly faster. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Reid Vandewiele created an issue Puppet / PUP-5588 Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Issue Type: Bug Assignee: Unassigned Created: 2015/12/08 12:23 PM Priority: Normal Reporter: Reid Vandewiele We monkey patch OpenSSL::X509::Store#set_default_paths to load our own additional certs. Specifically in the case of code that uses Net::HTTP, however, the monkey patch is invoked multiple times, and on the second and subsequent invocations the cert(s) are already loaded into the object. This causes a warning to print very verbosely, obscuring useful output. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-5588 Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Change By: Reid Vandewiele We monkey patch OpenSSL::X509::Store#set_default_paths to load our own additional certs. Specifically in the case of code that uses Net::HTTP, however, the monkey patch is can be invoked multiple times, and on the second and subsequent invocations the cert(s) are already loaded into the object. This causes a warning to print very verbosely, obscuring useful output. Puppet faces or extensions that use Net::HTTP or open-uri can trigger these superfluous warnings. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2246) Include trivial system summary information in jenkins test log
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2246 Include trivial system summary information in jenkins test log Issue Type: Improvement Assignee: Unassigned Created: 2015/12/08 12:47 PM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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
Jira (PDB-2246) Include trivial system summary information in jenkins test log
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2246 Include trivial system summary information in jenkins test log Change By: Rob Browning Sprint: PuppetDB 2015-12-16 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2246) Include trivial system summary information in jenkins test log
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2246 Include trivial system summary information in jenkins test log Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1974) Mechanism for securing sensitive catalog data
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1974 Mechanism for securing sensitive catalog data Change By: Owen Rodabaugh CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5538) Puppet fails to convert Windows Unicode group or user names to sids
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5538 Puppet fails to convert Windows Unicode group or user names to sids Change By: Ethan Brown Sprint: Windows 2016-01-13 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2247) (maint) Cleanup our acceptance tests
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2247 (maint) Cleanup our acceptance tests Issue Type: Bug Assignee: Unassigned Created: 2015/12/08 2:16 PM Priority: Normal Reporter: gepetto-bot This commit removes some embedded database testing remanents and changes some of our existing beaker code to use proper beaker helpers. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2247) (maint) Cleanup our acceptance tests
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2247 (maint) Cleanup our acceptance tests Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: Had time, easy fix Sprint: PuppetDB 2015-12-16 Fix Version/s: PDB 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title rick hornsby updated an issue Puppet / PUP-5296 Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Change By: rick hornsby Affects Version/s: PUP 4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title rick hornsby commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Seeing the same behavior in Puppet 4.3.0. Added it to the list of affected versions. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3839) Use internal gem mirror for acceptance host setup
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3839 Use internal gem mirror for acceptance host setup Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3523) Scope work required to override environment caching behavior
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3523 Scope work required to override environment caching behavior Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3555) introduce override-able factory pattern for constructing environment cache entries
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3555 introduce override-able factory pattern for constructing environment cache entries Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3512) Require metric id in Puppet Profiler API
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3512 Require metric id in Puppet Profiler API Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3854) Update the automation in puppet_for_the_win to retrieve cfacter from the right location
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3854 Update the automation in puppet_for_the_win to retrieve cfacter from the right location Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5004) Add node definitions for Fedora 22 to the source repos
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5004 Add node definitions for Fedora 22 to the source repos Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-659) Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with ::
Title: Message Title Eric Thompson updated an issue Puppet / PUP-659 Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with :: Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3436) Optimize CPU intensitive compiler methods
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3436 Optimize CPU intensitive compiler methods Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2402) Add acceptance tests for sshkey type
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2402 Add acceptance tests for sshkey type Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5096) Windows Puppet build includes an OpenSSL with crazy defaults baked in
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5096 Windows Puppet build includes an OpenSSL with crazy defaults baked in Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1974) Mechanism for securing sensitive catalog data
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1974 Mechanism for securing sensitive catalog data Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: This has become more and more of an issue as time goes on and customers realize secrets are stored in plaintext. CS Severity: 3 CS Business Value: 5 CS Frequency: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3591 Puppet does not plugin sync with the proper environment after agent attempts to resolve environment Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3621) Environments::Cached#get! bypasses the environment cache.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3621 Environments::Cached#get! bypasses the environment cache. Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3615) Remove automatic string to number conversion
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3615 Remove automatic string to number conversion Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-405) Remove ActiveRecord stored configs
Title: Message Title Eric Thompson updated an issue Puppet / PUP-405 Remove ActiveRecord stored configs Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3389) Significant delay in puppet runs with growing numbers of directory environments
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3389 Significant delay in puppet runs with growing numbers of directory environments Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2904) Make string/symbol use consistent in new function API
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2904 Make string/symbol use consistent in new function API Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3806) Issue with Collectors and the Future Parser
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3806 Issue with Collectors and the Future Parser Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3461) Blocks validate parameters incorrectly
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3461 Blocks validate parameters incorrectly Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3786 Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-776) Display the FS label in the partitions fact
Title: Message Title Eric Thompson updated an issue Facter / FACT-776 Display the FS label in the partitions fact Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3313) Remove deprecated puppet_lambda method
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3313 Remove deprecated puppet_lambda method Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3793) Exec resource's user validation should not block catalog compilation
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3793 Exec resource's user validation should not block catalog compilation Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Eric Thompson updated an issue Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3002) Better report invalid resource attribute errors
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3002 Better report invalid resource attribute errors Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title
Eric Thompson assigned an issue to qa
Puppet / PUP-5578
parse_string doesnt interpolate %{key} with Puppet 4.0
Change By:
Eric Thompson
Status:
Ready for CI Test
Assignee:
qa
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5509) No error context when a non-numeric index is used on a string
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-5509 No error context when a non-numeric index is used on a string Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-5502 lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5554) Improve lexer speed on jruby
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-5554 Improve lexer speed on jruby Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-163) Array/list support for "IN" operator for matching against a list of possible items
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-163 Array/list support for "IN" operator for matching against a list of possible items Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Charlie Sharpsteen assigned an issue to Unassigned Puppet / PUP-686 --detailed-exit-codes not honored when --noop is used Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1387) Support data anonymization at the storage level
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-1387 Support data anonymization at the storage level Change By: Owen Rodabaugh Comment: [~rachel] [~beth.cornils] May be the product owner. I'm not aware of any near term work on this however. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5582) Enforce "no return in ensure block" rubocop
Title: Message Title Kylo Ginsberg commented on PUP-5582 Re: Enforce "no return in ensure block" rubocop On further reflection, I'm going to close this ticket. I misunderstood what ruby does and what the checker does. From https://github.com/bbatsov/rubocop/issues/60, I found this description of the checker: Never return from an ensure block. If you explicitly return from a method inside an ensure block, the return will take precedence over any exception being raised, and the method will return as if no exception had been raised at all. In effect, the exception will be silently thrown away. However, I tried this snippet with both ruby 1.9.3 and ruby 2.2.0 and the exception is actually raised. def thing 42 ensure raise Exception return "something else" end and it results in, say: Exception: Exception
Jira (PUP-5061) Always restore full trusted information from store
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5061 Always restore full trusted information from store Change By: Kylo Ginsberg Fix Version/s: PUP 4.x Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5589) Type without namevar causes failures with no error
Title: Message Title Hunter Haugen created an issue Puppet / PUP-5589 Type without namevar causes failures with no error Issue Type: Bug Assignee: Unassigned Created: 2015/12/08 9:05 PM Priority: Normal Reporter: Hunter Haugen When trying to compile a catalog with a resource type that does not have a namevar specified in the type (ie, no parameter with `:namevar => true` and no `isnamevar` call) then the puppet run will exit 1 as soon as the catalog compile is finished with no back trace, error message, or any other indicator that anything is wrong. This makes it extremely difficult to debug (ie, guessing at what is missing). Add Comment This message was sent by Atlassian JIRA (v6.4
Jira (FACT-1283) facter --puppet doesn't load plugin synced facts in PE 2015.3
Title: Message Title Jeff McCune created an issue Facter / FACT-1283 facter --puppet doesn't load plugin synced facts in PE 2015.3 Issue Type: Bug Affects Versions: FACT 3.1.3 Assignee: Unassigned Created: 2015/12/08 9:45 PM Priority: Normal Reporter: Jeff McCune I'm working on site with $customer, and I'm running into the following strange behavior with diagnosing a custom fact synchronized via pluginsync to a PE 2015.3 agent. The impact data is that this fact affects all of the puppet manifests for $customer and they're a paying PE customer. They're evaluating the work required to upgrade from 3.8.x to 2015.x. Expected behavior: After a successful puppet agent -t run that synchronizes a single custom fact located at /etc/puppetlabs/code/environments/production/modules/plugins/lib/facter/apache.rb, $customer wants to debug why the fact value is not what they expect it to be, so they run facter --puppet expecting to see a value for a fact named apache_exists. Actual behavior: No such fact exists, implying the synchronized fact is loaded. Additional steps to reproduce: Install pry using sudo /opt/puppetlabs/puppet/bin/gem install pry --no-ri --no-rdoc. Place require 'pry'; binding.pry; in the first line of the custom fact. Synchronize the fact with puppet agent -t, observe Puppet dropping into a Pry REPL. Try facter --puppet and observe no REPL behavior, implying the fact is not loaded.
Jira (FACT-1283) facter --puppet doesn't load plugin synced facts in PE 2015.3
Title: Message Title
Jeff McCune updated an issue
Facter / FACT-1283
facter --puppet doesn't load plugin synced facts in PE 2015.3
Change By:
Jeff McCune
I'm working on site with $customer, and I'm running into the following strange behavior with diagnosing a custom fact synchronized via pluginsync to a PE 2015.3 agent. The impact data is that this fact affects all of the puppet manifests for $customer and they're a paying PE customer. They're evaluating the work required to upgrade from 3.8.x to 2015.x.Expected behavior:After a successful puppet agent -t run that synchronizes a single custom fact located at {{/etc/puppetlabs/code/environments/production/modules/plugins/lib/facter/apache.rb}}, $customer wants to debug why the fact value is not what they expect it to be, so they run {{facter --puppet}} expecting to see a value for a fact named {{apache_exists}}.Actual behavior:No such fact exists, implying the synchronized fact is not loaded.Additional steps to reproduce:Install pry using {{sudo /opt/puppetlabs/puppet/bin/gem install pry --no-ri --no-rdoc}}. Place {{require 'pry'; binding.pry;}} in the first line of the custom fact. Synchronize the fact with {{puppet agent -t}}, observe Puppet dropping into a Pry REPL. Try {{facter --puppet}} and observe no REPL behavior, implying the fact is not loaded.Additional steps to conform inform the hypothesis :Manually augmenting the ruby load path evaluates the custom fact from the pluginsync location:{code}vagrant@vagrant-ubuntu-trusty-64:~$ RUBYLIB=/opt/puppetlabs/puppet/cache/lib facter -p2015-12-09 05:44:09.019021 WARN puppetlabs.facter - skipping external facts for "/home/vagrant/.puppetlabs/opt/puppet/cache/facts.d": No such file or directoryHistory file not loaded: Permission denied @ rb_sysopen - /home/vagrant/.pry_historyFrom: /opt/puppetlabs/puppet/cache/lib/facter/apache.rb @ line 1 : => 1: require 'pry'; binding.pry;2: Facter.add(:apache_exists) do...{code}This seems related to FACT- and FACT-96
Add Comment
This m
