Jira (PUP-1496) static compiler doesn't work when a file resource has more than one source URL
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1496
static compiler doesn't work when a file resource has more than one source URL
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
23/Jan/14 12:41 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
The static compiler ignores - and, so, uses non-static sourcing for - file resources with more than one source:
file { /tmp/example.txt: source = [puppet:///foo, puppet:///bar] }
It isn't clear to me what the most correct behaviour is:
Should we replace all those URL references with content references? Works fine for both `sourceselect = all` and `sourceselect = first`, but may result in putting more data in the bucket than is required. Also, makes it more likely that a future change that did more to sync bucket content to agents might reveal more than should be shown to the machine. (eg: if we treat everything we make static as target node can access this we reveal both foo and bar, even if only foo should be available.)
Should we try and emulate the file type behaviour? That works, I guess, but it leads to the odd situation where the static compiler and the file type have to agree on their behaviour - otherwise we end of diverging between the two. Which isn't awesome. It does mean that we do a static, compilation time evaluation of the decision point in the resource, though, which seems like a win.
Do we try and defer this until we only have the static compiler (or do it preemptively), and allow types to add behaviour that supports this? (eg: the file type has the can make myself static
Jira (PUP-1496) static compiler doesn't work when a file resource has more than one source URL
Title: Message Title
Aurlien Degrmont commented on an issue
Re: static compiler doesn't work when a file resource has more than one source URL
According to Redmine ticket, code duplication is not nice, but instead of saying this should be fixed the right way, and having no fix for more than 1 year, it is possible to consider to just fix this, in one patch, and take the time needed to reorganize code in another patch?
Add Comment
Puppet / PUP-1496
static compiler doesn't work when a file resource has more than one source URL
The static compiler ignores - and, so, uses non-static sourcing for - file resources with more than one source: file { /tmp/example.txt: source = [puppet:///foo, puppet:///bar] } It isn't clear to me what the most correct behaviour is: Should we replace *all* those URL references with content references? Works fine for both `sourcesel...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-1497) Missing version number in Windows packages displayname prevents update
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-1497 Missing version number in Windows packages displayname prevents update Issue Type: Improvement Assignee: Eric Sorenson Created: 23/Jan/14 1:44 AM Environment: Windows Priority: Normal Reporter: Dirk Heinrichs Wanted to update the Puppet agent on Windows via Puppet. Unfortunately, the displayname, which is what the package resource looks after, of the Puppet package for Windows is just Puppet. So no matter what version I want to update to, package resource is always satisfied if ANY version of puppet is already installed. Pupping the version number into the displayname field, like many other packages do as well, would solve that problem. Add Comment
Jira (PUP-1497) Missing version number in Windows packages displayname prevents update
Title: Message Title Dirk Heinrichs updated an issue Puppet / PUP-1497 Missing version number in Windows packages displayname prevents update Change By: Dirk Heinrichs WantedtoupdatethePuppetagentonWindowsviaPuppet.Unfortunately,thedisplayname,whichiswhatthepackageresourcelooksafter,ofthePuppetpackageforWindowsisjustPuppet.SonomatterwhatversionIwanttoupdateto, the packageresourceisalwayssatisfiedifANYversionofpuppetisalreadyinstalled. Pupping Putting theversionnumberintothedisplaynamefield,likemanyotherpackagesdoaswell,wouldsolvethatproblem. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1495) Puppet on Debian systems failing to apply file changes
Title: Message Title
Anthony Somerset updated an issue
Puppet / PUP-1495
Puppet on Debian systems failing to apply file changes
Change By:
Anthony Somerset
i'mnotexactlysurewhichversionthisstartedinbutitwasafter3.3.xandstillexistsin3.4.2wheneverafilechangeisdetectedthepuppetrunitwillshowthediffbutbeunabletoapplyit.itseemstotimeout.withoutdebug/verbosethiserrordropsintotheterminalwindow:err:/Stage[main]/Ssh/File[/etc/ssh/sshd_config]:Couldnotevaluate:Puppet::Util::Logrequiresamessagehoweverifirundebugandverboseflagsiget: rror Error :Couldnotbackup/etc/ssh/sshd_config:Timeout::ErrorError:Couldnotbackup/etc/ssh/sshd_config:Timeout::ErrorError:/Stage[main]/Ssh/File[/etc/ssh/sshd_config]/content:changefrom{md5}8caefdd9e251b7cc1baa37874149a870to{md5}2ee23a0ec404874c9e8e8462194fbf29failed:Couldnotbackup/etc/ssh/sshd_config:Timeout::Errorinotethatpluginsynccontinuestowork,creatingnewfilespullingfrompuppet(eithertemplateorstraightfile)butanyfilechangeorfiledeletefailsifidisablepassengerandloadthepuppetmasterdirectly,theneverythingworkscorrectlyifidisablefilebackupsthenitworksfinealsosothetimeoutoccursonthefilebackup
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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/groups/opt_out.
Jira (MCO-167) Mcollective forks to much processes
Title: Message Title Simon Hoenscheid created an issue MCollective / MCO-167 Mcollective forks to much processes Issue Type: Bug Assignee: R.I.Pienaar Created: 23/Jan/14 2:12 AM Priority: Major Reporter: Simon Hoenscheid We run Ubuntu 12.04 LTS on our Servers and use mcollective from the puppetlabs repo. On some hosts we see mcollective running willd, forking instances: 32286 ? Sl 171:30 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32290 ? Sl 172:01 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32296 ? Sl 172:34 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32300 ? Sl 173:38 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32305 ? Sl 177:17 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32310 ? Sl 173:49 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32315 ? Sl 178:44 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32319 ? Sl 180:29 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32323 ? Sl 164:54 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32338 ? Sl 165:24 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32343 ? Sl 179:37 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 30114 ? S 0:00 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 30118 ? S 0:00 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 30122 ? S 0:00 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 30127 ? S 0:00 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid
Jira (MCO-167) Mcollective forks to much processes
Title: Message Title
Simon Hoenscheid updated an issue
MCollective / MCO-167
Mcollective forks to much processes
Change By:
Simon Hoenscheid
WerunUbuntu12.04LTSonourServersandusemcollectivefromthepuppetlabsrepo.Onsomehostsweseemcollectiverunningwilld,forkinginstances:32286?Sl171:30ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32290?Sl172:01ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32296?Sl172:34ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32300?Sl173:38ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32305?Sl177:17ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32310?Sl173:49ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32315?Sl178:44ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32319?Sl180:29ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32323?Sl164:54ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32338?Sl165:24ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg32343?Sl179:37ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30114?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30118?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30122?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30127?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30132?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30137?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30142?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30146?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30151?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30156?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg30164?S0:00ruby/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfgItmakesnodifferenceifwedaemonizemcollectiveornot(whatisofficiallyrecommendetforubuntu?)thereisansimilarerrorknownfortheubuntupackage:https://bugs.launchpad.net/ubuntu/+source/mcollective/+bug/918348andthereisafiX:{code}startonrunlevel[2345]stoponrunlevel[!2345] * expectdaemon * exportRUBYLIB=/usr/local/lib/site_ruby/1.8:$RUBYLIBenvRUBYLIB=/usr/local/lib/site_ruby/1.8:$RUBYLIBexec/usr/sbin/mcollectived--pid=/var/run/mcollectived.pid--config=/etc/mcollective/server.cfg{code} the * expectdaemon*isthefix* BUT*TheubuntuPackageusesupstart,theonefrompuppetlabsanormalinitscript.Idontknowwhattodoandhowtofixit.itisveryurgentforus.
Jira (PDB-346) SSL bug, fqdn/certname problem: javax.net.ssl.SSLHandshakeException: null cert chain
Title: Message Title redmine.exporter created an issue PuppetDB / PDB-346 SSL bug, fqdn/certname problem: javax.net.ssl.SSLHandshakeException: null cert chain Issue Type: Bug Assignee: Unassigned Created: 23/Jan/14 2:19 AM Labels: redmine Priority: Normal Reporter: redmine.exporter This bug report is a result of communicating with Ken via the mailing list: https://groups.google.com/d/topic/puppet-users/877mzTGZl1A/discussion. Find complete output including puppet.conf here: http://pastebin.com/raw.php?i=TDejFAvp. Whenever `puppet agent -t` was ran, the following error would be returned: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for gaia.local to PuppetDB at puppetdb.local:8081: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Which only really means the SSL connection was cut-off early ... looking in puppetdb.log we saw the error: WARN [qtp788652058-42] [io.nio] javax.net.ssl.SSLHandshakeException: null cert chain The problem was the following: For everything puppet, I use puppet.local as the fqdn for the puppet master.
Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title
Bruce Bushby commented on an issue
Re: Yum provider purge target runs irrespective of package installation status
This is affecting all of our machines: [root@-linux opt]# [root@-linux opt]# rpm -qa | grep puppet puppet-3.3.2-1.el6.noarch [root@-linux opt]#
The package does not exist, but we still the the syslog message due to the ensure = purged;
class sudo::install { if ( $operatingsystem in [ 'redhat', 'RedHat' ]) { package { sudo: ensure = latest; -sudoers: ensure = purged; }
} }
The syslof message: Jan 23 03:42:28 -linux puppet-agent[17413]: (/Stage[main]/Sudo::Install/Package[-sudoers]/ensure) created Jan 23 03:42:31 -linux puppet-agent[17413]: Finished catalog run in 5.10 seconds Jan 23 04:42:29 -linux puppet-agent[18542]: (/Stage[main]/Sudo::Install/Package[-sudoers]/ensure) created Jan 23 04:42:32 -linux puppet-agent[18542]: Finished catalog run in 5.62 seconds Jan 23 05:42:30 -linux puppet-agent[19258]: (/Stage[main]/Sudo::Install/Package[-sudoers]/ensure) created Jan 23 05:42:33 -linux puppet-agent[19258]: Finished catalog run in 7.09 seconds Jan 23 06:42:29 -linux puppet-agent[20361]: (/Stage[main]/Sudo::Install/Package[-sudoers]/ensure) created Jan 23 06:42:31 -linux puppet-agent[20361]: Finished catalog run in 5.48 seconds
Add Comment
Puppet / PUP-1295
Yum provider purge target runs irrespective of package installation status
It seems the yum provider will try to purge an absent package: pre [root@test ~]# cat test.pp package { logwatch: ensure = purged; } [root@test ~]# /bin/rpm -q logwatch --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' package logwatch is not installed [root@test ~]# puppet -d -v test.pp debug: P...
Jira (PUP-620) Pull Request (2012): added install_options to gem provider. now you can do... install_options...
Title: Message Title gepetto-bot commented on an issue Re: Pull Request (2012): added install_options to gem provider. now you can do... install_options... xavicarrillo commented: +1 Add Comment Puppet / PUP-620 Pull Request (2012): added install_options to gem provider. now you can do... install_options... h2. added install_options to gem provider. now you can do... install_options... * Author: Mike mike.mogha...@gmail.com * Company: * Github ID: [mmoghadas|https://github.com/mmoghadas] * [Pull Request 2012 Discussion|https://github.com/puppetlabs/puppet/pull/2012] * [Pull Request 2012 File Diff|https://github.com/puppetlabs/puppet/pull/2012/files... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-345) PR (812): Fixes an issue when using spyscope as a lein user profile - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (812): Fixes an issue when using spyscope as a lein user profile - senior kbarber commented: @senior is this safe to push to 1.5.x instead? Add Comment PuppetDB / PDB-345 PR (812): Fixes an issue when using spyscope as a lein user profile - senior h2. Fixes an issue when using spyscope as a lein user profile * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 812 Discussion|https://github.com/puppetlabs/puppetdb/pull/812] * [Pull Request 812 File Diff|https://github.com/puppetlabs/puppetdb/pull/812/files] h2. Pull Request ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-346) SSL bug, fqdn/certname problem: javax.net.ssl.SSLHandshakeException: null cert chain
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-346 SSL bug, fqdn/certname problem: javax.net.ssl.SSLHandshakeException: null cert chain Change By: Kenneth Barber Affects Version/s: 1.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-344) Latests docs point to unreleased version
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-344 Latests docs point to unreleased version Change By: Kenneth Barber Affects Version/s: 1.6.0-rc3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-341) Select-resources subquery strange behavior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-341 Select-resources subquery strange behavior Change By: Kenneth Barber Affects Version/s: 1.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-341) Select-resources for file and line on facts are unsupported
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-341 Select-resources for file and line on facts are unsupported Change By: Kenneth Barber Summary: Select-resources subquerystrangebehavior forfileandlineonfactsareunsupported Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-341) Select-resources for file and line on facts end-point are unsupported
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-341 Select-resources for file and line on facts end-point are unsupported Change By: Kenneth Barber Summary: Select-resourcesforfileandlineonfacts end-point areunsupported Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-345) PR (812): Fixes an issue when using spyscope as a lein user profile - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-345 PR (812): Fixes an issue when using spyscope as a lein user profile - senior Change By: Kenneth Barber Sprint: 20140122to20140129 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-345) PR (812): Fixes an issue when using spyscope as a lein user profile - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-345 PR (812): Fixes an issue when using spyscope as a lein user profile - senior Change By: Kenneth Barber Story Points: 1 Affects Version/s: 1.5.0 Fix Version/s: 1.5.X Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-345) PR (812): Fixes an issue when using spyscope as a lein user profile - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (812): Fixes an issue when using spyscope as a lein user profile - senior Pull request Fixes an issue when using spyscope as a lein user profile has been closed. Add Comment PuppetDB / PDB-345 PR (812): Fixes an issue when using spyscope as a lein user profile - senior h2. Fixes an issue when using spyscope as a lein user profile * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 812 Discussion|https://github.com/puppetlabs/puppetdb/pull/812] * [Pull Request 812 File Diff|https://github.com/puppetlabs/puppetdb/pull/812/files] h2. Pull Request ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-345) PR (812): Fixes an issue when using spyscope as a lein user profile - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (812): Fixes an issue when using spyscope as a lein user profile - senior kbarber commented: Merged manually into 1.5.x here: https://github.com/puppetlabs/puppetdb/commit/680415f7deb50021e2afd5812cdb04aa9bed221c Add Comment PuppetDB / PDB-345 PR (812): Fixes an issue when using spyscope as a lein user profile - senior h2. Fixes an issue when using spyscope as a lein user profile * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 812 Discussion|https://github.com/puppetlabs/puppetdb/pull/812] * [Pull Request 812 File Diff|https://github.com/puppetlabs/puppetdb/pull/812/files] h2. Pull Request ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-1336) FWIW, puppetmaster doesn't notice changes to /etc/puppet/hiera.yaml
Title: Message Title Tristan Helmich commented on an issue Re: FWIW, puppetmaster doesn't notice changes to /etc/puppet/hiera.yaml Charlie Sharpsteen Should this migrated ticket be assigned to you? 6 Months ago during the Triage-a-thon I was told to assign it to you. Add Comment Puppet / PUP-1336 FWIW, puppetmaster doesn't notice changes to /etc/puppet/hiera.yaml pre If you change the :hierarchy: in /etc/puppet/hiera.yaml to add or remove a file foo (eg: foo.yaml) puppetmaster and it's clients won't notice this until you restart it. Ideally it would notice this with a mechanism such as inotify or similar. This can be an issue if you've added a classname::param: value entry in a new file, and you now expect t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1498) scheduled_task won't update command
Title: Message Title c lang created an issue Puppet / PUP-1498 scheduled_task won't update command Issue Type: Bug Affects Versions: 2.7.23 Assignee: Eric Sorenson Created: 23/Jan/14 7:24 AM Priority: Normal Reporter: c lang if you update a scheduled_task's command, Puppet does not make the change in the task scheduler. Other changes, e.g. the trigger, appear to work, but not the command. I've had to work around by deleting the old task and creating a new one with a different name. Add Comment This message was sent
Jira (PUP-1462) PR (2268): Ccin2p3 yumrepo repo gpgcheck - riton
Title: Message Title gepetto-bot commented on an issue Re: PR (2268): Ccin2p3 yumrepo repo gpgcheck - riton riton commented: Ok, it's done, you can merge this from 45993329252e4f89d3bcbb347712e3cdc4b27ac8. Is this ok for you ? Add Comment Puppet / PUP-1462 PR (2268): Ccin2p3 yumrepo repo gpgcheck - riton h2. Ccin2p3 yumrepo repo gpgcheck * Author: Remi Ferrand * Company: IN2P3 Computing Centre * Github ID: [riton|https://github.com/riton] * [Pull Request 2268 Discussion|https://github.com/puppetlabs/puppet/pull/2268] * [Pull Request 2268 File Diff|https://github.com/puppetlabs/puppet/pull/2268/files] h2. Pull Request Description Add suppor... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber
Title: Message Title John Duarte updated an issue PuppetDB / PDB-312 PR (802): Convert unit testing to use dynamic postgres instance - kbarber Change By: John Duarte Labels: github qa-reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (MCO-168) release MCollective 2.4.0
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-168 release MCollective 2.4.0 Change By: Pieter Loubser Fix Version/s: 2.4.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (MCO-168) release MCollective 2.4.0
Title: Message Title Pieter Loubser commented on an issue Re: release MCollective 2.4.0 https://github.com/puppetlabs/marionette-collective/pull/155 Add Comment MCollective / MCO-168 release MCollective 2.4.0 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (MCO-168) release MCollective 2.4.0
Title: Message Title Pieter Loubser created an issue MCollective / MCO-168 release MCollective 2.4.0 Issue Type: Task Assignee: Pieter Loubser Created: 23/Jan/14 8:14 AM Due Date: 23/Jan/14 Priority: Normal Reporter: Pieter Loubser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (MCO-168) release MCollective 2.4.0
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-168 release MCollective 2.4.0 Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-735) Status unchanged when Could not apply complete catalog
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-735 Status unchanged when Could not apply complete catalog Change By: Michelle Johansen Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-283) Improve agent error reporting
Title: Message Title Michelle Johansen commented on an issue Re: Improve agent error reporting Aaron Armstrong and Kenn Hussey We are taking this off the Platform team's list for now as Reporting and PuppetDB requests from PE are still in flux. If and when this work is needed, hopefully this work can be planned into the PE team workload with support from the PuppetDB and Platform team. Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PDB-347) Support CRL checking
Title: Message Title Erik Daln created an issue PuppetDB / PDB-347 Support CRL checking Issue Type: New Feature Assignee: Unassigned Created: 23/Jan/14 8:24 AM Priority: Normal Reporter: Erik Daln As PuppetDB handles the checking of client SSL certificates it should also be able to verify them against a CRL. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are
Jira (PUP-283) Improve agent error reporting
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-283 Improve agent error reporting Change By: Michelle Johansen Fix Version/s: 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1499) Puppet open source Windows packages should include mcollective
Title: Message Title c lang created an issue Puppet / PUP-1499 Puppet open source Windows packages should include mcollective Issue Type: Improvement Assignee: Eric Sorenson Created: 23/Jan/14 8:30 AM Priority: Normal Reporter: c lang I have a large client that's 50/50 Windows/Linux that's desperately trying to embrace Puppet, but Puppet on Windows always appears to be the proverbial red-headed stepchild. Puppet kick is both deprecated and not supported on Windows, and the recommended solution is to use mcollective. Unfortunately, mcollective is not part of the open source MSI, and attempting to make that work, even with third party MSIs, is a great deal of labor - especially if you want the mcollective puppet agent to work. Can you please consider providing open source MSIs that install Puppet and Mcollective that will allow a simple installation of a functional Mcollective Puppet plugin? This seems like an opportunity to both distinguish Puppet from its competition and improve the adoption of mcollective. Add Comment
Jira (PUP-916) Document report format changes for improved agent reporting
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-916 Document report format changes for improved agent reporting Change By: Michelle Johansen Fix Version/s: 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (MCO-167) Mcollective forks to much processes
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-167 Mcollective forks to much processes Change By: Pieter Loubser Assignee: R.I.Pienaar RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (MCO-167) Mcollective forks to much processes
Title: Message Title Richard Clamp commented on an issue Re: Mcollective forks to much processes Well the init script/upstart management and server.cfg must be in agreement as to what mcollectived should do (to daemonize or not) when it is started, so either modify the upstart script as you note to say expect daemon or update your server.cfg to say daemonize = 0 . Add Comment MCollective / MCO-167 Mcollective forks to much processes We run Ubuntu 12.04 LTS on our Servers and use mcollective from the puppetlabs repo. On some hosts we see mcollective running willd, forking instances: 32286 ? Sl 171:30 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg 32290 ? Sl 172:01 ruby /usr/sbin/mcollectived --pid=/var/run/mcol... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1164) Order matters with tagged function
Title: Message Title
Carlos Sanchez updated an issue
Puppet / PUP-1164
Order matters with tagged function
Change By:
Carlos Sanchez
Itshouldbenotedinthedocumentationofthelimitswhenusingthe'tagged'functionorderingofclassesvia'include'matters.Iethiscode.code: pre {code} classa{notify{classa:}iftagged(b){notify{foundclassb:}}}classb{notify{classb:}}classtest{notify{classtest:}includeaincludeb} /pre {code} testoutput: pre {code} [root@bast~]#puppet-eincludetesttest.pp--verbose--logdest=console--debugdebug:importing'/home/larry/test.pp'info:Autoloadedmoduletestdebug:Creatingdefaultschedulesdebug://test/a/Notify[classa]:Changingmessagedebug://test/a/Notify[classa]:1change(s)notice:classanotice://test/a/Notify[classa]/message:defined'message'as'classa'debug://test/Notify[classtest]:Changingmessagedebug://test/Notify[classtest]:1change(s)notice:classtestnotice://test/Notify[classtest]/message:defined'message'as'classtest'debug://test/b/Notify[classb]:Changingmessagedebug://test/b/Notify[classb]:1change(s)notice:classbnotice://test/b/Notify[classb]/message:defined'message'as'classb'debug:Finishingtransaction70131190151540with3changes /pre {code} willonlyoutputfoundclassbwhentheorderofincludesisreversed.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-41) Puppet returns different result non-existent services on EL and Debian
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-41 Puppet returns different result non-existent services on EL and Debian Change By: Michelle Johansen Fix Version/s: 3.5.0 Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-41) Puppet returns different result non-existent services on EL and Debian
Title: Message Title
Michelle Johansen commented on an issue
Re: Puppet returns different result non-existent services on EL and Debian
Kenn Hussey and Aaron Armstrong We would also like to see if this work can be picked up by the PE team as it is specific to PE 3 functionality
Add Comment
Puppet / PUP-41
Puppet returns different result non-existent services on EL and Debian
EL and Debian have different results for service resources that don't exist. On EL, `puppet resource service abcdefg` will return service { 'abcdefg': ensure = 'stopped', enable = 'false', } On Debian, this will return Error: Could not run: Could not find init script for 'abcdefg' While what is returned by puppet on EL is te...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PDB-348) v3 URL metrics return v2 information
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-348 v3 URL metrics return v2 information Issue Type: Bug Affects Versions: 1.5.X, 1.6.x Assignee: Unassigned Created: 23/Jan/14 9:12 AM Priority: Normal Reporter: Ryan Senior The below code is executed for v2 and v3 metrics on the commands URL Unable to find source-code formatter for language: clojure. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml (.startsWith name com.puppetlabs.puppetdb.http.server:type=commands) (s/replace name #type=commands type=/v2/commands) So a user would look for metrics at /v3/metrics/mbeans and it would return v2 metrics instead. The above is true for metrics, commands, facts and resources Add
Jira (HI-140) Smoke test packages
Title: Message Title Henrik Lindberg commented on an issue Re: Smoke test packages Ubuntu 13.10 passed. Add Comment Hiera / HI-140 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. * Centos 5/6 * Debian Squeeze/Wheezy * Ubuntu Lucid/Precise * Gem * dmg Check that * hiera is available. * man hiera (except for gems) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-348) v3 URL metrics return v2 information
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-348 v3 URL metrics return v2 information Change By: Kenneth Barber Affects Version/s: 1.5.X Affects Version/s: 1.6.x Affects Version/s: 1.5.0 Affects Version/s: 1.6.0-rc3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-844) Create basic acl type
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-844 Create basic acl type Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1411) Windows agents experience intermittent SSL_connect failures in acceptance testing
Title: Message Title
Joshua Cooper commented on an issue
Re: Windows agents experience intermittent SSL_connect failures in acceptance testing
SSL_connect failure on 2008r2 https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-stable-vcloud-and-github/149/label=acc-coord,platform=win2008-all/
Add Comment
Puppet / PUP-1411
Windows agents experience intermittent SSL_connect failures in acceptance testing
Breaking this out as a separate ticket related to QA-768. During Windows acceptance testing on master, certificate requests non-deterministically fail due with SSL_connect failures: {code} #RuntimeError: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'oqr39kv18vwtk49' exited with 1 running: ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (HI-140) Smoke test packages
Title: Message Title Henrik Lindberg commented on an issue Re: Smoke test packages dmg PASSED Add Comment Hiera / HI-140 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. * Centos 5/6 * Debian Squeeze/Wheezy * Ubuntu Lucid/Precise * Gem * dmg Check that * hiera is available. * man hiera (except for gems) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (HI-140) Smoke test packages
Title: Message Title Henrik Lindberg commented on an issue Re: Smoke test packages gem install PASSED Add Comment Hiera / HI-140 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. * Centos 5/6 * Debian Squeeze/Wheezy * Ubuntu Lucid/Precise * Gem * dmg Check that * hiera is available. * man hiera (except for gems) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (HI-140) Smoke test packages
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Hiera / HI-140 Smoke test packages Change By: Henrik Lindberg Assignee: AndrewParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (HI-151) hiera_array() fails when used in class parameters
Title: Message Title
Marc Villacorta created an issue
Hiera / HI-151
hiera_array() fails when used in class parameters
Issue Type:
Bug
Affects Versions:
1.3.0
Assignee:
Eric Sorenson
Created:
23/Jan/14 9:48 AM
Environment:
bash-4.1# puppet --version
3.4.2
bash-4.1# hiera --version
1.3.0
Priority:
Normal
Reporter:
Marc Villacorta
Given this hiera config:
bash-4.1# cat /etc/puppet/hiera.yaml
---
:backends:
- yaml
:hierarchy:
- one
- two
:yaml:
:datadir: '/etc/puppet/hieradata'
:merge_behavior: deeper
...
and this values:
bash-4.1# cat /etc/puppet/hieradata/{one,two}.yaml
---
foo::message:
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title gepetto-bot commented on an issue Re: PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar hlindberg commented: I am sorry - I was under the impression we ended up with more backwards incompatibility than what you mention (the exceptional floats). Will review again. Could you trigger a rerun of Travis? Something made it fail (seems like an infrastructure failure). (Now looking how I can trigger that for you...) Add Comment Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar h2. fix is_numeric/is_integer when checking non-string parameters * Author: Simon Effenberg * Company: * Github ID: [Savar|https://github.com/Savar] * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213] * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop
Jira (PDB-349) duplicate key value violates unique constraint constraint_resource_events_unique
Title: Message Title Erik Daln updated an issue PuppetDB / PDB-349 duplicate key value violates unique constraint constraint_resource_events_unique Change By: Erik Daln Attachment: 2014-01-23T17.09.52.055Z-4a2cd8374d440b8ecfeb1d1de13e4de15a575b1c Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-349) duplicate key value violates unique constraint constraint_resource_events_unique
Title: Message Title Erik Daln created an issue PuppetDB / PDB-349 duplicate key value violates unique constraint constraint_resource_events_unique Issue Type: Bug Assignee: Unassigned Attachments: 2014-01-23T17.09.52.055Z-4a2cd8374d440b8ecfeb1d1de13e4de15a575b1c Created: 23/Jan/14 10:04 AM Priority: Normal Reporter: Erik Daln After upgrading to puppetdb terminus 1.6.0-rc1 I started getting this error. It didn't occur when using 1.6.0-rc1 on the server but 1.5 terminus. Add Comment This message was sent by
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-759) Remove ca_days from --genconfig output
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-759 Remove ca_days from --genconfig output Change By: Michelle Johansen Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1484) msgpack serialization of TagSet broken
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1484 msgpack serialization of TagSet broken Change By: Adrien Thebo Sprint: Week2014-1-22to2014-1-29 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1484) msgpack serialization of TagSet broken
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-1484 msgpack serialization of TagSet broken Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-759) Remove ca_days from --genconfig output
Title: Message Title Michelle Johansen commented on an issue Re: Remove ca_days from --genconfig output Kylo Ginsberg Is this status true? And if so, let's pull it into the sprint. If not, can we get the status updated please. Add Comment Puppet / PUP-759 Remove ca_days from --genconfig output puppet master --gencofig gives me (for ca_ttl): # The default TTL for new certificates. If this setting is set, ca_days is ignored. # This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y). # The default value is '5y'. ca_ttl = 15768 Since ca_days is no longer a setting,... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-894) Too easy to hit CRL not yet valid for host (and not very informative)
Title: Message Title Michelle Johansen commented on an issue Re: Too easy to hit CRL not yet valid for host (and not very informative) Kylo Ginsberg Is this a requirement for 3.5.0? Add Comment Puppet / PUP-894 Too easy to hit CRL not yet valid for host (and not very informative) Currently we set the CRL time range to start at 1 second in the past: https://github.com/puppetlabs/puppet/blob/a8311df5438601a3394d38e37f671626969d50db/lib/puppet/ssl/certificate_revocation_list.rb#L85 However, this creates a window where an agent with a small amount of clock skew can hit the `CRL not yet valid for host` message. This affects bo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1484) msgpack serialization of TagSet broken
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1484 msgpack serialization of TagSet broken Change By: Adrien Thebo Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1038) puppet fails if template contains invalid utf-8
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1038 puppet fails if template contains invalid utf-8 Change By: Michelle Johansen Assignee: MarkJeromin CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1039) Use in expressions when realizing virtual resources
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1039 Use in expressions when realizing virtual resources Change By: Michelle Johansen Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1039) Use in expressions when realizing virtual resources
Title: Message Title
Michelle Johansen commented on an issue
Re: Use in expressions when realizing virtual resources
Henrik Lindberg Is this still a valid request?
Add Comment
Puppet / PUP-1039
Use in expressions when realizing virtual resources
It would be nice if you could use the in _expression_ when realizing resources. Currently the following fails: {code} @group{ 'foo': ... } @group{ 'bar': ... } $grouplist=[ 'foo', 'bar' ] Group | title in $grouplist | {code} However using realise it works: {code} @group{ 'foo': ... } @group{ 'bar': ... } $grouplist=[ 'foo', 'bar' ] real...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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/groups/opt_out.
Jira (PUP-1038) puppet fails if template contains invalid utf-8
Title: Message Title Michelle Johansen commented on an issue Re: puppet fails if template contains invalid utf-8 Charlie Sharpsteen Can you provide some info here please? Add Comment Puppet / PUP-1038 puppet fails if template contains invalid utf-8 If you attempt to use a file resource with a 'content' parameter pointing at a template, and the template contains binary content, you may get an error like this: Error: Failed to apply catalog: Parameter content failed: Munging failed for value ... invalid byte sequence in UTF-8 I've reproduced the failure in 2.7.16 and 3.x, though the err... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1039) Use in expressions when realizing virtual resources
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1039 Use in expressions when realizing virtual resources Change By: Michelle Johansen Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1042) Puppet apply runmode should write classes.txt file
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1042 Puppet apply runmode should write classes.txt file Change By: Michelle Johansen Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1484) msgpack serialization of TagSet broken
Title: Message Title Adrien Thebo commented on an issue Re: msgpack serialization of TagSet broken PR/2279 closed and https://github.com/puppetlabs/puppet/pull/2287 reopened that targets stable. Since it doesn't look like we're going be doing 3.4.3 I'm going to rebase the PR on top of master and merge it in. Add Comment Puppet / PUP-1484 msgpack serialization of TagSet broken This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1042) Puppet apply runmode should write classes.txt file
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1042 Puppet apply runmode should write classes.txt file Change By: Michelle Johansen Sprint: Week2014-1-22to2014-1-29 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-894) Too easy to hit CRL not yet valid for host (and not very informative)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-894 Too easy to hit CRL not yet valid for host (and not very informative) Change By: Kylo Ginsberg Fix Version/s: 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-894) Too easy to hit CRL not yet valid for host (and not very informative)
Title: Message Title Kylo Ginsberg commented on an issue Re: Too easy to hit CRL not yet valid for host (and not very informative) No. This is merely a nice-to-have. I'll remove the Fix Version field and let it drop into the backlog. Add Comment Puppet / PUP-894 Too easy to hit CRL not yet valid for host (and not very informative) Currently we set the CRL time range to start at 1 second in the past: https://github.com/puppetlabs/puppet/blob/a8311df5438601a3394d38e37f671626969d50db/lib/puppet/ssl/certificate_revocation_list.rb#L85 However, this creates a window where an agent with a small amount of clock skew can hit the `CRL not yet valid for host` message. This affects bo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-759) Remove ca_days from --genconfig output
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-759 Remove ca_days from --genconfig output Change By: Kylo Ginsberg Sprint: Week2014-1-22to2014-1-29 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-350) PR (113): Enable fast finish in Travis - ghoneycutt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-350 PR (113): Enable fast finish in Travis - ghoneycutt Issue Type: Task Assignee: Unassigned Created: 23/Jan/14 11:21 AM Labels: github module Priority: Normal Reporter: gepetto-bot Enable fast finish in Travis Author: Garrett Honeycutt git...@garretthoneycutt.com Company: Github ID: ghoneycutt Pull Request 113 Discussion Pull Request 113 File Diff Pull Request Description http://blog.travis-ci.com/2013-11-27-fast-finishing-builds/ (webhooks-id: f0ec7823e740c25fe68a08af253d9dd2)
Jira (PUP-759) Remove ca_days from --genconfig output
Title: Message Title Kylo Ginsberg commented on an issue Re: Remove ca_days from --genconfig output Status is correct. I added it to the current sprint, since it was merged 12 days ago. Not really sure if it's made it through CI or not (though it's trivial), so I haven't bumped the status to FR yet. Add Comment Puppet / PUP-759 Remove ca_days from --genconfig output puppet master --gencofig gives me (for ca_ttl): # The default TTL for new certificates. If this setting is set, ca_days is ignored. # This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y). # The default value is '5y'. ca_ttl = 15768 Since ca_days is no longer a setting,... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (HI-131) Hiera 1.3.1 Release - January 23st, 2014
Title: Message Title Melissa Stone updated an issue Hiera / HI-131 Hiera 1.3.1 Release - January 23st, 2014 Change By: Melissa Stone Summary: Hiera1.3.1Release-January 21st 23st ,2014 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-350) PR (113): Enable fast finish in Travis - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (113): Enable fast finish in Travis - ghoneycutt Pull request Enable fast finish in Travis has been closed. Add Comment PuppetDB / PDB-350 PR (113): Enable fast finish in Travis - ghoneycutt h2. Enable fast finish in Travis * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 113 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/113] * [Pull Request 113 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/113/files] h2. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (FACT-244) PR (614): (RE-814) Add initial support for building in a RHEL 7 mock - mckern
Title: Message Title gepetto-bot created an issue Facter / FACT-244 PR (614): (RE-814) Add initial support for building in a RHEL 7 mock - mckern Issue Type: Task Assignee: Adrien Thebo Components: Community Created: 23/Jan/14 11:53 AM Labels: github Priority: Normal Reporter: gepetto-bot (RE-814) Add initial support for building in a RHEL 7 mock Author: Ryan McKern r...@orangefort.com Company: Puppet Labs Github ID: mckern Pull Request 614 Discussion Pull Request 614 File Diff Pull Request Description As per
Jira (PUP-1500) PR (216): Enable fast finish in Travis - ghoneycutt
Title: Message Title gepetto-bot created an issue Puppet / PUP-1500 PR (216): Enable fast finish in Travis - ghoneycutt Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 23/Jan/14 11:53 AM Labels: github Priority: Normal Reporter: gepetto-bot Enable fast finish in Travis Author: Garrett Honeycutt git...@garretthoneycutt.com Company: Github ID: ghoneycutt Pull Request 216 Discussion Pull Request 216 File Diff Pull Request Description http://blog.travis-ci.com/2013-11-27-fast-finishing-builds/
Jira (PDB-350) PR (113): Enable fast finish in Travis - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (113): Enable fast finish in Travis - ghoneycutt Pull request Enable fast finish in Travis has been closed. Add Comment PuppetDB / PDB-350 PR (113): Enable fast finish in Travis - ghoneycutt h2. Enable fast finish in Travis * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 113 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/113] * [Pull Request 113 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/113/files] h2. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-350) PR (113): Enable fast finish in Travis - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (113): Enable fast finish in Travis - ghoneycutt Pull request Enable fast finish in Travis has been closed. Add Comment PuppetDB / PDB-350 PR (113): Enable fast finish in Travis - ghoneycutt h2. Enable fast finish in Travis * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 113 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/113] * [Pull Request 113 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/113/files] h2. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-350) PR (113): Enable fast finish in Travis - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (113): Enable fast finish in Travis - ghoneycutt Pull request Enable fast finish in Travis has been closed. Add Comment PuppetDB / PDB-350 PR (113): Enable fast finish in Travis - ghoneycutt h2. Enable fast finish in Travis * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 113 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/113] * [Pull Request 113 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/113/files] h2. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Adrien Thebo commented on an issue Re: puppet gem does not include platform specific gem dependencies Merged into master in 445ca3a; this should be released in 3.5.0. Add Comment Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies The puppet gem on windows has dependencies on win32-dir, etc, but these are not expressed in the gemspec file. So if you are developing a module, and attempt to `bundle install`, the transitive dependencies are not satisfied. The same issue exists in facter and hiera. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Rob Reynolds commented on an issue Re: puppet gem does not include platform specific gem dependencies There was some good discussion on PR #2283 about why we pinned specific versions in the first place. We went through and pinned all the versions of the gems that required native extensions. Add Comment Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies The puppet gem on windows has dependencies on win32-dir, etc, but these are not expressed in the gemspec file. So if you are developing a module, and attempt to `bundle install`, the transitive dependencies are not satisfied. The same issue exists in facter and hiera. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (HI-126) Build windows specific gem
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Hiera / HI-126 Build windows specific gem Change By: Adrien Thebo Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (HI-126) Build windows specific gem
Title: Message Title Adrien Thebo updated an issue Hiera / HI-126 Build windows specific gem Change By: Adrien Thebo Sprint: Week2014-1-22to2014-1-29 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (HI-126) Build windows specific gem
Title: Message Title Adrien Thebo commented on an issue Re: Build windows specific gem Merged into master in eec3180. Add Comment Hiera / HI-126 Build windows specific gem See PUP-1282 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (FACT-244) PR (614): (RE-814) Add initial support for building in a RHEL 7 mock - mckern
Title: Message Title gepetto-bot commented on an issue Re: PR (614): (RE-814) Add initial support for building in a RHEL 7 mock - mckern puppetcla commented: CLA signed by all contributors. Add Comment Facter / FACT-244 PR (614): (RE-814) Add initial support for building in a RHEL 7 mock - mckern h2. (RE-814) Add initial support for building in a RHEL 7 mock * Author: Ryan McKern r...@orangefort.com * Company: Puppet Labs * Github ID: [mckern|https://github.com/mckern] * [Pull Request 614 Discussion|https://github.com/puppetlabs/facter/pull/614] * [Pull Request 614 File Diff|https://github.com/puppetlabs/facter/pull/614/files] h2. Pull Re... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1501) PR (2292): (RE-816) Add initial support for building in a RHEL 7 mock - mckern
Title: Message Title gepetto-bot created an issue Puppet / PUP-1501 PR (2292): (RE-816) Add initial support for building in a RHEL 7 mock - mckern Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 23/Jan/14 1:39 PM Labels: github Priority: Normal Reporter: gepetto-bot (RE-816) Add initial support for building in a RHEL 7 mock Author: Ryan McKern r...@orangefort.com Company: Puppet Labs Github ID: mckern Pull Request 2292 Discussion Pull Request 2292 File Diff Pull Request Description
Jira (PUP-1153) Incorrect ordering of group and user resource purging
Title: Message Title Eric Sorenson commented on an issue Re: Incorrect ordering of group and user resource purging IMO if that's happening because of login.defs, that's how the system works and we should not try to second-guess it. I agree it's surprising, maybe a special note in the type reference is warranted...? Add Comment Puppet / PUP-1153 Incorrect ordering of group and user resource purging I am using the following below code to purge/remove all unmanaged (to Puppet) users and groups on a system so that only OS groups and users I allow can exist. I receive errors in my log though because Puppet will attempt to remove a (primary) group before it removes the corresponding user. Although a subsequent run has no errors (the user was eventual... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.
Jira (MCO-169) PR (156): (RE-817) Add initial support for building in a RHEL 7 mock - mckern
Title: Message Title gepetto-bot created an issue MCollective / MCO-169 PR (156): (RE-817) Add initial support for building in a RHEL 7 mock - mckern Issue Type: Task Assignee: Pieter Loubser Created: 23/Jan/14 1:54 PM Labels: github Priority: Normal Reporter: gepetto-bot (RE-817) Add initial support for building in a RHEL 7 mock Author: Ryan McKern r...@orangefort.com Company: Puppet Labs Github ID: mckern Pull Request 156 Discussion Pull Request 156 File Diff Pull Request Description Building in an x86_64 mock, since RHEL has not yet provided a 32-bit release. (webhooks-id: 8affad8151cb36b103dadc23721d61ab)
Jira (PDB-351) PR (813): (RE-818) Add initial support for building in a RHEL 7 mock - mckern
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-351 PR (813): (RE-818) Add initial support for building in a RHEL 7 mock - mckern Issue Type: Task Assignee: Unassigned Created: 23/Jan/14 2:07 PM Labels: github Priority: Normal Reporter: gepetto-bot (RE-818) Add initial support for building in a RHEL 7 mock Author: Ryan McKern r...@orangefort.com Company: Puppet Labs Github ID: mckern Pull Request 813 Discussion Pull Request 813 File Diff Pull Request Description Building in an x86_64 mock, since RHEL has not yet provided a 32-bit release. (webhooks-id: 5bac28c4769c81b63b3cac236f8b0904)
Jira (PDB-351) PR (813): (RE-818) Add initial support for building in a RHEL 7 mock - mckern
Title: Message Title gepetto-bot commented on an issue Re: PR (813): (RE-818) Add initial support for building in a RHEL 7 mock - mckern puppetlabs-jenkins commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-351 PR (813): (RE-818) Add initial support for building in a RHEL 7 mock - mckern h2. (RE-818) Add initial support for building in a RHEL 7 mock * Author: Ryan McKern r...@orangefort.com * Company: Puppet Labs * Github ID: [mckern|https://github.com/mckern] * [Pull Request 813 Discussion|https://github.com/puppetlabs/puppetdb/pull/813] * [Pull Request 813 File Diff|https://github.com/puppetlabs/puppetdb/pull/813/files] h2. Pul... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1406) PR (2236): Add ability to override default system confdir and vardir - jeffmccune
Title: Message Title gepetto-bot commented on an issue Re: PR (2236): Add ability to override default system confdir and vardir - jeffmccune jeffmccune commented: The purpose of the change is to enable those who are currently rebuilding puppet manually to avoid doing so and instead use the official release in an automated fashion. The alternatives proposed don't address the primary use case and as such would defeat the purpose of the change in the first place. Go ahead and close this pull request unless there's some way we can move forward while taking the primary use case into account. Add Comment Puppet / PUP-1406 PR (2236): Add ability to override default system confdir and vardir - jeffmccune h2. Add ability to override default system confdir and vardir * Author: Jeff McCune j...@puppetlabs.com * Company: Puppet Labs * Github ID: [jeffmccune|https://github.com/jeffmccune] * [Pull Request 2236 Discussion|https://github.com/puppetlabs/puppet/pull/2236] * [Pull Request 2236 File Diff|https://github.com/puppetlabs/puppet/pull/2236/files] ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1368) Puppet on Windows segfaulting
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1368 Puppet on Windows segfaulting Change By: Joshua Cooper Assignee: JoshuaCooper PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1500) PR (216): Enable fast finish in Travis - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (216): Enable fast finish in Travis - ghoneycutt Pull request Enable fast finish in Travis has been closed. Add Comment Puppet / PUP-1500 PR (216): Enable fast finish in Travis - ghoneycutt h2. Enable fast finish in Travis * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 216 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/216] * [Pull Request 216 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/216/files] h2. Pull... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1502) PR (2293): (maint) Puppet fails to properly surface backtraces - Iristyle
Title: Message Title gepetto-bot created an issue Puppet / PUP-1502 PR (2293): (maint) Puppet fails to properly surface backtraces - Iristyle Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 23/Jan/14 3:03 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Puppet fails to properly surface backtraces Author: Ethan J. Brown Company: Github ID: Iristyle Pull Request 2293 Discussion Pull Request 2293 File Diff Pull Request Description
Jira (PUP-1502) PR (2293): (maint) Puppet fails to properly surface backtraces - Iristyle
Title: Message Title gepetto-bot commented on an issue Re: PR (2293): (maint) Puppet fails to properly surface backtraces - Iristyle Iristyle commented: @zaphod42 and @joshcooper you might want to take a gander at this. It came up last week before we had to make a concerted effort to straighten out the CI. Add Comment Puppet / PUP-1502 PR (2293): (maint) Puppet fails to properly surface backtraces - Iristyle h2. (maint) Puppet fails to properly surface backtraces * Author: Ethan J. Brown * Company: * Github ID: [Iristyle|https://github.com/Iristyle] * [Pull Request 2293 Discussion|https://github.com/puppetlabs/puppet/pull/2293] * [Pull Request 2293 File Diff|https://github.com/puppetlabs/puppet/pull/2293/files] h2. Pull Request Description -... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title gepetto-bot commented on an issue Re: PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar hlindberg commented: Managed to get a travis run and it was green. In order for this to be committed it should have a reference to a JIRA ticket. One was automatically created for this PR (PUP-1195). In order to save you the trouble of rebasing I decided to fix up the last details and merge this in. I will close this PR since I added the reference to (PUP-1195), squashed the commits up to the final implementation, and did some small changes to the documentation of the functions. (You are still credited with the commit as the author). Will be right back with a commit SHA once I have merged this in. Add Comment Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar h2. fix is_numeric/is_integer when checking non-string parameters * Author: Simon Effenberg * Company: * Github ID: [Savar|https://github.com/Savar] * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213] * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title gepetto-bot commented on an issue Re: PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar hlindberg commented: On master branch 2c8450d830453e452b819bfb05678768336c3031 Add Comment Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar h2. fix is_numeric/is_integer when checking non-string parameters * Author: Simon Effenberg * Company: * Github ID: [Savar|https://github.com/Savar] * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213] * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title gepetto-bot commented on an issue Re: PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar Pull request fix is_numeric/is_integer when checking non-string parameters has been closed. Add Comment Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar h2. fix is_numeric/is_integer when checking non-string parameters * Author: Simon Effenberg * Company: * Github ID: [Savar|https://github.com/Savar] * [Pull Request 213 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213] * [Pull Request 213 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/213/files] h2. Pull Reque... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1195) PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1195 PR (213): fix is_numeric/is_integer when checking non-string parameters - Savar Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
