Jira (FACT-1118) Add 'noatime' option to mountpoint fact
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1118 Add 'noatime' option to mountpoint fact Issue Type: Improvement Affects Versions: FACT 3.0.1 Assignee: Unassigned Components: Community Created: 2015/07/13 1:46 AM Environment: OpenBSD 5.8 Priority: Normal Reporter: Jasper Lievisse Adriaanse The mountpoints fact could be improved to also list the 'noatime' field for 'options'. I didn't guard it with an ifdef as it seems all systems I check have it (Linux, AIX, FreeBSD, OpenBSD).
Jira (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title Fabrice Bacchella commented on FACT-184 Re: Using 'ip addr' over ifconfig You don't intent to fixe it until facter 3 is out ? The current interfaces fact implementation is broken in many way : it still uses ifconfig, which is broken in linux since years it launch ifconfig in a wrong way: sh, -c, /sbin/ifconfig -a 2/dev/null, why fork a shell for that ? it's result are wrong, because ifconfig is deprecated, and ifconfig confuse interfaces and ip address, On a RHEL7, if you have two IP on the same interface, ifconfig gives : bond0: flags=5187UP,BROADCAST,RUNNING,MASTER,MULTICAST mtu 1500 ... bond0:git: flags=5187UP,BROADCAST,RUNNING,MASTER,MULTICAST mtu 1500 ... But ip link list, /proc/net/dev, snmp only see bond0, so the bond0_git interface is unusable in many ways. Add Comment
Jira (PUP-1531) Puppet Master unable to find module if the directory is a symlink
Title: Message Title Andreas Sieferlinger commented on PUP-1531 Re: Puppet Master unable to find module if the directory is a symlink This is also still an issue with puppet 3.8.1. Has anybody found a way to use symlinks in the modules directory? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-930) Bad library dependency when building for FreeBSD
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-930 Re: Bad library dependency when building for FreeBSD In order to resolve this ticket the handling I added for OpenBSD will need to be expanded for FreeBSD too. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1118) Add 'noatime' option to mountpoint fact
Title: Message Title Jasper Lievisse Adriaanse updated an issue Facter / FACT-1118 Add 'noatime' option to mountpoint fact Change By: Jasper Lievisse Adriaanse Themountpointsfactcouldbeimprovedtoalsolistthe'noatime'fieldfor'options'.Ididn'tguarditwithanifdefasitseemsallsystemsIcheckhaveit(Linux,AIX,FreeBSD,OpenBSD). When#1081isresolvedIwillsubmitthePR. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1758) PR (64): Bump project version and PDB dependency to 3.0.1-SNAPSHOT - senior
Title: Message Title gepetto-bot commented on PDB-1758 Re: PR (64): Bump project version and PDB dependency to 3.0.1-SNAPSHOT - senior senior commented: I switched from the git command I was using to determine branch to use the TRAVIS_BRANCH environment variable. Travis tests are green now. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1751) PR (1528): [PDB 135] improve utf8 warning - kronn
Title: Message Title gepetto-bot commented on PDB-1751 Re: PR (1528): [PDB 135] improve utf8 warning - kronn kronn commented: @ajroetker I adapted the specs in the least way possible to make them green again. I am looking forward to a review of this (and to the code potentially being torn apart because I missed something). Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1751) PR (1528): [PDB 135] improve utf8 warning - kronn
Title: Message Title gepetto-bot commented on PDB-1751 Re: PR (1528): [PDB 135] improve utf8 warning - kronn kbarber commented: Oh yeah, this should be targeted at master, as its a new feature, stable should be mainly for bug fixes and this is probably too intrusive a change to fit that label. You'll need to re-open this PR unfortunately to do that, should have mentioned this before I commented on it, nevermind. When you reopen it just be mindful of the comments I've made, and reference this original PR somewhere in a comment or something. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1751) PR (1528): [PDB 135] improve utf8 warning - kronn
Title: Message Title gepetto-bot commented on PDB-1751 Re: PR (1528): [PDB 135] improve utf8 warning - kronn Pull request [PDB 135] improve utf8 warning has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1751) PR (1528): [PDB 135] improve utf8 warning - kronn
Title: Message Title gepetto-bot commented on PDB-1751 Re: PR (1528): [PDB 135] improve utf8 warning - kronn kbarber commented: @kronn I don't mind the direction this patch is taking, but I'm wary of rushing this so we'll need to ponder it some more and at the very least get this code into shape a bit, it's a great start though. Some general notes: The use of this facility should probably be documented, at least in a FAQ entry perhaps. See documentation/ Use of diff can be risky, see my comment. The pathing locations for the content needs to be considered more, /tmp isn't a great place. The use of flock feels like a smell, this needs to be reconsidered. Permissions are too permissive. The code needs rspec tests, we couldn't take on anything like this without at least rspec tests. We document our methods and code with yarddoc, this will need to be done across the board: http://www.rubydoc.info/gems/yard/file/docs/Tags.md FWIW our convention for commits is (PDB-135) not [PDB 135], we have bots that rely on this stuff now, so its worth fixing. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4654) Create acceptance for custom facts using puppet facts face
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-4654 Create acceptance for custom facts using puppet facts face Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4855) recurse setting for folders with templates
Title: Message Title Oded Simon commented on PUP-4855 Re: recurse setting for folders with templates Hi Henrik, When creating folder with puppet I can add the option recurse so it will track all changes done in the folder as log as the option source is set. https://docs.puppetlabs.com/references/latest/type.html#file-attribute-recurse The recurse do not work with the content (call for template folder). as result if the content of a folder are templated in puppet, I need to specify each file separately. Can the recurse option work with templates? regards Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-420) Deep merging not working with Hiera 3.0
Title: Message Title Sivakalyan Chintakana created an issue Hiera / HI-420 Deep merging not working with Hiera 3.0 Issue Type: Bug Affects Versions: HI 3.0.1 Assignee: Unassigned Created: 2015/07/13 10:44 PM Environment: CentOS 7 64 bit Puppet server 2.1.1 Puppet 4.2 Puppet agent 1.2.1 Hiera 3.0.1 Priority: Major Reporter: Sivakalyan Chintakana Hi, 1. I've enabled deep merging in hiera.yaml. --- :backends:
Jira (HI-420) Deep merging not working with Hiera 3.0.1
Title: Message Title Sivakalyan Chintakana updated an issue Hiera / HI-420 Deep merging not working with Hiera 3.0.1 Change By: Sivakalyan Chintakana Summary: DeepmergingnotworkingwithHiera3.0 .1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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
Tim Stibbs commented on PUP-4495
Re: Puppet 3.5.0 introduced a regression in tag filtering for catalog runs
Note that the exact issue reported above seems to have been fixed in puppet 4.0, but still exists if using hiera. E.g.
# tag_test.pp
hiera_include('classes')
class test::step1 {
file { '/tmp/test1.txt':
ensure = 'file',
}
}
class test::step2 {
Jira (PDB-1760) PR (1534): (RE-5033) Update Ezbake to new 0.3.14 - stahnma
Title: Message Title gepetto-bot commented on PDB-1760 Re: PR (1534): (RE-5033) Update Ezbake to new 0.3.14 - stahnma Pull request (RE-5033) Update Ezbake to new 0.3.14 has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4855) recurse setting for folders with templates
Title: Message Title Henrik Lindberg assigned an issue to Oded Simon Puppet / PUP-4855 recurse setting for folders with templates Change By: Henrik Lindberg Assignee: KyloGinsberg OdedSimon Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4855) recurse setting for folders with templates
Title: Message Title Henrik Lindberg commented on PUP-4855 Re: recurse setting for folders with templates Can you describe what you tried/want and how that is expected to work? Do you want to specify that files recursively should get content from different templates? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4856) Overriding resource attributes doesn't work through the ENC
Title: Message Title
Sam Cannell created an issue
Puppet / PUP-4856
Overriding resource attributes doesn't work through the ENC
Issue Type:
Bug
Affects Versions:
PUP 4.2.0, PUP 3.4.2
Assignee:
Unassigned
Components:
Language
Created:
2015/07/13 6:58 PM
Environment:
Reproduced on Ubuntu Trusty running both Puppet 3.4.2 (from deb package) and 4.2.0 (from git)
Used a simple shell script for the ENC:
{{ #!/bin/bash cat EOT classes:
override EOT }}
Priority:
Normal
Reporter:
Sam Cannell
Consider the following setup, with a defined type and two classes:
{{ define defined_type_test($value) { notify { message_$ {title}
Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error in PE
Title: Message Title Henrik Lindberg commented on PUP-4848 Re: Global parser = future with environment.conf parser = current gives an error in PE Oh duh, think I found it - it is not enough to just use Puppet[:parser] == 'future' Since that only checks the main setting. The correct way to check is Puppet.future_parser? I found one such faulty check in the code path for collectors. Will vacuum for others. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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
Jira (PUP-4856) Overriding resource attributes doesn't work through the ENC
Title: Message Title
Sam Cannell updated an issue
Puppet / PUP-4856
Overriding resource attributes doesn't work through the ENC
Change By:
Sam Cannell
Environment:
ReproducedonUbuntuTrustyrunningbothPuppet3.4.2(fromdebpackage)and4.2.0(fromgit)UsedasimpleshellscriptfortheENC:{{ #!/bin/bashcatEOTclasses:-overrideEOT }}
Considerthefollowingsetup,withadefinedtypeandtwoclasses:{{ definedefined_type_test($value){notify{message_${title}:message=$value,}}classbase{defined_type_test{'foo':value='OriginalMessage',}}classoverride{Defined_type_test|title=='foo'|{value='OverriddenMessage',}} }}Whenbothclassesarecalledvia'nodedefault',itworksasexpected--The'message_foo'notifyemits'OverriddenMessage'.However,whentheclass'base'iscalledvia'nodedefault',andtheclass'override'iscalledviatheENC,'message_foo'emits'OriginalMessage'.The'override'classisdefinitelybeingexecuted;otherresourcesaddedtotheclassareappliedwithoutissues.Likewise,onlyresourcesthatareinstancesofdefinedtypesareaffected.Overridinganattributeofa'real'typeworksfinefromaclasscalledviatheENC.AsbestIcantell,thisonlyoccurswhenallofthefollowingaretrue:*You'reattemptingtooverrideanattributeonaresourcethatisaninstanceofadefinedtype*Theresourceiscreatedinaclassthatiscalledviamanifests/site.pp*ThecollectortooverridetheattributeisinaclassthatiscalledviatheENC(notnecessarilydirectly;thisalsoholdsifanintermediateclassiscalledfromtheENC,whichinturncallstheclasscontainingtheoverride)
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4856) Overriding resource attributes doesn't work through the ENC
Title: Message Title
Sam Cannell updated an issue
Puppet / PUP-4856
Overriding resource attributes doesn't work through the ENC
Change By:
Sam Cannell
Environment:
ReproducedonUbuntuTrustyrunningbothPuppet3.4.2(fromdebpackage)and4.2.0(fromgit)UsedasimpleshellscriptfortheENC: {{ #!/bin/bashcatEOTclasses:-overrideEOT }}
Considerthefollowingsetup,withadefinedtypeandtwoclasses: {{ definedefined_type_test($value){notify{message_${title}:message=$value,}}classbase{defined_type_test{'foo':value='OriginalMessage',}}classoverride{Defined_type_test|title=='foo'|{value='OverriddenMessage',}} }} Whenbothclassesarecalledvia'nodedefault',itworksasexpected--The'message_foo'notifyemits'OverriddenMessage'.However,whentheclass'base'iscalledvia'nodedefault',andtheclass'override'iscalledviatheENC,'message_foo'emits'OriginalMessage'.The'override'classisdefinitelybeingexecuted;otherresourcesaddedtotheclassareappliedwithoutissues.Likewise,onlyresourcesthatareinstancesofdefinedtypesareaffected.Overridinganattributeofa'real'typeworksfinefromaclasscalledviatheENC.AsbestIcantell,thisonlyoccurswhenallofthefollowingaretrue:*You'reattemptingtooverrideanattributeonaresourcethatisaninstanceofadefinedtype*Theresourceiscreatedinaclassthatiscalledviamanifests/site.pp*ThecollectortooverridetheattributeisinaclassthatiscalledviatheENC(notnecessarilydirectly;thisalsoholdsifanintermediateclassiscalledfromtheENC,whichinturncallstheclasscontainingtheoverride)
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4856) Overriding resource attributes doesn't work through the ENC
Title: Message Title
Sam Cannell updated an issue
Puppet / PUP-4856
Overriding resource attributes doesn't work through the ENC
Change By:
Sam Cannell
Considerthefollowingsetup,withadefinedtypeandtwoclasses: {noformat} definedefined_type_test($value){notify{message_${title}:message=$value,}}classbase{defined_type_test{'foo':value='OriginalMessage',}}classoverride{Defined_type_test|title=='foo'|{value='OverriddenMessage',}} {noformat} Whenbothclassesarecalledvia'nodedefault',itworksasexpected--The'message_foo'notifyemits'OverriddenMessage'.However,whentheclass'base'iscalledvia'nodedefault',andtheclass'override'iscalledviatheENC,'message_foo'emits'OriginalMessage'.The'override'classisdefinitelybeingexecuted;otherresourcesaddedtotheclassareappliedwithoutissues.Likewise,onlyresourcesthatareinstancesofdefinedtypesareaffected.Overridinganattributeofa'real'typeworksfinefromaclasscalledviatheENC.AsbestIcantell,thisonlyoccurswhenallofthefollowingaretrue:*You'reattemptingtooverrideanattributeonaresourcethatisaninstanceofadefinedtype*Theresourceiscreatedinaclassthatiscalledviamanifests/site.pp*ThecollectortooverridetheattributeisinaclassthatiscalledviatheENC(notnecessarilydirectly;thisalsoholdsifanintermediateclassiscalledfromtheENC,whichinturncallstheclasscontainingtheoverride)
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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
Jira (PUP-4856) Overriding resource attributes doesn't work through the ENC
Title: Message Title
Sam Cannell updated an issue
Puppet / PUP-4856
Overriding resource attributes doesn't work through the ENC
Change By:
Sam Cannell
Environment:
ReproducedonUbuntuTrustyrunningbothPuppet3.4.2(fromdebpackage)and4.2.0(fromgit)UsedasimpleshellscriptfortheENC: {noformat} #!/bin/bash catEOTclasses:-overrideEOT {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4819) Add service for obtaining class information per environment
Title: Message Title
Henrik Lindberg commented on PUP-4819
Re: Add service for obtaining class information per environment
Note that in Puppet 4 data values include literal default, and regular expressions - these may appear in the returned hash. If the end result is to be represented in JSON, there needs to be some encoding of the special values.
Puppet
Ruby
undef
nil
default
:default
/.*/
/.*/
Also note that there is no distinction between bare words and strings, and there is no difference between single and double quoted values. As an example:
class($a = x, $b = 'x', $c = x) { }
Will return the three parameters a, b, and c, and they will all have the same string value: a Ruby string x.
Double quoted strings with interpolation are not considered to be literal. A double quoted string without interpolation is.
Jira (PUP-1499) Puppet open source Windows packages should include mcollective
Title: Message Title Josh Cooper commented on PUP-1499 Re: Puppet open source Windows packages should include mcollective C Lang Starting with puppet 4, we now have a unified agent installer (puppet-agent) for both open source and PE, and it includes mcollective. See the release notes at: http://docs.puppetlabs.com/puppet/latest/reference/ You can download the latest puppet-agent version here: https://downloads.puppetlabs.com/windows/puppet-agent-x64-latest.msi. Note puppet-agent does not include mcollective plugins, but you can use puppet to bootstrap mcollective plugins and mcollective configuration. I'm going to close the ticket, but please comment on the ticket if something isn't right. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-716) Puppet 3.7.1 Agent on Windows blocks for 20 seconds trying to connect to ec2 metadata service on xen hypervisors
Title: Message Title Josh Cooper assigned an issue to Ian Au Facter / FACT-716 Puppet 3.7.1 Agent on Windows blocks for 20 seconds trying to connect to ec2 metadata service on xen hypervisors Change By: Josh Cooper Assignee: IanAu Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-716) Puppet 3.7.1 Agent on Windows blocks for 20 seconds trying to connect to ec2 metadata service on xen hypervisors
Title: Message Title Josh Cooper commented on FACT-716 Re: Puppet 3.7.1 Agent on Windows blocks for 20 seconds trying to connect to ec2 metadata service on xen hypervisors Jason Greathouse Ian Au Etienne Lacombe Starting in puppet 4.2, we ship puppet with a native facter implementation. It uses a 200ms connection timeout: https://github.com/puppetlabs/facter/blob/master/lib/src/facts/resolvers/ec2_resolver.cc#L36 Can you verify if the issue is resolved using puppet-agent 1.2.x, which contains puppet 4.2.x facter 3.0.x? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-604) Fact domainname does hostname no-op call on windows
Title: Message Title Josh Cooper commented on FACT-604 Re: Fact domainname does hostname no-op call on windows facter has been rewritten in C++ and we no longer shell out to the hostname.exe executable, instead calling Win32 APIs to retrieve the hostname and domain names, e.g. see https://github.com/puppetlabs/facter/blob/master/lib/src/facts/windows/networking_resolver.cc#L155. I'm going to mark this as won't fix, since we won't be patching the ruby facter implementation. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4847) Custom facts not loaded when using puppet resource command
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Puppet / PUP-4847 Custom facts not loaded when using puppet resource command Change By: Shaigy Nixon Assignee: qa ShaigyNixon Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1119) Add Mac OS X facts test
Title: Message Title Michael Smith created an issue Facter / FACT-1119 Add Mac OS X facts test Issue Type: Task Assignee: Unassigned Created: 2015/07/13 10:43 AM Priority: Normal Reporter: Michael Smith We have acceptance tests for core facts on most systems we ship. We should add them for Mac OS X as well. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4476) Add a 'puppet lookup' command line application as UI to lookup function
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-4476 Add a 'puppet lookup' command line application as UI to lookup function Change By: Hailee Kenney Assignee: HaileeKenney Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1721) Possible Memory leak with PuppetDB?
Title: Message Title Richard Chatterton updated an issue PuppetDB / PDB-1721 Possible Memory leak with PuppetDB? I've also attached a screenshot showing the change in metrics over time of a typical case. The data source for all of these metrics is the /v3/metrics/mbean API endpoint of PuppetDB. Represented here, the blue line is the average statement execution time, the purple line is the StatementsCached metric, the green line is the committed heap, and the red line is the used heap. Note that the values have been scaled so that they can be clearly seen on the same graph. We can see that, from the time when PuppetDB was started at ~1230, the committed heap roughly follows the increases in the StatementsCached metric. We run Puppet once an hour at the start of every hour across all nodes in the population, and most of the increases in StatementsCached occur at this time, at a rate of about 1k per hour. This begins to fall off as the used heap begins to approach the maximum heap of 3 GB. The execution time becomes very long as performance begins to degrade, and garbage collections are not freeing up much space as time passes. Gaps in the metrics are likely due to PuppetDB's metric endpoints becoming intermittently unresponsive as the situation becomes worse, until it eventually crashes at ~0400. Change By: Richard Chatterton Attachment: puppetdb-metrics.png Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PDB-1764) PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr
Title: Message Title gepetto-bot commented on PDB-1764 Re: PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr rbrw commented: Looks right to me. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1764) PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1764 PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr Issue Type: Task Assignee: Unassigned Created: 2015/07/13 11:53 AM Labels: github Priority: Normal Reporter: gepetto-bot (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT Author: wayne Company: Github ID: waynr Pull Request 65 Discussion Pull Request 65 File Diff Pull Request Description The use of a release version has been leading to failures during the Lein EZBake job in CI. (webhooks-id: 69a30397ff231e0dfde1da94cd025e08)
Jira (PDB-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title gepetto-bot commented on PDB-1763 Re: PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1648/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1764) PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr
Title: Message Title gepetto-bot commented on PDB-1764 Re: PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr wkalt commented: failing travis...haven't looked into why yet Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1764) PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr
Title: Message Title gepetto-bot commented on PDB-1764 Re: PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr Pull request (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1764) PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr
Title: Message Title gepetto-bot commented on PDB-1764 Re: PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr waynr commented: Closing because #64 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title gepetto-bot commented on PDB-1763 Re: PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1647/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1118) Add 'noatime' option to mountpoint fact
Title: Message Title Jasper Lievisse Adriaanse commented on FACT-1118 Re: Add 'noatime' option to mountpoint fact pull request Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4634) Add some timings/metrics in report
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4634 Add some timings/metrics in report Change By: Josh Cooper Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1764) PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr
Title: Message Title gepetto-bot commented on PDB-1764 Re: PR (65): (MAINT) Bump pd-pdb and pdb versions to 3.0.1-SNAPSHOT - waynr ajroetker commented: This is done by https://github.com/puppetlabs/pe-puppetdb-extensions/pull/64 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title gepetto-bot commented on PDB-1763 Re: PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt wkalt commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title gepetto-bot commented on PDB-1763 Re: PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1649/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1763 PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/07/13 10:46 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) update preinst for redhat to check for 2.x if upgrading Author: Wyatt Alt Company: Github ID: wkalt Pull Request 1537 Discussion Pull Request 1537 File Diff Pull Request Description This should fix the issue where we attempted to tar a nonexistent directory in preinst when upgrading from 3.0.0 - 3.0.x (webhooks-id:
Jira (PUP-4476) Add a 'puppet lookup' command line application as UI to lookup function
Title: Message Title
Hailee Kenney updated an issue
Puppet / PUP-4476
Add a 'puppet lookup' command line application as UI to lookup function
Change By:
Hailee Kenney
Inordertosupportdatainmodulesandenvironmentandbeabletotestanddebugadataconfigurationitisimportanttohaveacommandlineutilitythatcanhelpanswerquestionsaboutwhichvaluewill be producedforagivenkey,andhowdidthesystemarriveatthatvalue.Thisnewcommandlineutilitysupplantstheexisting{{hiera}}commandlinetoolsinceitisnotawareofdata-in-modules,andcannotperformcrosslookups/mergeslikethelookupfunctionalitycan.Thus,the{{puppetlookup}}commandisbasicallyaUIforthelookupfunction,withtheaddedfeaturethatitcanrequestanddisplayanexplanation(seePUP-4475).Theapplicationtakesoptionsforlookup:*--typeTYPESTRING-toassertthatvaluehasthattype*--merge=unique|hash|deep*--knock_out_prefix=prefix_string*--sort_merged_arrays*--unpack_arrays*--merge_hash_arrays*--explain-printsanexplanationforhowresultwasobtained*--default=VALUE-avalueproducedifnovaluewasfound(usefulifcommandisusedtosetashellvariableorsimilar)Theapplicationtakesoptionsforfacts/scope:*--nodenodename-looksupthefactsfromthefactsterminus*--factsfactfile-a.json,or.yamlfileholdingkey=valuemappingsthatwillpopulateascopewithdatathatisusedwhenlookingupFollowedbyoneormorekeystolookup,thefirstfoundisreturned.Ifmultiplevaluesaregiven,explanationsareproducedforeachkeyupto(andincluding)thefirstfoundvalue.Exitswith0ifvaluewasfound(ordefaultvaluewasusedifvaluewasnotfound),and1otherwise.Tocompletetheimplementationofthe--explainfeature,PUP-4475mustbeimplemented.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (FACT-1112) Move curl wrapper functions to Leatherman
Title: Message Title Michael Smith commented on FACT-1112 Re: Move curl wrapper functions to Leatherman This ticket should be FRed in ec2/gce to verify functionality still works. I'll volunteer to do that. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4752) Uppercase letters in parameter variable names
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4752 Uppercase letters in parameter variable names Change By: Eric Thompson Assignee: qa EricThompson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4752) Uppercase letters in parameter variable names
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4752 Uppercase letters in parameter variable names Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1119) Add Mac OS X facts test
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-1119 Add Mac OS X facts test Change By: William Hopper Assignee: WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4799) Documentation lacks puppet requirement in metadata.json
Title: Message Title Ben Ford updated an issue Puppet / PUP-4799 Documentation lacks puppet requirement in metadata.json Change By: Ben Ford The [ moduledevelopmentdocumentation |https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#write-a-metadatajson-file] doesnotmentionhowtoconstrainpuppetversionrequirementsusingtherequirementkeyinmetadata.json .Anexampleofthiskey'susagecanbeseenathttps://github.com/puppetlabs/puppetlabs-stdlib/blob/master/metadata.json#L100 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1758) PR (64): Bump project version and PDB dependency to 3.0.1-SNAPSHOT - senior
Title: Message Title gepetto-bot commented on PDB-1758 Re: PR (64): Bump project version and PDB dependency to 3.0.1-SNAPSHOT - senior ajroetker commented: I'm :+1:, @rbrw? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1721) Possible Memory leak with PuppetDB?
Title: Message Title
Richard Chatterton commented on PDB-1721
Re: Possible Memory leak with PuppetDB?
We're seeing a similar issue. After upgrading to 2.3.5-1, PuppetDB is crashing roughly every 12 to 24 hours with java.lang.OutOfMemoryError: GC overhead limit exceeded. Analyzing the heap dumps from these crashes with Java VisualVM, we see that there are ~11,000 instances of org.postgresql.jdbc4.Jdbc4PreparedStatement. The shallow size of these objects is roughly 2 MB, however using a OQL query that should return the sum of the retained sizes of each of these objects, we see that together they are using about 3 GB of heap. This PuppetDB installation currently has -Xmx3072.
Query: select sum(heap.objects('org.postgresql.jdbc4.Jdbc4PreparedStatement'), 'rsizeof(it)')
Result: 3.390594731E9
In an attempt to solve this, we're trying setting the statements-cache-size configuration parameter to 500, which should be half of the default documented value of 1000. If this helps, we'll update this ticket with that information.
Some additional information: This PuppetDB environment contains 912 nodes, with ~142k resources in the population. We are making use of a few relatively large structured facts, which necessitated our upgrade from 2.2.x to 2.3.5-1. We started with a fresh database in 2.3.5-1 due to schema issues in the upgrade. We can provide the hprof I referenced, if that would be helpful.
Add Comment
Jira (PUP-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Josh Cooper commented on PUP-2789 Re: critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Clement XaT can you provide the manifest showing the group resource Ethan Brown was mentioning? Can you reproduce the issue using only the group resource? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Eric Thompson Assignee: qa EricThompson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-184) Using 'ip addr' over ifconfig
Title: Message Title Kylo Ginsberg commented on FACT-184 Re: Using 'ip addr' over ifconfig Fabrice Bacchella: facter 3.0 was released and is packaged with the last few puppet-agent builds: https://groups.google.com/forum/#!topic/puppet-users/gnUUUIZcdVo Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4654) Create acceptance for custom facts using puppet facts face
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-4654 Create acceptance for custom facts using puppet facts face Change By: William Hopper Assignee: qa WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Hailee Kenney assigned an issue to qa Facter / FACT- deprecation of 'facter --puppet' removes critically necessary functionality Change By: Hailee Kenney Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1113) Move dlopen wrapper class to Leatherman
Title: Message Title Hailee Kenney assigned an issue to qa Facter / FACT-1113 Move dlopen wrapper class to Leatherman Change By: Hailee Kenney Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4847) Custom facts not loaded when using puppet resource command
Title: Message Title Hailee Kenney assigned an issue to qa Puppet / PUP-4847 Custom facts not loaded when using puppet resource command Change By: Hailee Kenney Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 Charlie Sharpsteen updated an issue Puppet / PUP-4495 Puppet 3.5.0 introduced a regression in tag filtering for catalog runs This issue is still present in the latest releases of both the 3.x and 4.x branches. Change By: Charlie Sharpsteen Affects Version/s: PUP3.8.0 Affects Version/s: PUP3.7.5 Affects Version/s: PUP3.6.2 Affects Version/s: PUP4.0.0 Affects Version/s: PUP3.8.1 Affects Version/s: PUP4.2.0 Add Comment
Jira (PDB-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title gepetto-bot commented on PDB-1763 Re: PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt Pull request (maint) update preinst for redhat to check for 2.x if upgrading has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4847) Custom facts not loaded when using puppet resource command
Title: Message Title Shaigy Nixon commented on PUP-4847 Re: Custom facts not loaded when using puppet resource command Validated on redhat-6-x86_64 SHA=a0f4030a10eb873538c25d105ec822dbab44840c. Installed puppetlabs-firewall module and created a firewall resource. #puppet module install puppetlabs-firewall [root@nnxiotspfan5q3a ~]# ls /etc/puppetlabs/code/environments/production/modules/ firewall [root@nnxiotspfan5q3a ~]# puppet resource firewall --trace --debug | grep iptables_version Debug: Facter: searching for custom fact iptables_version. Debug: Facter: searching for iptables_version.rb in /etc/puppetlabs/code/environments/production/modules/firewall/lib/facter. Info: Facter: loading custom facts from /etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rb. Debug: Facter: fact iptables_version has resolved to 1.4.7.
Jira (FACT-1115) Treats non-zero responses as failures
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1115 Treats non-zero responses as failures Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Eric Thompson commented on PUP-4810 Re: Puppet caches parse results when environment_timeout is set to 0 LGTM charlie's VERY good reproduction and monitoring case above on ubuntu 14.04 at puppet-agent SHA: 3d61cd62d0ab9d94c06e1659890125a46f998f11 (puppet stable) # in /etc/sysconfig/puppetserver: JAVA_ARGS=-Xms2048m -Xmx2560m -XX:MaxPermSize=256m -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port= -Dcom.sun.management.jmxremote.local._only_=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=d92opdvgw5mehtr.delivery.puppetlabs.net #restart puppetserver connect from test-runner (osx) using jvisualvm Add Comment
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Eric Thompson Attachment: ScreenShot2015-07-13at1.36.39PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1758) PR (64): Bump project version and PDB dependency to 3.0.1-SNAPSHOT - senior
Title: Message Title gepetto-bot commented on PDB-1758 Re: PR (64): Bump project version and PDB dependency to 3.0.1-SNAPSHOT - senior Pull request Bump project version and PDB dependency to 3.0.1-SNAPSHOT has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title gepetto-bot commented on PDB-1763 Re: PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt mullr commented: ... this was just merged into master. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4826) meaning of Integer[0] different in a ruby function
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Puppet / PUP-4826 meaning of Integer[0] different in a ruby function Change By: Shaigy Nixon Assignee: qa ShaigyNixon Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4752) Uppercase letters in parameter variable names
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4752 Uppercase letters in parameter variable names Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1721) Possible Memory leak with PuppetDB?
Title: Message Title Richard Chatterton commented on PDB-1721 Re: Possible Memory leak with PuppetDB? Wyatt, thanks for your follow up. We're collecting a 'packages' fact, which is an array of the full package strings for all packages on the system. On an EL system, it's essentially the output of rpm -qa as an array. For a typical example, this array is 716 elements long and ~30K on disk, serialized as JSON. Initially, this was a nested map with more information, but (particularly on 2.2.x), we found that it was not performant enough and switched to a simpler format. Each of our 912 nodes are reporting this fact on every run. At this time, I'm not certain if PuppetDB has a concept of ordered arrays in structured facts, or if rpm -qa returns the list of packages in the same order every time – if the fact value is an array with the same members in a different order, would that cause an update? We're currently running our PuppetDB with statements-cache-size = 500, and from the metrics we can see at this time, it looks like it will likely die within the next few hours. In the event it does die, we'll try running it with statements-cache-size = 100, as you suggest. The hprof I referenced is 3.5 GB in size, so I imagine you probably don't want me attaching it directly to this issue. Is there somewhere to which we can upload it? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1721) Possible Memory leak with PuppetDB?
Title: Message Title Wyatt Alt commented on PDB-1721 Re: Possible Memory leak with PuppetDB? Simon Oxwell Richard Chatterton thanks for reporting this. It's pretty clear that there's an issue here but we've been wrapped up in release related stuff and haven't had a chance to delve just yet. I tried to replicate this about a week ago and found that the number of instances of org.postgresql.jdbc4.Jdbc4PreparedStatement seemed to grow unaffected by reductions in statements-cache-size and forced garbage collection, but when I left my simulation running overnight the number of instances seemed to top out around 2500 and the retained size never grew beyond 5% of my 750mb heap. Both of your retained sizes are massive in comparison. Richard Chatterton thanks for your note about large structured facts. I remember from PDB-1448 that Simon Oxwell also uses large structured facts, and I'm sure that larger facts imply larger retained size. If that were the issue, it would explain why we're not seeing this from everyone. Any information you can give us on the size and structure of those facts (i.e array of maps, map of arrays, etc.) would be helpful. I'll repeat my experiment with some large facts in a little while, but in the meantime if you have that hprof dump handy it would definitely be nice to have. Richard, given that you're seeing this frequently it would also be interesting to know if dramatically reducing that cache size has any effect for you. Maybe even something like 100. Wyatt Add Comment This message was sent by
Jira (PDB-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title gepetto-bot commented on PDB-1763 Re: PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1650/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4752) Uppercase letters in parameter variable names
Title: Message Title
Eric Thompson commented on PUP-4752
Re: Uppercase letters in parameter variable names
validated on ubuntu 14.04 at puppet-agent SHA: 3d61cd62d0ab9d94c06e1659890125a46f998f11
# two uses, two errors, as expected. note the \w is output correctly in the error message
[root@d92opdvgw5mehtr ~]# puppet apply -e '$Ateam=fail notify{$Ateam:}'
Error: Illegal variable name, The given name 'Ateam' does not conform to the naming rule /^((::)?[a-z]\w*)*((::)?[a-z_]\w*)$/ at line 1:1
Error: Illegal variable name, The given name 'Ateam' does not conform to the naming rule /^((::)?[a-z]\w*)*((::)?[a-z_]\w*)$/ at line 1:21
Error: Found 2 errors. Giving up
#no heading caps, caps in middle are fine, 12 errors expected:
[root@d92opdvgw5mehtr ~]# cat bad-names
class x ($Ateam='fail') {}
Jira (PUP-4752) Uppercase letters in parameter variable names
Title: Message Title
Eric Thompson commented on PUP-4752
Re: Uppercase letters in parameter variable names
mildly concerning due to different error message.
[root@d92opdvgw5mehtr ~]# cat bad-names
class x ($a-team='fail') {}
[root@d92opdvgw5mehtr ~]# puppet apply bad-names
Error: Could not parse for environment production: Syntax error at '-' at /root/bad-names:2:12 on node d92opdvgw5mehtr.delivery.puppetlabs.net
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
You received this message because you are subscribed to the Google
Jira (PUP-4752) Uppercase letters in parameter variable names
Title: Message Title Eric Thompson commented on PUP-4752 Re: Uppercase letters in parameter variable names Henrik Lindberg understood. i was just surprised that error took precedence. but if it's a bad-_expression_ at that point in the flow, that makes sense. the other comments shall should as validation. thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4853) Periodic environment test failures when agent lines run together?
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-4853 Periodic environment test failures when agent lines run together? Issue Type: Bug Assignee: Unassigned Created: 2015/07/13 3:51 PM Priority: Normal Reporter: Jeremy Barlow We have periodically experienced failures around some of the Puppet environment acceptance tests. The failures seem to happen when two lines of output from the agent run together where the test was expecting the lines to be separate. Usually, the second line which should be separate starts with text like Warning: Setting config_version is deprecated in puppet.conf. I'm not sure if this problem only happens when the tests are run on specific operating systems. The last couple of failures that I've seen were both on CentOS 7. Not sure if this is an agent or a test problem. I could make a case that the agent should always have the Warning... appear on its own line. — Examples from recent runs: From http://jenkins-enterprise.delivery.puppetlabs.net/view/puppet-server/view/all/job/enterprise_puppet-server_integration-system_no-conditional_full-stable/54/LAYOUT=64mdca,LDAP_TYPE=default,PLATFORM=centos7,label=beaker/testReport/junit/(root)/ruby_puppet_acceptance_tests_environment/directory_rb/: puppet_config: *UNEXPECTED FAILURE*
Jira (PUP-4854) DSC - Module Fails to Install from Forge
Title: Message Title Ethan Brown moved an issue Puppet / PUP-4854 DSC - Module Fails to Install from Forge Change By: Ethan Brown Component/s: dsc Component/s: Windows Component/s: PMT Key: MODULES PUP - 2221 4854 Project: ForgeModules Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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
Jira (PUP-4826) meaning of Integer[0] different in a ruby function
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4826
meaning of Integer[0] different in a ruby function
Change By:
Henrik Lindberg
UpdateTh4.xfunctionAPIcreatedtypesthatweremorerestrictivefor{{Integer}}and{{Float}}thanthecorrespondingexpressionsinthepuppetlanguage.Whenusing{{Integer\[1]}},theexpectationwasthatthisproducesthetype{{Integer\[1,default]}},butitproduced{{Integer\[1,1]}}.Thehandlingof{{Float}}hadthesameproblem.Afterthefix,thetypesinthe4.xfunctionAPIbehavesasdocumentedforthePuppetLanguage.Original Hi,Accordingto[thedocumentation|http://docs.puppetlabs.com/puppet/4.2/reference/lang_data_number.html#parameters],{code}Integer[0]{code}matchesanyintegergreaterthanorequalto0.Butthebehaviorisdifferentinarubyfunction.Hereisthecontentoftherubyfunction{{f.rb}}ina{{test}}puppetmodule:{code:ruby}#Thefunctionisinmodule-root/test/lib/puppet/functions/test/f.rbPuppet::Functions.create_function(:'test::f')dodispatch:fdorequired_param'Integer[0]',:nenddeff(n)trueendend{code}Then,ifItrytocallthefunctioninapuppetclasslikethis:{code:puppet}classtest{test::f(10)}{code}Ihavethiserror:{code}root@puppet4:~#puppetagent--testInfo:RetrievingpluginfactsInfo:RetrievingpluginInfo:LoadingfactsError:Couldnotretrievecatalogfromremoteserver:Error400onSERVER:EvaluationError:ErrorwhileevaluatingaFunctionCall,function'test::f'calledwithmis-matchedargumentsexpected:test::f(Integer[0,0]n)-argcount{1}actual:test::f(Integer)-argcount{1}at/etc/puppetlabs/code/environments/production/modules/test/manifests/init.pp:12:3onnodepuppet4.athome.privWarning:NotusingcacheonfailedcatalogError:Couldnotretrievecatalog;skippingrun{code}Inrubyfunction,itseemsthat:{code}Integer[0]=Integer[0,0]{code}Itisn'tabigproblembecausethereisaworkaroundwith:{code}Puppet::Functions.create_function(:'test::f')dodispatch:fdo#required_param'Integer[0]',:nrequired_param'Integer[0,default]',:nenddeff(n)trueendend{code}Howeveritseemstomethatthereisalittleinconsistency.Regards.
Add Comment
This message was sent by Atlassian
Jira (PUP-4854) PMT fails to install modules on Windows that have long paths
Title: Message Title Ethan Brown commented on PUP-4854 Re: PMT fails to install modules on Windows that have long paths Looks like we came to the same conclusion at the same time James Pogran. I just diagnosed the issue locally and indeed this is a max path issue. We can buy ourselves a little more headroom by selecting a better default temporary path on Windows (like %TEMP%), that isn't underneath the environments modules directory. PMT makes a problematic default selection on Windows at https://github.com/puppetlabs/puppet/blob/003d2b73b4730953092bb7e8b7bc723d2210c999/lib/puppet/module_tool/applications/unpacker.rb#L96 We should make sure that we're OK with any security implications of writing to a different temp directory. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1750) PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1750 PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker Change By: Russell Mull Fix Version/s: PDB3.0.x Fix Version/s: PDB3.0.1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4751) Optimize Secure safe_posix_fork
Title: Message Title Kylo Ginsberg commented on PUP-4751 Re: Optimize Secure safe_posix_fork Michael Smith ah, I only had part of the picture when I commented this morning that this should be in a Y release. I agree with fixing this in puppet 3.8.2, but holding off on the merge to stable until we release 4.2.1 (which should be real soon now), meaning this would hit the 4.x series in 4.2.2. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4775) org.jruby.exceptions.RaiseException: (SystemStackError) stack level too deep
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4775
org.jruby.exceptions.RaiseException: (SystemStackError) stack level too deep
Change By:
Henrik Lindberg
ReleaseNote Serialization of{{node}}objectscouldproducegiantserializationsthanwhenlaterloadedwouldcause'stackleveltoodeep'errors.Thiswascausedbylogicmissinginthenodeimplementationthatshouldhavepreventedserializationoftheentireruntimestateoftheenvironment.SummarySerialization /DeseerializationofPuppet::Nodeobjectsusingyamlcausestheentireenvironmentassociatedwiththenodetobeserializedinfull-thisiseverythingloadedandevaluatedintheenvironment,anditgoesverydeep.Asnotedincomments,itispossibletoworkaroundtheissueofhittingastackoverflowbyincreasingthestackandmakingmorememoryavailable.Therootcauseisthatobjects(suchasPuppet::Node)whichrequiresasymmetricserialization(itonlywantsaserializationoftheenvironment'sname,andlooksuptheenvironmentondeserialization)mustincludeamodule:{code:ruby}includePuppet::Util::PsychSupport{code}togettheexpectedbehaviorofusingto/fromdatahashmethods.ORIGINAL---AfterrunningforawhilePuppetagentrunsstarttofailduetoservererrors,theexceptionappearstoindicateanissuewithyamlencoding.Thiserrorwashappeningwith2.0.0andIhavealsotriedthelatestpackageavailableinthenightlyrepowhichisexhibitingthesamebehaviour.{noformat}2015-05-3115:50:41,651ERROR[p.p.ringutils]ExceptionwhilehandlingHTTPrequestorg.jruby.exceptions.RaiseException:(SystemStackError)stackleveltoodeep atorg.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)~[puppet-server-release.jar:na]repeatedpartomitted atRUBY.accept(/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:128)~[na:na] atRUBY.dump_ivars(/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:480)~[na:na] atorg.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)~[puppet-server-release.jar:na] atRUBY.dump_ivars(/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:478)~[na:na] atRUBY.visit_Object(/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:150)~[na:na] atRUBY.accept(/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:128)~[na:na] atRUBY.visit_Array(/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/META-INF/jruby.home/lib/ruby/shared/psych/visitors/yaml_tree.rb:344)~[na:na] atorg.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)~[puppet-server-release.jar:na]{noformat}
Jira (PUP-4787) Acceptance failing on check_woy_cache_works.rb on all platforms (master and stable)
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4787 Acceptance failing on check_woy_cache_works.rb on all platforms (master and stable) Change By: Eric Thompson Release Notes: NotNeeded Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4752) Uppercase letters in parameter variable names
Title: Message Title Eric Thompson commented on PUP-4752 Re: Uppercase letters in parameter variable names see my other comments for the validation. If this isn't clear, we can discuss another commenting format so the validation is more obvious/definitive... let me know if this is an issue, in general. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1756) PR (1533): (maint) Update acceptance tests to expect an AIO latest - ajroetker
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1756 PR (1533): (maint) Update acceptance tests to expect an AIO latest - ajroetker Change By: Russell Mull Story Points: 0 Fix Version/s: PDB3.0.1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-3328) tidy should follow symlinks
Title: Message Title Cosmin Lehene commented on PUP-3328 Re: tidy should follow symlinks Here's the PR with the current patch rebased to master: https://github.com/puppetlabs/puppet/pull/4084 Christopher Barbour this is worth discussing. I'm not sure that I'll get back to this very soon, though and that change would require resource changes, documentation, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1084) Store variables set at classification along with facts in PuppetDB
Title: Message Title Owen Rodabaugh commented on PDB-1084 Re: Store variables set at classification along with facts in PuppetDB This does make sense. NC variables are a sort of trusted data about a node and so being able to query them. As for laying down custom facts, we quite often see this happen at provisioning time because those facts are often used to drive classification post-provisioning. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1084) Store variables set at classification along with facts in PuppetDB
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-1084 Store variables set at classification along with facts in PuppetDB Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1756) PR (1533): (maint) Update acceptance tests to expect an AIO latest - ajroetker
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1756 PR (1533): (maint) Update acceptance tests to expect an AIO latest - ajroetker Change By: Russell Mull Sprint: PuppetDB2015-07-15 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1760) PR (1534): (RE-5033) Update Ezbake to new 0.3.14 - stahnma
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1760 PR (1534): (RE-5033) Update Ezbake to new 0.3.14 - stahnma Change By: Russell Mull Sprint: PuppetDB2015-07-15 Story Points: 8 Scope Change Reason: Allofourbuildsbroke Scope Change Category: Found Fix Version/s: PDB3.0.1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and
Jira (PUP-4777) Puppet gem dependencies are out of date
Title: Message Title Michael Smith updated an issue Puppet / PUP-4777 Puppet gem dependencies are out of date Change By: Michael Smith Release Notes Summary: ThePuppetgemrestricteditsHieradependencytoversionsbelow3.0.Puppet4.2.1updatesthedependencytouseHiera3. Release Notes: BugFix Original Estimate: 0minutes Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1763) PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1763 PR (1537): (maint) update preinst for redhat to check for 2.x if upgrading - wkalt Change By: Russell Mull Sprint: PuppetDB2015-07-15 Story Points: 1 Scope Change Reason: Testsbroke Scope Change Category: Found Fix Version/s: PDB3.0.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from
Jira (FACT-1119) Add Mac OS X facts test
Title: Message Title Michael Smith assigned an issue to William Hopper Facter / FACT-1119 Add Mac OS X facts test Change By: Michael Smith Assignee: WilliamHopper Sprint: Client2015-07-22 Scope Change Reason: Coversfunctionalitywewillreleasein3.0.2 Scope Change Category: Found Fix Version/s: FACT3.0.2 Release Notes: NotNeeded Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4819) Add service for obtaining class information per environment
Title: Message Title Henrik Lindberg commented on PUP-4819 Re: Add service for obtaining class information per environment Christopher PricePatrick Carlisle PR up - appreciate if you give it a glance over to see if it meets your expectations. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1119) Add Mac OS X facts test
Title: Message Title William Hopper assigned an issue to Unassigned Facter / FACT-1119 Add Mac OS X facts test Change By: William Hopper Assignee: WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1102) Prepare long form release notes and short form release story
Title: Message Title Garrett Guillotte assigned an issue to Nicholas Fagerlund Submitted PR 523, not for merge until 3.0.2's release. Facter / FACT-1102 Prepare long form release notes and short form release story Change By: Garrett Guillotte Assignee: NicholasFagerlund Fix Version/s: FACT3.0.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1772) Tag the release and create packages
Title: Message Title Matthaus Owens commented on PDB-1772 Re: Tag the release and create packages Tagged https://github.com/puppetlabs/puppetdb/commit/9ff30bea68addc0fc71fcc65159b2d92e12be67d as 3.0.1 and kicked the jenkins job to get packages built. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1102) Prepare long form release notes and short form release story
Title: Message Title Garrett Guillotte updated an issue Facter / FACT-1102 Prepare long form release notes and short form release story Change By: Garrett Guillotte Comment: SubmittedPR523,notformergeuntil3.0.2'srelease. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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.
