Jira (PDB-716) HTTP API gets stuck
Title: Message Title Erik Daln commented on an issue Re: HTTP API gets stuck The only ruby versions used are ruby 1.8.7 (2010-08-16 patchlevel 302) [x86_64-linux] from Debian squeeze and ruby 2.0.0p384 (2014-01-12) [x86_64-linux-gnu] from Ubuntu Trusty. Add Comment PuppetDB / PDB-716 HTTP API gets stuck Sometimes the HTTP API seems to get completely stuck. Other parts continue working though according to logs. Attaching 10 stack trace dumps taken a few seconds apart with jstack -F pid 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/d/optout.
Jira (PUP-2931) Puppet CA sometimes resets certificate serial counter
Title: Message Title Mihkel Ader created an issue Puppet / PUP-2931 Puppet CA sometimes resets certificate serial counter Issue Type: Bug Affects Versions: 3.6.2 Assignee: Andy Parker Components: Server Created: 14/Jul/14 3:43 AM Environment: Puppet 3.x server, CentOS 6 x86_64 Priority: Major Reporter: Mihkel Ader We are running our Puppet masters on CentOS 6 with Passenger and stock Apache. Puppet CA's data files reside on NFS storage. Autosigning is turned on. Sometimes the serials of issued client certificates reset to 0x0001 with serious consequences - when someone revokes the duplicate 0x0001 client's certificate, the CA revokes its own cert too. Revoking the duplicate 0x0002 revokes the secondary Puppet master server's cert etc. This seems to happen when there are many simultaneous certificate requests coming in. There are no unusual messages in logs. Sample from inventory.txt file: 0x02bd 2014-04-08T06:07:01GMT 2019-04-08T06:07:01GMT /CN=somenode123 0x02be 2014-04-08T06:07:01GMT 2019-04-08T06:07:01GMT
Jira (PDB-760) PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund Pull request (docs) Port recent docs revisions to 1.6.x branch has been closed. Add Comment PuppetDB / PDB-760 PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund h2. (docs) Port recent docs revisions to 1.6.x branch * Author: Nick Fagerlund * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1012 Discussion|https://github.com/puppetlabs/puppetdb/pull/1012] * [Pull Request 1012 File Diff|https://github.com/puppetlabs/puppetdb/pull/1012/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 at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-758) PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-758 PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund Change By: Kenneth Barber Sprint: 20140702to20140716 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/d/optout.
Jira (PDB-760) PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-760 PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund Change By: Kenneth Barber Sprint: 20140702to20140716 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/d/optout.
Jira (PDB-761) PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-761 PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund Change By: Kenneth Barber Sprint: 20140702to20140716 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/d/optout.
Jira (PDB-761) PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund Pull request (docs) Fix glitches noticed while backporting recent revisions to 1.6.x has been closed. Add Comment PuppetDB / PDB-761 PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund h2. (docs) Fix glitches noticed while backporting recent revisions to 1.6.x * Author: Nick Fagerlund * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 1013 Discussion|https://github.com/puppetlabs/puppetdb/pull/1013] * [Pull Request 1013 File Diff|https://github.com/puppetlabs/puppetdb/pull/1013/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
Jira (PDB-759) PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-759 PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund Change By: Kenneth Barber Sprint: 20140702to20140716 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/d/optout.
Jira (PDB-760) PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-760 PR (1012): (docs) Port recent docs revisions to 1.6.x branch - nfagerlund Change By: Kenneth Barber Story Points: 0 Fix Version/s: 1.6.x 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/d/optout.
Jira (PDB-761) PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-761 PR (1013): (docs) Fix glitches noticed while backporting recent revisions to 1.6.x - nfagerlund Change By: Kenneth Barber Story Points: 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/d/optout.
Jira (PDB-759) PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-759 PR (1011): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund Change By: Kenneth Barber Story Points: 0 Fix Version/s: 2.1.x 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/d/optout.
Jira (PDB-758) PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-758 PR (1010): (docs) Revise API docs for updated info, clarity, consistency, and formatting - nfagerlund Change By: Kenneth Barber Story Points: 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/d/optout.
Jira (PUP-1527) After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Title: Message Title
Matheus Gomes commented on an issue
Re: After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
Quoting resources integers was unsuccessful, had to downgraded the client to puppet v3.2.4
Add Comment
Puppet / PUP-1527
After upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources taken from hiera
gtAfter upgrade from 3.3.2-1 to 3.4.2-1 naginator fails to create config from exported resources, data taken from hiera. When hiera has the following data: check_apt_security : { check_command : check_nrpe_1arg!check_apt_security, contact_groups : sladmins, normal_check_interval : 10, ...
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/d/optout.
Jira (PUP-2859) specify call by name / call by position
Title: Message Title Henrik Lindberg commented on an issue Re: specify call by name / call by position Terms changed to pass by position and pass by name. Add Comment Puppet / PUP-2859 specify call by name / call by position We now have two distinct ways of calling; functions and lambdas use call by position, and instantiation of classes and defines use call by name. The EPP functions pass arguments to templates via call by name. The Puppet Language Specification should document this in one place (rather than repeat the rules). 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/d/optout.
Jira (PDB-762) lein run export fails on failed or unchanged reports
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-762 lein run export fails on failed or unchanged reports Change By: Kenneth Barber Story Points: 2 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/d/optout.
Jira (PDB-763) Handle creation of pg_trgm indexes for structure facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-763 Handle creation of pg_trgm indexes for structure facts Change By: Kenneth Barber Sprint: 20140730to20140813 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/d/optout.
Jira (PDB-121) Add Ruby 2.0 to spec test matrix for puppetdb
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-121 Add Ruby 2.0 to spec test matrix for puppetdb Change By: Kenneth Barber Sprint: 20140716to 20140730 to20140813 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/d/optout.
Jira (PDB-763) Handle creation of pg_trgm indexes for structure facts
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-763 Handle creation of pg_trgm indexes for structure facts Issue Type: Task Assignee: Unassigned Created: 14/Jul/14 8:10 AM Fix Versions: 2.2.0 Priority: Normal Reporter: Kenneth Barber This task has been split out due to the nature of installing extensions and what not. The goal here is to have our software notice if the pg_trgm module isn't installed, and warn the user. This is because the puppetdb db user won't often have superuser permissions to do this itself. If the pg_trgm index exists, we should install the correct indexes on fact_values.value_string and fact_paths.path to get the performance we want. We might need to do this as a separate task from migration, but after migration specifically. I believe the trgm indexes full benefits are surfaced in 9.3, so we might want to also cowardly refuse the indexes unless they are running 9.3 or above. I'm more inclined to want to avoid the index type in 9.2 and below, since I'm not sure its that fast there for regexp searching. While we are at it, we could deprecate pre 9.3 databases, we already have the code for this so the change is pretty minor.
Jira (PDB-716) HTTP API gets stuck
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-716 HTTP API gets stuck Change By: Kenneth Barber Sprint: 20140716to 20140730 to20140813 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/d/optout.
Jira (PDB-745) Structured facts: dangling reference cleanup jobs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-745 Structured facts: dangling reference cleanup jobs Change By: Kenneth Barber Sprint: 20140716 20140702 to 20140730 20140716 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/d/optout.
Jira (PDB-762) lein run export fails on failed or unchanged reports
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-762 lein run export fails on failed or unchanged reports Change By: Kenneth Barber Fix Version/s: 2.2.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/d/optout.
Jira (PDB-762) `puppetdb export` fails on failed or unchanged reports
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-762 `puppetdb export` fails on failed or unchanged reports Change By: Kenneth Barber Summary: leinrun `puppetdb export ` failsonfailedorunchangedreports 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/d/optout.
Jira (PUP-2883) epp does not handle empty template
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2883
epp does not handle empty template
Change By:
Henrik Lindberg
Wheneppistoldtoevaluateanemptytemplate,theresultisacomplaintthattheendofinputisreached.eppshouldproduceanemptystringinthissituationandnotcomplain.Toreproduce:{code}noticeinline_epp(@ ( END),{x=world})%-|$x|%|-END{code}Thistemplatehasaparameter,butnoothercontentinthetemplate.
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/d/optout.
Jira (PUP-2883) epp does not handle empty template
Title: Message Title
Henrik Lindberg commented on an issue
Re: epp does not handle empty template
This also reproduces the problem:
notice inline_epp(@(END)) -END {end}
The problem occurs because the grammar requires there to be at least one statement in the body (a string to emit, or some puppet _expression_). Thus, this is not a big problem, but the error message is baffling. The grammar should be changed to allow for an empty epp body. If we want to validate that epp actually contains something we can handle that in validation, but it is questionable if that should be done, since the configuration may want the logic to use a template that is different on different branches, and sometimes want the configuration to have a template that is empty.
Thus, the fix is to only change the grammar to accept an empty body.
Add Comment
Puppet / PUP-2883
epp does not handle empty template
When epp is told to evaluate an empty template, the result is a complaint that the end of input is reached. epp should produce an empty string in this situation and not complain. To reproduce: {code} notice inline_epp(@(END), {x = world}) %-| $x| % |- END {code} This template has a parameter, but no other content in the template.
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title
Andy Parker commented on an issue
Re: Puppet 3.6.x future parser introduces dependency cycles
Tristan Helmich, puppet 3.7.0 is slated for the end of August.
Add Comment
Puppet / PUP-2839
Puppet 3.6.x future parser introduces dependency cycles
In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): {code} puppet apply --graph --modulepath /vagrant/modules/ --...
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/d/optout.
Jira (PDB-745) Structured facts: dangling reference cleanup jobs
Title: Message Title Kenneth Barber assigned an issue to Wyatt Alt PuppetDB / PDB-745 Structured facts: dangling reference cleanup jobs Change By: Kenneth Barber Assignee: WyattAlt 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/d/optout.
Jira (PDB-746) Query support for structured facts /facts - Globbing/Regexp support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-746 Query support for structured facts /facts - Globbing/Regexp support Change By: Kenneth Barber Sprint: 20140716to 20140730 to20140813 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/d/optout.
Jira (PDB-716) HTTP API gets stuck
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-716 HTTP API gets stuck Change By: Kenneth Barber Sprint: 20140730to 20140813 to20140827 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/d/optout.
Jira (PDB-121) Add Ruby 2.0 to spec test matrix for puppetdb
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-121 Add Ruby 2.0 to spec test matrix for puppetdb Change By: Kenneth Barber Sprint: 20140730to 20140813 to20140827 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/d/optout.
Jira (PDB-718) Fact Path Endpoint
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-718 Fact Path Endpoint Change By: Kenneth Barber Sprint: 20140730to 20140813 to20140827 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/d/optout.
Jira (PDB-565) Support trusted facts in PuppetDB fact storage
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-565 Support trusted facts in PuppetDB fact storage Change By: Kenneth Barber Sprint: 20140716to 20140730 to20140813 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/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Charlie Sharpsteen Component/s: TypesandProviders Component/s: Client Affects Version/s: 3.6.2 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/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Charlie Sharpsteen Assignee: 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/d/optout.
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Facter / FACT-569 Run Facter acceptance against ruby 2.0 x64 Change By: Ethan Brown Assignee: EthanBrown 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/d/optout.
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Facter / FACT-603 Allow to configure acceptance using github mirror Change By: Ethan Brown Assignee: EthanBrown 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/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) 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/d/optout.
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Run Facter acceptance against ruby 2.0 x64
Rebased against stable
Add Comment
Facter / FACT-569
Run Facter acceptance against ruby 2.0 x64
Facter's acceptance setup step for git will need to install the appropriate version of ruby based on the agent's architecture. See https://github.com/puppetlabs/facter/blob/facter-2/acceptance/setup/common/00_EnvSetup.rb#L37 Beaker's {{install_from_git}} method accepts a {{:rev}} parameter so it should be possible to specify the revision to checkout, e...
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/d/optout.
Jira (PUP-2526) puppet agent retry failed http requests
Title: Message Title Peter Drake commented on an issue Re: puppet agent retry failed http requests I did some work on this here: https://github.com/puppetlabs/puppet/pull/2870 Add Comment Puppet / PUP-2526 puppet agent retry failed http requests It would be nice if puppet agent had the ability had the ability to retry failed http requests to the puppet master. I have multiple puppet masters sitting behind a load balancer in AWS (ELB). Whenever we update a puppet master, the node is removed from the load balancer while the update occurs. Unfortunately the AWS ELB does not allow quiescent remova... 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/d/optout.
Jira (PUP-2776) Adjust master acceptance/tests/environment/{static,dynamic,directory}.rb to run in PE
Title: Message Title
Joshua Partlow commented on an issue
Re: Adjust master acceptance/tests/environment/{static,dynamic,directory}.rb to run in PE
The work on PUP-417 required this change as well for FOSS Passenger testing, and it is rolled up in the PR for that ticket.
Add Comment
Puppet / PUP-2776
Adjust master acceptance/tests/environment/{static,dynamic,directory}.rb to run in PE
I believe PE 3.4.x will be based on Puppet master. We have new environment tests in master which currently rely on setting --confdir in the Beaker with_puppet_running_on() :__commandline_args__ setting so that the puppet master is started with those command line arguments. PE tests can't use this setting, as we are just restarting the rack environment a...
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 (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Facter / FACT-569 Run Facter acceptance against ruby 2.0 x64 Change By: Josh Cooper Fix Version/s: 2.2.0 Fix Version/s: 2.1.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/d/optout.
Jira (PUP-2452) Refreshable feature on package type
Title: Message Title Andy Parker assigned an issue to Anthony Ryan Moving this to Failed Review because there are problems that were uncovered when containment is used. There is some discussion of the problem in the PR, but the gist of it is that many resources by be able to perform a refresh, but it might not be desirable to allow it to. In order to take this feature, there needs to be a way of controlling refresh better. Puppet / PUP-2452 Refreshable feature on package type Change By: Andy Parker Assignee: AnthonyRyan 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/d/optout.
Jira (PUP-2932) Document the behavior of private classes
Title: Message Title Justin Holguin created an issue Puppet / PUP-2932 Document the behavior of private classes Issue Type: Bug Assignee: Unassigned Created: 14/Jul/14 2:35 PM Priority: Normal Reporter: Justin Holguin Private classes have ostensibly been around for a while, but they don't actually behave any differently compared to non-private classes. Making private classes actually private is scoped out for Puppet 4 (PUP-523), so we'll need to keep any eye on that and update the docs (e.g., lang_classes) as necessary. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-855) On Windows allow using root path for file type
Title: Message Title Andy Parker commented on an issue Re: On Windows allow using root path for file type Rob Reynolds, if I'm reading this and the puppet-dev conversation correctly, it seems like this feature request is being rejected. If so, can you close it out and reply to the thread on puppet-dev just to make that clear? Add Comment Puppet / PUP-855 On Windows allow using root path for file type This would allow full path in a way that doesn't require specifying the drive to look at. When this is specified, we will use SYSTEMDRIVE. This would allow multiple computers with different system drives to be able to use the same manifests. This could also open the door for more platforms using the same manifest with less use of selectors based on the O... 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-2933) Could not parse for environment testing: Illegal fully qualified name in file
Title: Message Title
Nikolay Georgieff created an issue
Puppet / PUP-2933
Could not parse for environment testing: Illegal fully qualified name in file
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
14/Jul/14 3:18 PM
Priority:
Normal
Reporter:
Nikolay Georgieff
I'm getting rror 400 on SERVER: Could not parse for environment testing: Illegal fully qualified name in file /etc/puppet/manifests/site.pp at line 10:28 on node ucla-ws-xx1.xx..xxx
Puppet is not properly parsing include module::class
– Logs –
nfo: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d_authjsondump.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Debug: Failed to load library 'msgpack' for feature 'msgpack' Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing Debug: catalog supports formats: pson dot yaml b64_zlib_yaml raw Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment testing: Illegal fully qualified name in file /etc/puppet/manifests/site.pp at line 10:28 on node -ws-t01.xx..edu Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run
And here is my default.pp. Line 10 is mcollective-agents::facts
node default { include
Jira (PUP-2933) Could not parse for environment testing: Illegal fully qualified name in file
Title: Message Title
Nikolay Georgieff updated an issue
Puppet / PUP-2933
Could not parse for environment testing: Illegal fully qualified name in file
Change By:
Nikolay Georgieff
I'mgettingrror400onSERVER:Couldnotparseforenvironmenttesting:Illegalfullyqualifiednameinfile/etc/puppet/manifests/site.ppatline10:28onnodeucla-ws-xx1.xx..xxxPuppetisnotproperlyparsingincludemodule::class--Logs--nfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/pe_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/root_home.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/concat_basedir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d_authjsondump.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/puppet_vardir.rbDebug:Failedtoloadlibrary'msgpack'forfeature'msgpack'Debug:Puppet::Network::Format[msgpack]:featuremsgpackismissingDebug:catalogsupportsformats:psondotyamlb64_zlib_yamlrawError:Couldnotretrievecatalogfromremoteserver:Error400onSERVER:Couldnotparseforenvironmenttesting:Illegalfullyqualifiednameinfile/etc/puppet/manifests/site.ppatline10:28onnode-ws-t01.xx..eduWarning:NotusingcacheonfailedcatalogError:Couldnotretrievecatalog;skippingrunAndhereismydefault.pp.Line10ismcollective-agents::facts {quote} nodedefault{includemcollective-agentsincludemcollective-agents::factsincludepuppet-cron#includedisco#includeqguard#includepuppet-upgradeincludeucla_base} {quote} IfIcommentthelineI'mabletorunpuppet.
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
Jira (FACT-598) fqdn is concatenation of hostname -s and domainname instead of hostname -f
Title: Message Title
Adrien Thebo commented on an issue
Re: fqdn is concatenation of hostname -s and domainname instead of hostname -f
This works around a corner case that we don't want to support, closing this as wontfix.
Add Comment
Facter / FACT-598
fqdn is concatenation of hostname -s and domainname instead of hostname -f
Some systems have a hostname other than the concatenation of hostname and dnsdomainname. Or put differently, the {{hostname -s}} is not equal to {{hostname}}: {noformat} $ hostname -f systemX.locationY.domain.tld $ hostname domain-systemX {noformat} This keeps the local hostname short yet detailed enough. In that case, the right FQDN would b...
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/d/optout.
Jira (FACT-598) fqdn is concatenation of hostname -s and domainname instead of hostname -f
Title: Message Title Adrien Thebo updated an issue Facter / FACT-598 fqdn is concatenation of hostname -s and domainname instead of hostname -f Change By: Adrien Thebo Component/s: Community 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/d/optout.
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Josh Cooper commented on an issue Re: Allow to configure acceptance using github mirror Rob ReynoldsEthan Brown it looks the facter acceptance jobs will need to be audited to ensure they are defaulting GIT_SERVER to github.delivery.puppetlabs.net Add Comment Facter / FACT-603 Allow to configure acceptance using github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. 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/d/optout.
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Adrien Thebo commented on an issue Re: Allow to configure acceptance using github mirror +1 for deferring on the acceptance test refactoring. Add Comment Facter / FACT-603 Allow to configure acceptance using github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. 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/d/optout.
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Ethan Brown commented on an issue Re: Allow to configure acceptance using github mirror All set – a few jobs were modified to use internal mirror. Add Comment Facter / FACT-603 Allow to configure acceptance using github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. 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/d/optout.
Jira (PUP-2818) Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled
Title: Message Title Ethan Brown commented on an issue Re: Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled After merging the PUP-2881 code, the error from a disabled scheduler service is different. Executing Will now generate an error like this: execute the following command line C:\source\puppet [ticket/master/PUP-2881-update-win32-taskscheduler +4 ~0 -0 !] bundle exec puppet resource scheduled_task get the following results DL is deprecated, please use Fiddle DL is deprecated, please use Fiddle Error: Could not run: Failed to call #Win32::TaskScheduler::COM::Task:0x0006c0a200::GetAccountInformation with HRESULT: -2147216619.: The Task Scheduler Service is not running. I believe that a simple call can be made at some point early in the task scheduler loading to bail out earlier than the call to GetAccountInformation, but this is a better error than what was occurring previously. Add Comment Puppet / PUP-2818 Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled This ticket should
Jira (PUP-2818) Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled
Title: Message Title Ethan Brown commented on an issue Re: Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled FYI, psexec is a good way to kill the scheduler service locally. http://social.technet.microsoft.com/Forums/windowsserver/en-us/b9e5a4c0-073c-42fd-a390-8b2aee407a4f/task-scheduler-service-schedule-cannot-be-stopped-in-windows-2008-r1-?forum=winserversecurity psexec.exe -i -s CMD to launch a command prompt as system, then sc stop scheduler Add Comment Puppet / PUP-2818 Win32-taskscheduler gem 0.2.2 (patched in vendored repo) crashes when task scheduler is disabled This ticket should represent more of a verification of behavior in the latest 0.3.0 taskscheduler gem after upgrading to the latest version during x64 FFI work. According to user reports, a crash occurs at the following line of puppet-win32-ruby: https://github.com/puppetlabs/puppet-win32-ruby/blob/1.9.3-p484.3/ruby/lib/ruby/gems/1.9.1/gems/win32-ta... 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
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Joshua Partlow assigned an issue to Roger Ignazio Roger Ignazio I've put this into ready for merge, and assigned it to you. It's waiting on QENG-188...perhaps it would be better in needs information? Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. Change By: Joshua Partlow Assignee: RogerIgnazio 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/d/optout.
Jira (FACT-613) Create structured processor fact
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Facter / FACT-613 Create structured processor fact Change By: Kylo Ginsberg 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/d/optout.
Jira (PUP-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Andy Parker commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output Merged fix into master in 634a3f Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output 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/d/optout.
Jira (PUP-2807) 4x logging functions does not include container
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2807 4x logging functions does not include container Change By: Joshua Partlow Assignee: JoshuaPartlow 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/d/optout.
Jira (PDB-762) `puppetdb export` fails on failed or unchanged reports
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-762 `puppetdb export` fails on failed or unchanged reports Change By: Wyatt Alt Sprint: 20140716 20140702 to 20140730 20140716 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/d/optout.
Jira (PUP-2859) specify call by name / call by position
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2859 specify call by name / call by position Change By: Andy Parker Assignee: AndyParker 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/d/optout.
Jira (PDB-762) `puppetdb export` fails on failed or unchanged reports
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-762 `puppetdb export` fails on failed or unchanged reports Change By: Wyatt Alt Assignee: WyattAlt 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/d/optout.
Jira (PUP-2859) specify call by name / call by position
Title: Message Title Andy Parker commented on an issue Re: specify call by name / call by position Merged into specifications in dcde48 Add Comment Puppet / PUP-2859 specify call by name / call by position We now have two distinct ways of calling; functions and lambdas use call by position, and instantiation of classes and defines use call by name. The EPP functions pass arguments to templates via call by name. The Puppet Language Specification should document this in one place (rather than repeat the rules). 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/d/optout.
Jira (PUP-2807) 4x logging functions does not include container
Title: Message Title Joshua Partlow commented on an issue Re: 4x logging functions does not include container Merged to master in 7b44fb55 Add Comment Puppet / PUP-2807 4x logging functions does not include container The logging functions (notice, error, etc) were modified in future evaluator to use the new function API and the new loaders. In the new implementation, it was missed that the old (i.e. current) functions also output the name of the calling container (i.e. the resource owning the scope). First - do we want it to continue working the same way? (And if... 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/d/optout.
Jira (PUP-2883) epp does not handle empty template
Title: Message Title
Joshua Partlow commented on an issue
Re: epp does not handle empty template
Merged to master in d766dd6d
Add Comment
Puppet / PUP-2883
epp does not handle empty template
When epp is told to evaluate an empty template, the result is a complaint that the end of input is reached. epp should produce an empty string in this situation and not complain. To reproduce: {code} notice inline_epp(@(END), {x = world}) %-| $x| % |- END {code} This template has a parameter, but no other content in the template.
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/d/optout.
Jira (PUP-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2714 Future parser returns nil when parsing a source that contains no statements Change By: Joshua Partlow Assignee: JoshuaPartlow 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/d/optout.
Jira (PUP-2693) LiteralString class parameters get parsed with positioning information that includes a negative length
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2693 LiteralString class parameters get parsed with positioning information that includes a negative length Change By: Joshua Partlow Assignee: JoshuaPartlow 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/d/optout.
Jira (PUP-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-2714 Future parser returns nil when parsing a source that contains no statements Change By: Joshua Partlow Assignee: JoshuaPartlow 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/d/optout.
Jira (PUP-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Brandon High commented on an issue Re: puppet module tool on windows will (sometimes) create a PaxHeader directory PR https://github.com/puppetlabs/puppet/pull/2872 has been added with a proposed solution. Add Comment Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory In Puppet 3.2 the module tool started using minitar when the tar executable is not present. It turns out that minitar does not understand the [PAX](http://en.wikipedia.org/wiki/Pax_(Unix)) format. An example of a module that was created with this is [liamjbennet/win_facts v0.0.1](https://forge.puppetlabs.com/liamjbennett/win_facts/0.0.1). When that mod... 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/d/optout.
Jira (PUP-2693) LiteralString class parameters get parsed with positioning information that includes a negative length
Title: Message Title
Joshua Partlow commented on an issue
Re: LiteralString class parameters get parsed with positioning information that includes a negative length
Merge to master in 7e69be37d
Add Comment
Puppet / PUP-2693
LiteralString class parameters get parsed with positioning information that includes a negative length
When using the future parser, any class parameter with a LiteralString value receive positioning information with a negative length: {code} # param_test.rb require 'puppet' require 'puppet/pops' parser = Puppet::Pops::Parser::Parser.new result = parser.parse_string -EOM class test::class ( $param_one = undef, $param_two = 'some string...
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/d/optout.
Jira (PUP-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2714 Future parser returns nil when parsing a source that contains no statements Change By: Joshua Partlow Assignee: JoshuaPartlow 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/d/optout.
Jira (PUP-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-2714 Future parser returns nil when parsing a source that contains no statements Change By: Joshua Partlow Assignee: JoshuaPartlow 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/d/optout.
Jira (PUP-2891) creating a resource override for a Class fails (future parser)
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2891 creating a resource override for a Class fails (future parser) Change By: Joshua Partlow Assignee: JoshuaPartlow 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/d/optout.
Jira (PUP-1541) Separate out hold state into a separate property
Title: Message Title Andy Parker updated an issue Puppet / PUP-1541 Separate out hold state into a separate property Change By: Andy Parker Issue Type: Task 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/d/optout.
Jira (PUP-1541) Separate out hold state into a separate property
Title: Message Title Andy Parker updated an issue Puppet / PUP-1541 Separate out hold state into a separate property Change By: Andy Parker Summary: PR(2309): Separateoutholdstateintoaseparateproperty -lollipopman 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/d/optout.
Jira (PUP-2891) creating a resource override for a Class fails (future parser)
Title: Message Title
Joshua Partlow commented on an issue
Re: creating a resource override for a Class fails (future parser)
Merged to master in 2fd07724
Add Comment
Puppet / PUP-2891
creating a resource override for a Class fails (future parser)
{code} Class[a] { x = 'the default' } {code} Results in the error: {code} Error: Evaluation Error: Error while evaluating a Resource Override, undefined method `type_name' for Puppet::Pops::Types::PHostClassType:Puppet::Pops::Types::PHostClassType at /Users/henrik/git/puppet/bar.pp:4:1 on node henriks-macbook-pro.local /Users/henrik/git/puppet/lib/...
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/d/optout.
Jira (PUP-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2714 Future parser returns nil when parsing a source that contains no statements Change By: Joshua Partlow Assignee: JoshuaPartlow 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/d/optout.
Jira (PDB-764) Malformed post-conditions in query.clj
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-764 Malformed post-conditions in query.clj Issue Type: Bug Affects Versions: 2.1.0 Assignee: Unassigned Created: 14/Jul/14 7:02 PM Priority: Normal Reporter: Wyatt Alt Several cases of missing parentheses like the following: https://github.com/puppetlabs/puppetdb/blob/master/src/com/puppetlabs/puppetdb/query.clj#L367 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2757) Apply parses everything twice
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2757 Apply parses everything twice Change By: Josh Cooper 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/d/optout.
Jira (PUP-894) Too easy to hit CRL not yet valid for host (and not very informative)
Title: Message Title Josh Cooper commented on an issue Re: Too easy to hit CRL not yet valid for host (and not very informative) Acceptance failure https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-Per-Commit-master/698/label=acc-coord,platform=rhel6/console Error: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [CRL is not yet valid for /CN=efp9ev0z2mc2mv5.delivery.puppetlabs.net] 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
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Josh Cooper commented on an issue Re: Allow to configure acceptance using github mirror Ethan Brown I had to undo the changes to the jenkins jobs, because some of the jobs will use an EC2 coordinator node that can't connect to our internal mirror. Roger Ignazio has plans to make such that individual repos don't need to translate github URLs (INFTOOL-79), but I don't know how far off that is. In the meantime, this ticket is blocked by QENG-936. Add Comment Facter / FACT-603 Allow to configure acceptance using github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. 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 (FACT-603) Facter acceptance should use our github mirror
Title: Message Title Josh Cooper updated an issue Facter / FACT-603 Facter acceptance should use our github mirror Change By: Josh Cooper Summary: Allowtoconfigure Facter acceptance using shoulduseour githubmirror 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/d/optout.
