Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Rakesh Kathpal commented on an issue Re: Pre/Post-run commands don't work under Windows Hi, I am facing this issue currently on multiple windows servers, is there a workaround for this issue I am on open source puppet 3.4.2 Add Comment Puppet / PUP-1431 Pre/Post-run commands don't work under Windows If a postrun or prerun command is specified in puppet.conf on a Windows host it will fail to execute with a message like the following: Debug: Executing 'C:\Windows\System32\cmd.exe /c type NUL C:\from_postrun.txt' Error: Could not run command from postrun_command: CreateProcess() failed: The system cannot find the file specified.Example postr... 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-2872) Problem with variable in array for template
Title: Message Title
Vincent commented on an issue
Re: Problem with variable in array for template
Yes, sure, there it is :
class testvincent (
$datadir = '/home/test',
$conf = [
datadir = ${datadir},
log-file = /var/log/${fqdn},
],
) {
$echo = inline_template(%= conf %)
notify{$echo:}
notify{$datadir:}
}
This give me the following :
Notice: datadir = log-file = /var/log/my.hostname.com
Notice: /home/test
That just confirm my problem
Add Comment
Puppet / PUP-2872
Problem with variable in array for template
I have the following parameters in my class manifest : {code} $datadir = '/home/test', $confarray = [datadir = ${datadir},log-file = /var/log/${fqdn}], {code} And the following in my conf template : {code} %- @confarray.each do |conf| -% %= conf % %- end -% {code} The output on my conf file is : {code} datadir = log-file = /var/log...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-675) init.d script silently fails if PIDfile is missing
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-675 init.d script silently fails if PIDfile is missing Change By: Kenneth Barber Sprint: 20140521to20140604,20140604to20140618 ,20140618to20140702 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-2429) Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
Title: Message Title
Kenneth Barber commented on an issue
Re: Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
Peter Huene I've confirmed this on my own box, works a treat:
{authenticated=remote, certname=puppetdb1.vm, extensions={}}
I guess this means that the way we merge it or store it in PuppetDB is up for question, I was hoping to just insert it at the top level under 'trusted' as a real fact, but I'm wary of name collision. What are your thoughts on this?
Add Comment
Puppet / PUP-2429
Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
PDB-565 covers the need to store trusted facts in PuppetDB, but right now I don't believe we have a suitable API contract for getting this information from Puppet. At least I can't find one, neither the facts terminus nor the catalog terminus supplies this for example. One solution to this is to include the set of trusted facts in the request object su...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-565) Support trusted facts in PuppetDB fact storage
Title: Message Title Kenneth Barber assigned an issue to Unassigned PuppetDB / PDB-565 Support trusted facts in PuppetDB fact storage Change By: Kenneth Barber Assignee: EricSorenson 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 commented on an issue
Re: Support trusted facts in PuppetDB fact storage
Peter Huene has found a way to do this in the save method for the puppetdb facts terminus:
trusted = Puppet.lookup(:trusted_information) { Puppet::Context::TrustedInformation.local(request.node) }.to_h if Puppet[:trusted_node_data]
Works perfectly:
{authenticated=remote, certname=puppetdb1.vm, extensions={}}
Still need to decide how to inject this/store this in PuppetDB.
Add Comment
PuppetDB / PDB-565
Support trusted facts in PuppetDB fact storage
Since Puppet 3.4, we've added a new top-scope, immutable hash called 'trusted' which is exposed in the DSL and populated with the authenticated certname from the SSL certificate that made the catalog request. In addition, custom attributes can be added to the certificate and will also show up in the trusted hash (see http://docs.puppetlabs.com/puppet/late...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-743) Report submission fails on JSON::ParserError
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-743 Report submission fails on JSON::ParserError 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-743) Report submission fails on JSON::ParserError
Title: Message Title Kenneth Barber commented on an issue Re: Report submission fails on JSON::ParserError Umm, this doesn't contain any of the logging information we had requested for postgresql. We still don't have enough data to reproduce this Kurt Wall ... your team or whoever manages and writes these tests will have to continue to work with one of our team members to continue to find a way to reproduce this. Add Comment PuppetDB / PDB-743 Report submission fails on JSON::ParserError We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... 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
Jira (PDB-726) PuppetDB 2.1.0 Release - July 8th, 2014
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-726 PuppetDB 2.1.0 Release - July 8th, 2014 Change By: Kenneth Barber Summary: PuppetDB2.1.0Release- July8th, 2014 /7/8 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: 20140618to 20140702 to20140716 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-744) Publish Blog
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-744 Publish Blog Issue Type: Sub-task Assignee: Unassigned Created: 02/Jul/14 5:19 AM Priority: Normal Reporter: Kenneth Barber Publish the blog we started to develop on here: https://docs.google.com/a/puppetlabs.com/document/d/1E0ZqmDtb6zu_5Ce_H8Mh8sf9TnKg8L4vksO0atPhYgg/edit Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-206) When a query contains a comparison between a string and a boolean, an Internal Server Error response is returned
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-206 When a query contains a comparison between a string and a boolean, an Internal Server Error response is returned 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-745) Structured facts: dangling reference cleanup jobs
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-745 Structured facts: dangling reference cleanup jobs Issue Type: Task Assignee: Unassigned Created: 02/Jul/14 5:46 AM Fix Versions: 2.2.0 Priority: Normal Reporter: Kenneth Barber The new structured facts schema is fairly normalized, so it may suffer some dangling references when the fact data gets replaced/updated. This task is to track the cleanup task work required. The normal GC routines already have many examples of this. Add Comment
Jira (PDB-708) Storage for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-708 Storage for structured facts Change By: Kenneth Barber Story Points: 13 11 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-50) Additional query support for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-50 Additional query support for structured facts Change By: Kenneth Barber Sprint: 20140716to20140730 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-709) v4 facts endpoint changed for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-709 v4 facts endpoint changed for structured facts Change By: Kenneth Barber Sprint: 20140716to20140730 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-50) Additional query support for structured facts - exact matches
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-50 Additional query support for structured facts - exact matches Change By: Kenneth Barber Story Points: 13 5 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-50) Additional query support for structured facts - exact matches
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-50 Additional query support for structured facts - exact matches Change By: Kenneth Barber Summary: Additionalquerysupportforstructuredfacts -exactmatches 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) Additional query support for structured facts - Globbing/Regexp support
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-746 Additional query support for structured facts - Globbing/Regexp support Issue Type: Task Assignee: Unassigned Created: 02/Jul/14 5:53 AM Priority: Normal Reporter: Kenneth Barber This ticket tracks the work required to add regexp/globbing support for the new structured facts work, involving path/value matching (instead of name/value matching as before). Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-746) Additional query support for structured facts - Globbing/Regexp support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-746 Additional query support for structured facts - Globbing/Regexp support 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-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: 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-708) Storage for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-708 Storage for structured facts Change By: Kenneth Barber Story Points: 11 8 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-747) Produce work-able schema for structured facts
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-747 Produce work-able schema for structured facts Issue Type: Task Assignee: Unassigned Created: 02/Jul/14 5:55 AM Priority: Normal Reporter: Kenneth Barber This task tracks the work to create a schema for structured facts. If we break out the work amongst multiple people, this ticket will require possibly some sort of migration of SQL script as an output so others can use it. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-747) Produce work-able schema for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-747 Produce work-able schema for structured facts 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-711) Factset endpoint for simplifying structure fact export and full retrieval
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-711 Factset endpoint for simplifying structure fact export and full retrieval 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-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: 20140827to20140910 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: 20140813to20140827 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-713) Modify anonymization tool to support structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-713 Modify anonymization tool to support structured facts Change By: Kenneth Barber Sprint: 20140813to20140827 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-2876) Better error messaging for un-accessible puppet.conf
Title: Message Title Gerrard Geldenhuis created an issue Puppet / PUP-2876 Better error messaging for un-accessible puppet.conf Issue Type: Improvement Assignee: Aaron Armstrong Components: PE Created: 02/Jul/14 5:59 AM Priority: Normal Reporter: Gerrard Geldenhuis If the permissions or ownership for puppet.conf changes in such a way that the pe_puppet user can access it anymore puppet errors with a completely unintelligible error message. The error message is a lot of ruby calls and raw html code displayed on the command line. A simple unable to read puppet.conf would be much easier to debug. Add Comment
Jira (PDB-712) Modify export and import tool to support structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-712 Modify export and import tool to support structured facts Change By: Kenneth Barber Sprint: 20140813to20140827 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-747) Produce work-able schema for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-747 Produce work-able schema for structured facts Change By: Kenneth Barber Thistasktrackstheworktocreateaschemaforstructuredfacts.Ifwebreakouttheworkamongstmultiplepeople,thisticketwillrequirepossiblysomesortofmigrationofSQLscriptasanoutputsootherscanuseit. Wealreadyhaveastartontheschemainthedesigndoc:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-712) Modify export and import tool to support structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-712 Modify export and import tool to support structured facts Change By: Kenneth Barber Withstructuredfactstheexportandimporttoolwillneedtobemodifiedtosupportthenewformat. Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-50) Additional query support for structured facts - exact matches
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-50 Additional query support for structured facts - exact matches Change By: Kenneth Barber Thistasktrackstheeffortsforprovidingqueryoperatorssuitableforuserstoquerydatainsidestructuredfacts(asopposedtojustmatchingtheentirecontentonly). Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-709) v4 facts endpoint changed for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-709 v4 facts endpoint changed for structured facts Change By: Kenneth Barber Thisticketcoverstheworktochangethe/factsV4endpointtoreturnthenewstructuredfactsawarepathnameasperthedesign. Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-713) Modify anonymization tool to support structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-713 Modify anonymization tool to support structured facts Change By: Kenneth Barber Oncestructuredfactsisenabledtheanonymizationtoolwillneedtobemodifiedtosupportthenewformat. Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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 Thisendpointwillreturnallfactsforallfactpaths,toaidwithconsolebasedauto-completion. Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-711) Factset endpoint for simplifying structure fact export and full retrieval
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-711 Factset endpoint for simplifying structure fact export and full retrieval Change By: Kenneth Barber Factsetendpointforsimplifyingstructurefactexportandfullretrieval .Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-49) Store structured facts as JSON server side
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-49 Store structured facts as JSON server side Change By: Kenneth Barber Currentlywereceivealreadyflattenedstructuredfacts.Thisstepistochangetheterminusandcreateanewversionofthereplacefactscommandtoallowforreceptionofstructurefactsoverthewire.Fornowwe'lljustflattenforthestorageside,asthisisanincrementalsteptofullsupport. Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-708) Storage for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-708 Storage for structured facts Change By: Kenneth Barber Nowthatthecommandsprotocolsupportsreceivingstructuredfacts,weshouldbeabletostoretheminaformatthatisqueryableasdefinedinourdesign. Thisisawaitingontheresearchworkforthedifferentstoragetypeoptionsfirst. Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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 Thenewstructuredfactsschemaisfairlynormalized,soitmaysuffersomedanglingreferenceswhenthefactdatagetsreplaced/updated.Thistaskistotrackthecleanuptaskworkrequired. ThenormalGCroutinesalreadyhavemanyexamplesofthis. Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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) Additional query support for structured facts - Globbing/Regexp support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-746 Additional query support for structured facts - Globbing/Regexp support Change By: Kenneth Barber Thistickettrackstheworkrequiredtoaddregexp/globbingsupportforthenewstructuredfactswork,involvingpath/valuematching(insteadofname/valuematchingasbefore). Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-726) PuppetDB 2.1.0 Release - July 8th, 2014
Title: Message Title Kenneth Barber commented on an issue Re: PuppetDB 2.1.0 Release - July 8th, 2014 Heads up for the next release of PuppetDB 2.1.0, currently scheduled for July 8th. Ping Melissa Stone, Meg Hartley, Nicholas Fagerlund, Moses Mendoza, Kenn Hussey, Deepak Giridharagopal, Ryan Senior, Aliza Earnshaw, Nick Lewis. Feel free to follow/watch this ticket for any changes etc. Add Comment PuppetDB / PDB-726 PuppetDB 2.1.0 Release - July 8th, 2014 See https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process 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-726) PuppetDB 2.1.0 Release - July 8th, 2014
Title: Message Title Kenneth Barber assigned an issue to Unassigned PuppetDB / PDB-726 PuppetDB 2.1.0 Release - July 8th, 2014 Change By: Kenneth Barber Assignee: KennethBarber 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-748) Update dujour for PuppetDB 2.1.0
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-748 Update dujour for PuppetDB 2.1.0 Issue Type: Sub-task Assignee: Unassigned Created: 02/Jul/14 6:22 AM Fix Versions: 2.1.0 Priority: Normal Reporter: Kenneth Barber We'll need to update Dujour once PuppetDB 2.1.0 has been published. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-743) Report submission fails on JSON::ParserError
Title: Message Title Kurt Wall commented on an issue Re: Report submission fails on JSON::ParserError Then we need another approach to capture this, which I've proposed in the linked ticket. Kenneth Barber when enabled the additional logging, we did not get this failure. That is, it masked it or modified the timing such that it didn't occur. Add Comment PuppetDB / PDB-743 Report submission fails on JSON::ParserError We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... 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 (PDB-49) Change terminus to send unflattened structured facts
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-49 Change terminus to send unflattened structured facts Change By: Ryan Senior Summary: Store Changeterminustosendunflattened structuredfacts asJSONserverside 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-206) When a query contains a comparison between a string and a boolean, an Internal Server Error response is returned
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-206 When a query contains a comparison between a string and a boolean, an Internal Server Error response is returned Change By: Ryan Senior 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 (PUP-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2315 function call error message about mis-matched arguments is hard to understand Change By: Henrik Lindberg Summary: functioncall errormessage whengivinglambdawhennotaccepted aboutmis-matchedarguments ishardtounderstand 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-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2315 function call error message about mis-matched arguments is hard to understand Change By: Henrik Lindberg Fix Version/s: 4.x Fix Version/s: 4.0.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-1137) Maintenance task for the filebucket
Title: Message Title
Patrik Bt commented on an issue
Re: Maintenance task for the filebucket
tidy { '/var/lib/puppet/clientbucket':
age = '5w',
recurse = true,
rmdirs = true,
backup = false,
}
might be a better solution maybe?
Add Comment
Puppet / PUP-1137
Maintenance task for the filebucket
As per: * https://groups.google.com/forum/#!topic/puppet-users/GjTxlD7VRww/discussion * https://ask.puppetlabs.com/question/132/does-filebucket-need-periodic-maintenance-cleaning/ Sometimes it's useful to clean the clientbucket on a Puppet master as it can grow over time and after a while becomes useless. It would be nice if there's a rake task...
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
Jira (PUP-1137) Maintenance task for the filebucket
Title: Message Title Paul Ttterman commented on an issue Re: Maintenance task for the filebucket Sure, I was just going for the general idea. Add Comment Puppet / PUP-1137 Maintenance task for the filebucket As per: * https://groups.google.com/forum/#!topic/puppet-users/GjTxlD7VRww/discussion * https://ask.puppetlabs.com/question/132/does-filebucket-need-periodic-maintenance-cleaning/ Sometimes it's useful to clean the clientbucket on a Puppet master as it can grow over time and after a while becomes useless. It would be nice if there's a rake task... 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-743) Report submission fails on JSON::ParserError
Title: Message Title Kenneth Barber commented on an issue Re: Report submission fails on JSON::ParserError How interesting, maybe its a race of some kind then. Anyway, I'll bring up this problem in planning today. Add Comment PuppetDB / PDB-743 Report submission fails on JSON::ParserError We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... 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
Client = puppet-3.4.3-1.el6.noarch Master = puppet-3.6.2-1.el6.noarch Is there a resolution to this yet?
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
After 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
Jira (PDB-749) Add validation to the query engine
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-749 Add validation to the query engine Issue Type: New Feature Assignee: Unassigned Created: 02/Jul/14 7:51 AM Priority: Normal Reporter: Ryan Senior Currently we only validate a few possible problems related to the syntax of a user's query. We check that = has three arguments, but we don't do the same for regex. We don't check that the type of the column matches the query value it should match. What is in the query engine now is what was needed to match the existing validations, which were different for each endpoint. This ticket covers thorough validation of all query engine queries. It should: Validate our join syntax sugar Check db data types with query arguments Check the number of arguments for all operators Ensure the query fields map to real columns (this exists already)
Jira (PDB-750) Add automatic aliasing to the query engine
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-750 Add automatic aliasing to the query engine Issue Type: New Feature Assignee: Unassigned Created: 02/Jul/14 7:54 AM Priority: Normal Reporter: Ryan Senior Currently the alias for a particular query snippit is hard coded into the context. This should be auto-generated so shat we can always piece together any two queries and add any subqueries without column name collisions. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2315 function call error message about mis-matched arguments is hard to understand Change By: Henrik Lindberg Story Points: 1 5 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-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2315
function call error message about mis-matched arguments is hard to understand
Change By:
Henrik Lindberg
ThenewfunctionAPIchecksthetypesofgivenargumentsandgivesanerror.Thiserrorishardtounderstand inseveralsituations:* whenalambdaisgivenwherenoneisacceptedsinceitonlyreportsthegivenCallabletypeasifitwasaregularparameter.Itshouldcallitoutexplicitly(sinceaCallableisanObject,itlooksliketheerrorisnotlegit). Callingthe {{ assert_type }} functionwithalambdashowsthebaderrormessage. *Whenalambdaisexpected,butdoesnotmatch*Errorspewsoutalldetailsaboutthetypes(anarraywiththousandsofentriesisdisplayed)WeshouldimplementanExplainingTypeCalculatorthat:*explainswhyamatchfailed*isgiventhenamesoftheinputobjects*producesamessagewithareferencerootedatthegivennamethatshowswheretheerrorwasfound(e.g.{{$x\[key\]\[3\]-expectedX,gotY}})*reducesthedetailedtypeinformationindependenttypes(e.g.Tuple,Array,Hash,Enum)suchthatrepeatedsequencesarecompacted(asequenceof100Integersmaybedisplayedas{{Integer\{100\}}}Anerrormessagenow,maylooklikethis:{code}ErrorwhileevaluatingaMethodcall,function'each'calledwithmis-matchedargumentsexpectedoneof:each(Hash[Any,Any]hash,Callable[2,2]block)-argcount{2}each(Hash[Any,Any]hash,Callable[1,1]block)-argcount{2}each(Anyenumerable,Callable[2,2]block)-argcount{2}each(Anyenumerable,Callable[1,1]block)-argcount{2}actual:each(Tuple[Integer,Integer,Integer,Integer,Integer,Integer,Integer],Callable[Any,Any,Any])-argcount{2}atline1:29onnodefoonode{code}Ittakesawhiletofigureoutthattheerroristhatthegivenblocktotheeachfunctionhadthreeparameterswhere1or2wereexpected.Ifeachexpectedresultshowsthereasonforrejectionareshownitwoulddisplaysomethinglike:{code}ErrorwhileevaluatingaMethodcall,function'each'calledwithmis-matchedargumentsexpectedoneof:each(Hash[Any,Any]hash,Callable[2,2]block)-argcount{2}rejected:$block[parameter_count]is3where2wasexpectedeach(Hash[Any,Any]hash,Callable[1,1]block)-argcount{2}rejected:$block[parameter_count]is3where1wasexpectedeach(Anyenumerable,Callable[2,2]block)-argcount{2}rejected:$block[parameter_count]is3where2wasexpectedeach(Anyenumerable,Callable[1,1]block)-argcount{2}rejected:$block[parameter_count]is3where1wasexpectedactual:each(Tuple[Integer,Integer,Integer,Integer,Integer,Integer,Integer],Callable[Any,Any,Any])-argcount{2}atline1:29onnodefoonode{code}Or,itmaybeclearerifitdoesthis:{code}ErrorwhileevaluatingaMethodcall,function'each'calledwithmis-matchedargumentsexpectedoneof:1.each(Hash[Any,Any]hash,Callable[2,2]block)-argcount{2}2.each(Hash[Any,Any]hash,Callable[1,1]block)-argcount{2}3.each(Anyenumerable,Callable[2,2]block)-argcount{2}4.each(Anyenumerable,Callable[1,1]block)-argcount{2}actual:each(Tuple[Integer,Integer,Integer,Integer,Integer,Integer,Integer],Callable[Any,Any,Any])-argcount{2}atline1:29onnodefoonoderejectedbecause:1.$block[parameter_count]is3where2wasexpected2.$block[parameter_count]is3where1wasexpected3.$block[parameter_count]is3where2wasexpected4.$block[parameter_count]is3where1wasexpected{code}Andifweareabletodetectapattern(allcausedbycountbeing3),wecouldpointthatoutandattheendshow:{code}rejectedbecause:$block[parameter_count]is3...andpossiblythedetails1-n{code}Naturally,ifthereisonlyonesignature,thenumberingshouldbeskipped.
Jira (PDB-190) Reports: ability to query by hash
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-190 Reports: ability to query by hash Change By: Ryan Senior Story Points: 2 1 Labels: redmine trivial 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-190) Reports: ability to query by hash
Title: Message Title Ryan Senior commented on an issue Re: Reports: ability to query by hash Note that querying for reports by hash is supported by the new query engine (v4 API with PuppetDB 2.1.0+). Leaving this ticket open for the convenience path mentioned in the description, this should be a pretty small change since we already support querying on that field. Add Comment PuppetDB / PDB-190 Reports: ability to query by hash Knowing the reports hash it should be possible to query for /reports/hash and get a single report back. The current solution would be to get all reports for a node, iterate over them and search for the hash. 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-488) Change wire formats to include timestamp from producer side
Title: Message Title Heidi Pio updated an issue PuppetDB / PDB-488 Change wire formats to include timestamp from producer side Change By: Heidi Pio Sprint: 20140618to20140702 ,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-675) init.d script silently fails if PIDfile is missing
Title: Message Title Heidi Pio updated an issue PuppetDB / PDB-675 init.d script silently fails if PIDfile is missing Change By: Heidi Pio Sprint: 20140521to20140604,20140604to20140618,20140618to20140702 ,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-716) HTTP API gets stuck
Title: Message Title Heidi Pio updated an issue PuppetDB / PDB-716 HTTP API gets stuck Change By: Heidi Pio Sprint: 20140702to 20140716 to20140730 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-743) Report submission fails on JSON::ParserError
Title: Message Title Heidi Pio updated an issue PuppetDB / PDB-743 Report submission fails on JSON::ParserError Change By: Heidi Pio 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 (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
Richard Clark updated an issue
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
Change By:
Richard Clark
After gtAfter upgradefrom3.3.2-1to3.4.2-1naginatorfailstocreateconfigfromexportedresources,datatakenfromhiera.Whenhierahasthefollowingdata:check_apt_security:{check_command:check_nrpe_1arg!check_apt_security,contact_groups:sladmins,normal_check_interval:10,retry_check_interval:30,max_check_attempts:3,notification_interval:1440,notifications_enabled:1}Error:/Stage[main]/Nagios::Base/Nagios_service[]:Couldnotevaluate:privatemethod`sub'calledfor1:FixnumWhichclearlyindicatesthatvariableisnotastring.WhenIquoteintegersinthehierajsonfileeverythingworksfine,notsureifthisishieraorpuppetnaginatorproblem.
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 Heidi Pio updated an issue PuppetDB / PDB-121 Add Ruby 2.0 to spec test matrix for puppetdb Change By: Heidi Pio Sprint: 20140702to 20140716 to20140730 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-711) Factset endpoint for simplifying structure fact export and full retrieval
Title: Message Title Heidi Pio updated an issue PuppetDB / PDB-711 Factset endpoint for simplifying structure fact export and full retrieval Change By: Heidi Pio Sprint: 20140730 20140702 to 20140813 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 (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Matthew Pounsett commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
This is a fairly simple bug with a simple fix, and could be fixed pretty quickly. I'd caution against dragging other issues into this. FACT-345 has been re-opened as it is similar but unrelated.
Add Comment
Facter / FACT-605
facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Facter will use RFC 4193 addresses when creating the ipaddress6 fact, but ignores them when it tries to create interface-specific ipaddress6_$\{interface\} facts. It looks like in the latter case it is treating them the same as link-local addresses. Since these are usable, routable addresses within a LAN, they should be treated the same as any globall...
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 (FACT-609) automatic puppet run ignores facter environment variable
Title: Message Title Bjoern created an issue Facter / FACT-609 automatic puppet run ignores facter environment variable Issue Type: Bug Affects Versions: 2.1.0 Assignee: Eric Sorenson Created: 02/Jul/14 8:36 AM Environment: CentOS, Ubuntu Priority: Normal Reporter: Bjoern In /etc/profile I defined a facter variable like this: export FACTER_MAINUSER=userXY When I execute puppet agent -t it's working fine and my module user $::mainuser with success. Unfortunately the automatic puppet run triggered by daemon perform my module with a empty $::mainuser. May it's the wrong way to set a global facter variable, but I guess /etc/profile should be global enough, isn't it? Add Comment
Jira (PDB-747) Produce work-able schema for structured facts
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-747 Produce work-able schema for structured facts Change By: Ryan Senior Assignee: KennethBarber 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-720) Port already in use with cli/services.clj test
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-720 Port already in use with cli/services.clj test Change By: Ryan Senior Assignee: RyanSenior 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-2877) When using square opening and closing brackets in title = puppet error
Title: Message Title
Jrme Dubois created an issue
Puppet / PUP-2877
When using square opening and closing brackets in title = puppet error
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
02/Jul/14 8:49 AM
Environment:
Centos 6.5
Priority:
Normal
Reporter:
Jrme Dubois
When using the following to define a title for a custom type: mycluster[01-02], I get the below error Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type custom_class at /etc/puppet/manifests/site.pp:14 on node mypuppetnode.xx
I simplified the use case as originally I was reading from hiera files, then calling create_resources and got a misleading ...Invalid resource type my_custom_type... encountered when calling create_resources. Indeed, when using mycluster[01-02] as a key/identifier for a hash in YAML I am guessing this is used as the title/name to instantiate the custom type.
Below code reproduces on my side: class custom_class { }
define custom_type { } #below line works but would not if closing square bracket custom_type {'mycluster[1-2':}
#below line produces an error custom_class {'mycluster[1-2]':}
Jira (PDB-190) Reports: ability to query by hash using a convenience URL like /reports/hash
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-190 Reports: ability to query by hash using a convenience URL like /reports/hash Change By: Kenneth Barber Summary: Reports:abilitytoquerybyhash usingaconvenienceURLlike/reports/hash 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-2876) Better error messaging for un-accessible puppet.conf
Title: Message Title Aaron Armstrong updated an issue Puppet / PUP-2876 Better error messaging for un-accessible puppet.conf Change By: Aaron Armstrong Assignee: AaronArmstrong 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-726) PuppetDB 2.1.0 Release - July 8th, 2014
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-726 PuppetDB 2.1.0 Release - July 8th, 2014 Change By: Kenneth Barber Assignee: KennethBarber 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-2872) Problem with variable in array for template
Title: Message Title
Henrik Lindberg commented on an issue
Re: Problem with variable in array for template
Any difference if you use:
$echo = inline_template(%= @conf %)
Which is the way the variables should be referenced.
Add Comment
Puppet / PUP-2872
Problem with variable in array for template
I have the following parameters in my class manifest : {code} $datadir = '/home/test', $confarray = [datadir = ${datadir},log-file = /var/log/${fqdn}], {code} And the following in my conf template : {code} %- @confarray.each do |conf| -% %= conf % %- end -% {code} The output on my conf file is : {code} datadir = log-file = /var/log...
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
Jira (PUP-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title
Melissa Stone created an issue
Puppet / PUP-2878
puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Issue Type:
Bug
Assignee:
Unassigned
Created:
02/Jul/14 10:18 AM
Priority:
Normal
Reporter:
Melissa Stone
{{
apt-get install puppet facter puppet-common ruby-rgen Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: hiera libjson-ruby ruby-json virt-what Suggested packages: puppet-el vim-puppet ruby-selinux libselinux-ruby1.8 librrd-ruby1.9.1 librrd-ruby1.8 The following NEW packages will be installed hiera libjson-ruby ruby-json ruby-rgen virt-what The following packages will be upgraded: facter puppet puppet-common 3 to upgrade, 5 to newly install, 0 to remove and 3 not to upgrade. Need to get 1,583 kB of archives. After this operation, 2,330 kB of additional disk space will be used. Do you want to continue [Y/n]? (Reading database ... 97569 files and directories currently installed.) Preparing to replace puppet-common 2.7.26-1puppetlabs1 (using .../puppet-common_3.6.2-1puppetlabs1_all.deb) ... Unpacking replacement puppet-common ... dpkg: error processing /var/cache/apt/archives/puppet-common_3.6.2-1puppetlabs1_all.deb (--unpack): trying to overwrite '/usr/share/man/man8/puppet-kick.8.gz', which is also in package puppet 2.7.26-1puppetlabs1 No apport report written because MaxReports has already been reached dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to replace puppet 2.7.26-1puppetlabs1 (using .../puppet_3.6.2-1puppetlabs1_all.deb) ...
Stopping puppet agent [ OK ] Unpacking replacement puppet ... Selecting previously unselected package
Jira (PUP-2879) `puppet resource service` not working for `cryptdisks-udev`
Title: Message Title Danny Arnold created an issue Puppet / PUP-2879 `puppet resource service` not working for `cryptdisks-udev` Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Client Created: 02/Jul/14 10:43 AM Environment: Ubuntu Trusty Tahr - Azure Virtual Machine Priority: Normal Reporter: Danny Arnold Issuing puppet resource service cryptdisks-udev outputs Error: Could not run: Execution of '/sbin/status cryptdisks-udev' returned 1: status: Unknown parameter: DEVNAME Since puppet stops there puppet resource service won't work as well.
Jira (PUP-1882) defaultfor method for providers should be allowed to be specified multiple times
Title: Message Title Simon Crute commented on an issue Re: defaultfor method for providers should be allowed to be specified multiple times I think this has become critical, for me at any rate. The service provider for suse systems is defaulting to redhat. However, on opensuse 13.1 this is now generating a failure if the service does not exist. That doesn't happen if the systemd provider is used. Add Comment Puppet / PUP-1882 defaultfor method for providers should be allowed to be specified multiple times You should be able to specify multiple defaultfor statements in providers: pre defaultfor :operatingsystem = :redhat, :lsbdistrelease = [2.1, 3, 4] defaultfor :operatingsystem = :oel, :operatingsystemrelease = [4, 5] /pre 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,
Jira (PUP-2880) Unable to start agent on Ubuntu Trusty Tahr
Title: Message Title
Danny Arnold created an issue
Puppet / PUP-2880
Unable to start agent on Ubuntu Trusty Tahr
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Client
Created:
02/Jul/14 10:51 AM
Environment:
Ubuntu Trusty Tahr - Azure Virtual Machine
Priority:
Normal
Reporter:
Danny Arnold
Issuing puppet resource service puppet ensure=running enable=true (taken from http://docs.puppetlabs.com/guides/install_puppet/post_install.html#starting-the-service[here]) outputs:
Notice: /Service[puppet]/ensure: ensure changed 'stopped' to 'running'
service { 'puppet':
ensure = 'stopped',
enable = 'true',
}
Trying to apply it via manifests from a master by running puppet agent -t outputs:
Notice:
Jira (FACT-231) PR (608): Fix to Virtual Machine detection on Darwin - keeleysam
Title: Message Title Tim Sutton commented on an issue Re: PR (608): Fix to Virtual Machine detection on Darwin - keeleysam For VMware Fusion, searching VMware in machine_model won't always suffice. VMware Fusion supports at least two additional hardware settings in VMX that can spoof a real hardware model like MacBookPro10,2. Setting either hw.model to the desired string or hw.model.reflectHost to TRUE will give a machine_model that's not like VMware7,1. It's probably mostly a corner case, but sometimes one needs to spoof the model name in order to test any conditional logic that would use hardware identifier value, or for applications/installer logic that might depend on this value. For example, the same facter output on my Mountain Lion Fusion VM that has guest tools installed and an explicitly-set hw.model in its VMX: $ facter | egrep -i vm|virt fqdn = test-vm-ml.domain.my hostname = test-vm-ml is_virtual = false sp_boot_rom_version = VMW71.00V.0.B64.1310020058 sp_local_host_name = test-vm-ml sp_secure_vm = secure_vm_enabled sp_serial_number = VMWVk0+Ybd6rKeIJ4kU0VBcjg virtual = physical One possible approach might be to scan the boot_rom_version similar to how the Parallels check works, in virtual.rb: require 'facter/util/macosx' result = physical # use SPHardwareDataType for VMware and VirtualBox, since it is the most # reliable source. output = Facter::Util::Macosx.profiler_data(SPHardwareDataType) if output.is_a?(Hash) result = vmware if output[boot_rom_version] =~ /VMW/ result = virtualbox if output[boot_rom_version] =~ /VirtualBox/ end The Boot ROM Version on my VM here is VMW71.00V.0.B64.1310020058 Add Comment Facter / FACT-231 PR (608): Fix to Virtual Machine detection on Darwin
Jira (PDB-728) Update changelog/release notes
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-728 Update changelog/release notes Change By: Ryan Senior Assignee: RyanSenior 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-2880) Unable to start agent on Ubuntu Trusty Tahr
Title: Message Title
Danny Arnold commented on an issue
Re: Unable to start agent on Ubuntu Trusty Tahr
Found out that /etc/default/puppet must be change as said here
That should probably be mentioned in the docs.
Add Comment
Puppet / PUP-2880
Unable to start agent on Ubuntu Trusty Tahr
Issuing {{puppet resource service puppet ensure=running enable=true}} (taken from [http://docs.puppetlabs.com/guides/install_puppet/post_install.html#starting-the-service][here]) outputs: {noformat} Notice: /Service[puppet]/ensure: ensure changed 'stopped' to 'running' service { 'puppet': ensure = 'stopped', enable = 'true', } {noformat} Tr...
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-2880) Unable to start agent on Ubuntu Trusty Tahr
Title: Message Title
Danny Arnold updated an issue
Puppet / PUP-2880
Unable to start agent on Ubuntu Trusty Tahr
Change By:
Danny Arnold
Issuing{{puppetresourceservicepuppetensure=runningenable=true}}(takenfrom[ here| http://docs.puppetlabs.com/guides/install_puppet/post_install.html#starting-the-service] [here] )outputs:{noformat}Notice:/Service[puppet]/ensure:ensurechanged'stopped'to'running'service{'puppet':ensure='stopped',enable='true',}{noformat}Tryingtoapplyitviamanifestsfromamasterbyrunning{{puppetagent-t}}outputs:{noformat}Notice:/Stage[main]/All/Service[puppet]/ensure:ensurechanged'stopped'to'running'Info:/Stage[main]/All/Service[puppet]:UnschedulingrefreshonService[puppet]{noformat}Running{{puppetagent}}seemstostarttheagent,buthaven'ttriedwhetheritsurvivesarestart.
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-2429) Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
Title: Message Title Peter Huene commented on an issue Re: Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) When trusted_node_data is set, we'll error if they have a custom fact named trusted or otherwise try to assign that reserved name in their manifests. I think it should be safe to use trusted as the top level name. If you need to flatten the facts, though, by adding facts like trusted_authenticated, trusted_certname, etc. then we might have a conflict problem. I don't think there is a good solution to that problem other than detecting the conflict and renaming. Add Comment Puppet / PUP-2429 Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) PDB-565 covers the need to store trusted facts in PuppetDB, but right now I don't believe we have a suitable API contract for getting this information from Puppet. At least I can't find one, neither the facts terminus nor the catalog terminus supplies this for example. One solution to this is to include the set of trusted facts in the request object su... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because
Jira (PUP-2429) Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
Title: Message Title Peter Huene commented on an issue Re: Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) Kenneth Barber I'm going to resolve this ticket for now. Please reactivate if there is something we can do in core to facilitate this feature in PuppetDB. Thanks! Add Comment Puppet / PUP-2429 Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) PDB-565 covers the need to store trusted facts in PuppetDB, but right now I don't believe we have a suitable API contract for getting this information from Puppet. At least I can't find one, neither the facts terminus nor the catalog terminus supplies this for example. One solution to this is to include the set of trusted facts in the request object su... 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-777) Start deprecating 'versionRequirement' per code comment
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-777 Start deprecating 'versionRequirement' per code comment Change By: Alex Dreyer Fix Version/s: 4.x Fix Version/s: 3.7.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 (FACT-606) Remove sid/unstable from build_defaults
Title: Message Title William Hopper commented on an issue Re: Remove sid/unstable from build_defaults Merged at https://github.com/puppetlabs/facter/commit/fe902c6cd058a04a4e02eb6793bffc8fe96ead63 Add Comment Facter / FACT-606 Remove sid/unstable from build_defaults Debian sid/unstable regularly causes failures in acceptance because someone pushes something broken to the apt repos and then we cannot build puppet, or facter, or something we build against sid. This OS target is of questionable value, given we already build against Debian testing. The fact that we also don't test this build, but still ship packages for ... 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 (HI-277) Remove sid and unstable from build_defaults
Title: Message Title William Hopper commented on an issue Re: Remove sid and unstable from build_defaults Merged at https://github.com/puppetlabs/hiera/commit/f228258b00e22ca9257712a9ee5d913368d11567 Add Comment Hiera / HI-277 Remove sid and unstable from build_defaults Debian sid/unstable regularly causes failures in acceptance because someone pushes something broken to the apt repos and then we cannot build puppet, or facter, or something we build against sid. This OS target is of questionable value, given we already build against Debian testing. 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-392) Validate win32 gems on x86 and x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate win32 gems on x86 and x64
I propose that we move win32-taskscheduler over to its own issue since it now falls out of the scope of no known issues.
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
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-392) Validate win32 gems on x86 and x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate win32 gems on x86 and x64
Win32-dir PR#10 resulted in win32-dir v0.4.9, so that one is good.
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
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-392) Validate win32 gems on x86 and x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate win32 gems on x86 and x64
With that, it means the following items are ready to move forward with merge:
https://github.com/puppetlabs/puppet/pull/2830
https://github.com/puppetlabs/puppet-win32-ruby/pull/39
https://github.com/puppetlabs/puppet-win32-ruby/pull/40
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2429) Provide a way to expose trusted facts to PuppetDB (and other terminus consumers)
Title: Message Title Kenneth Barber commented on an issue Re: Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) Peter Huene well this is great, so I can tell you right now trusted facts will not be flattened on our side, we're going to be able to store hashes arrays etc. So having 'trusted' reserved is totally sweet and is going to make this almost hassle free on our end. Thanks very much Peter, I guess we can close this now? Add Comment Puppet / PUP-2429 Provide a way to expose trusted facts to PuppetDB (and other terminus consumers) PDB-565 covers the need to store trusted facts in PuppetDB, but right now I don't believe we have a suitable API contract for getting this information from Puppet. At least I can't find one, neither the facts terminus nor the catalog terminus supplies this for example. One solution to this is to include the set of trusted facts in the request object su... 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-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 Story Points: 8 3 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-675) init.d script silently fails if PIDfile is missing
Title: Message Title
Kenneth Barber commented on an issue
Re: init.d script silently fails if PIDfile is missing
I've sent this out to the mailing list:
https://groups.google.com/forum/#!topic/puppet-users/yEcZ7u2qTxs
To see if anyone is still suffering and perhaps able to reproduce this, and if they can help us debug it.
Add Comment
PuppetDB / PDB-675
init.d script silently fails if PIDfile is missing
Debugging log: init.d restart fails but silently exits 0. Missing pidfile but still running application -- killing application fixes issue. {code}# sh -x /etc/init.d/puppetdb stop + [ -r /etc/default/puppetdb ] + . /etc/default/ + [ -f /usr/lib/jvm/java-7-openjdk-amd64/bin/java ] + JAVA_BIN=/usr/lib/jvm/java-7-openjdk-amd64/bin/java + JAVA_ARGS=-X...
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
Jira (PDB-747) Produce work-able schema for structured facts
Title: Message Title Kenneth Barber commented on an issue Re: Produce work-able schema for structured facts Branch for initial work is here: https://github.com/kbarber/puppetdb/tree/ticket/master/pdb-747 Add Comment PuppetDB / PDB-747 Produce work-able schema for structured facts This task tracks the work to create a schema for structured facts. If we break out the work amongst multiple people, this ticket will require possibly some sort of migration of SQL script as an output so others can use it. We already have a start on the schema in the design doc: https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes... 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-747) Produce work-able schema for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-747 Produce work-able schema for structured facts Change By: Kenneth Barber Attachment: ScreenShot2014-07-02at21.04.40.png 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: 20140730 20140716 to 20140813 20140730 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) Additional query support for structured facts - Globbing/Regexp support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-746 Additional query support for structured facts - Globbing/Regexp support Change By: Kenneth Barber Sprint: 20140730 20140716 to 20140813 20140730 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-2866) Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum.
Title: Message Title Adrien Thebo commented on an issue Re: Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. Merged in bb7ec34. Add Comment Puppet / PUP-2866 Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. 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-713) Modify anonymization tool to support structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-713 Modify anonymization tool to support structured facts Change By: Kenneth Barber Sprint: 20140813 20140730 to 20140827 20140813 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.
