Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Josh Cooper commented on PUP- Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Puppet will require (in the ruby sense) providers on the master to determine the default provider for a type. Any code that is outside of a class or instance method, will be executed on the master. For example, lib/puppet/provider/host/parsed.rb invokes Facter as soon as the file is required: case Facter.value(:osfamily) when Solaris; hosts = /etc/inet/hosts I believe any confining of providers will also be evaluated to determine suitability (during compilation). Also, this is why windows providers are guarded by the Puppet.features.microsoft_windows? feature flag, because we don't want to try to require windows gems on the master. So I think we'll find that there are many cases where Facter is executed on the master in both core puppet code and custom type providers. Fortunately, the API is relatively small as we're just looking up fact values. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Peter Huene commented on PUP- Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Yeah, I don't think removing Facter interactions on the master is the answer. I'm looking into building an optional JNI interface into libfacter that we can make use of from JRuby. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional Would it not be better to let the ENC make a decision if it is given the environment from the agent (if specified)? How high should we otherwise built the tower of decision makers? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg assigned an issue to Christopher Barbour Puppet / PUP-4459 Authoritative ENC Environments should be optional Change By: Henrik Lindberg Assignee: HenrikLindberg ChristopherBarbour Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-348) Facter should provide a convenient way to cache values
Title: Message Title Steve Traylen commented on FACT-348 Re: Facter should provide a convenient way to cache values This would be useful. For instance the ec2 facts which poll our nova master quite a bit. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Henrik Lindberg commented on PUP-2630 Re: Server-set global variables like $::environment get overwritten by client facts After discussion with Eric Soerenson, we decided that it was best to make this an opt-in and that we are not adding a function - this for the sake of consistency between $facts, $trusted_facts, and $server_facts. This means: At the same place where we currently set $trusted_facts we should also set $server_facts if users have opted in The values set in $server_facts are the @server_facts set in the node by the compiler indirection + the current environment name The user opts in by using the setting :trusted_server_facts The setting is false by default We issue a warning if any node parameter is overwritten We need a ticket to add a deprecation for the opt-in being set to false We need a ticket for 5.0.0 to remove the opt in and make $server_facts default, and to stop merging the server_facts into the node's parameters Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1452) PR (1363): (re-4451) Updates for pe-puppetdb - shrug
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1452 PR (1363): (re-4451) Updates for pe-puppetdb - shrug Change By: Kenneth Barber Sprint: PuppetDB2015-05-06 Story Points: 0 Scope Change Reason: PRraisedbyreleaseteam Scope Change Category: Adopted Fix Version/s: PDB3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and
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: PUP4.1.0 Fix Version/s: PUP4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4458) Refactor validation of 4.x parameter signatures
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4458 Refactor validation of 4.x parameter signatures Change By: Henrik Lindberg Fix Version/s: PUP4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-3596) Ensure Language Specification specifies behavior of undef resource param
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3596 Ensure Language Specification specifies behavior of undef resource param Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1448 'replace facts' failing due to foreign key constraint issue Change By: Wyatt Alt Sprint: PuppetDB2015-05-06 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt assigned an issue to Rob Browning PuppetDB / PDB-1448 'replace facts' failing due to foreign key constraint issue Change By: Wyatt Alt Assignee: WyattAlt RobBrowning Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4388) Remove /etc/default/puppet on Debian
Title: Message Title Josh Cooper assigned an issue to QA Puppet / PUP-4388 Remove /etc/default/puppet on Debian Change By: Josh Cooper Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4359) puppetversion fact is missing
Title: Message Title Josh Cooper assigned an issue to QA Puppet / PUP-4359 puppetversion fact is missing Change By: Josh Cooper Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4459) Authoritative ENC Environments should be optional
Title: Message Title Christopher Barbour commented on PUP-4459 Re: Authoritative ENC Environments should be optional Agreed, that is the ideal solution. Whether or not a node is allowed to override the ENC defined environment should probably be a property of the node, and managing node properties is the domain of the node classifier. The benefits of your approach is that we could use the PE rules classifier to define which group of nodes may override their environment. E.g. allow development nodes to change environment, but not production nodes. Or if supporting multiple tenants, we could control the setting on a per client basis. This would also open the possibility of building an 'approved environment list' feature into the ENC. My only reservation of including this feature in the ENC is that we'd have to wait for the various classifiers to supply the appropriate setting. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title gepetto-bot commented on PDB-1456 Re: PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker ajroetker commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4462) Backslash before $ handled wrongly in heredoc with no escapes enabled
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-4462
Backslash before $ handled wrongly in heredoc with no escapes enabled
Change By:
Nicholas Fagerlund
Ran:{code} $thing=hithere notice(@(ENDINTERP))Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:${thing}Variableenjambed:hey${thing}Variablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\${thing}ENDINTERP{code}Thesinglebackslashbeforethe$causesaproblem.I'mprettysurethisisagainst[thespecificationofheredocs|https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md].Actualresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\hithere{code}Expectedresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\hithereVariablewithdoublebackslashenjambed:\\hithere{code}3.7.5and4.0.0behaveidentically.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you 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-4462) Backslash before $ handled wrongly in heredoc with no escapes enabled
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4462 Backslash before $ handled wrongly in heredoc with no escapes enabled Issue Type: Bug Affects Versions: PUP 4.0.0, PUP 3.7.5 Assignee: Henrik Lindberg Components: Language Created: 2015/04/24 3:40 PM Priority: Normal Reporter: Nicholas Fagerlund Ran: notice(@(END INTERP)) This string should be able to interpolate variables, and all backslashes should
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Henrik Lindberg Scrum Team: Language Fix Version/s: PUP4.1.0 Fix Version/s: PUP3.8.1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional So, you could add your own ENC implementation that calls the PE ENC, and returns the results. Your proxy ENC has the features you want, if a certain parameter is set it allows the node to use the environment it specifies, otherwise what the ENC said. I hope there is no limit on what kinds of parameters you can set - just invent one that is meaningful and unique that the ENC proxy with your wanted feature looks at (and does not pass on). You can do that on your own while waiting for the PE ENC to have the same / similar features. I don't think puppet itself should have yet another classifier layer. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title
Peter Huene commented on PUP-
Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
$ jirb
2.0.0-p598 :001 com.puppetlabs.Facter.getFact('os')
{
architecture = x86_64,
family = Darwin,
hardware = x86_64,
macosx = {
build = 14D136,
product = Mac OS X,
version = {
full = 10.10.3,
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Henrik Lindberg Sprint: Language2015-04-29 Story Points: 1 Scope Change Reason: bugthatisgoingtobemorepainfulthelongerwewaitfixing Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to 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-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title gepetto-bot commented on PDB-1456 Re: PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker mullr commented: How does it compare to the pre-patch perf? On Fri, Apr 24, 2015 at 3:12 PM, Andrew Roetker notificati...@github.com wrote: @mullr https://github.com/mullr Preformed the factchurn.sh test on this a few times and it looks like the minimum gap I could get between the hash query and the GC query was about 2x, ie the hash query is still 2x slower than the GC on average. — Reply to this email directly or view it on GitHub https://github.com/puppetlabs/puppetdb/pull/1366#issuecomment-96080726. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4462) Single backslash makes $ disappear in heredoc with no escapes enabled
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4462 Single backslash makes $ disappear in heredoc with no escapes enabled Change By: Nicholas Fagerlund Summary: Backslashbefore Singlebackslashmakes $ handledwrongly disappear inheredocwithnoescapesenabled Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Simon Oxwell Thanks. I've got no real leads yet but we've pulled this into our current sprint for investigation. Our best vague guess at the moment is that one or both of those facts are being updated in a way that we are not handling correctly. I've got a few questions; interested if you can shed some light. are the problematic facts on the other three hosts also structured like these two, or are there any simple name/value pairs affected? when you run the delete command you mentioned in your report, does the problem come back immediately or after some time? does the problem always reappear on the same hosts? same facts? are you seeing more nodes affected as time goes on? are there any failed commands in /var/lib/puppetdb/mq/discarded that reflect the same constraint violation? are you running with the default puppet run interval on all your nodes? (30 minutes) for a host that's affected, could you give the output of facter -j funnelback_collections_profiles_structured facter -j funnelback_collections_structured (substituting in the relevant fact
Jira (PUP-4461) puppetserver ignores manifest changes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4461 puppetserver ignores manifest changes Change By: Henrik Lindberg Affects Version/s: PUP3.8.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1450) Make automatic expiration work with sync
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1450 Make automatic expiration work with sync Change By: Russell Mull Automatic Ourcurrentnode expiration system (ne automaticdeactivation)isproblematicwhensynchronizingPDBswitheachother,sinceit'sbasedonclockcomparison. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Nicholas Fagerlund Summary: Singlebackslash makes before $ disappear blocksinterpolation inheredocwithnoescapesenabled Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title gepetto-bot commented on PDB-1456 Re: PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1089/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4461) manifest changes are ignored when using hiera_include
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Henrik Lindberg Summary: puppetserverignores manifestchanges areignored whenusinghiera_include Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title gepetto-bot commented on PDB-1456 Re: PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker ajroetker commented: @mullr Preformed the factchurn.sh test on this a few times and it looks like the minimum gap I could get between the hash query and the GC query was about 2x, ie the hash query is still 2x slower than the GC on average. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1450) Make automatic deactivation work with sync
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1450 Make automatic deactivation work with sync Change By: Russell Mull Summary: Adddeactivatednodetimestamptowireformat Makeautomaticdeactivationworkwithsync Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1450) Make automatic deactivation work with sync
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1450 Make automatic deactivation work with sync Change By: Russell Mull Assignee: RussellMull Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Henrik Lindberg commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled Nicholas Fagerlund Yes, you found a bug. The specification says that @(END) means that interpolation is not, but not escapes. When turning on any escape, a literal backslash must always be escaped. You correctly described the expected result as per the specification. It seems that the code assumes that turning on interpolation also turns on the $ escape, and subsequently that backslash must be escaped. That is against the spirit of heredoc (to be as close to verbatim text as possible). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4461) puppetserver ignores manifest changes when using hiera_include
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4461 puppetserver ignores manifest changes when using hiera_include Change By: Henrik Lindberg Summary: puppetserverignoresmanifestchanges whenusinghiera_include Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4459) Authoritative ENC Environments should be optional
Title: Message Title Christopher Barbour assigned an issue to Henrik Lindberg Puppet / PUP-4459 Authoritative ENC Environments should be optional Change By: Christopher Barbour Assignee: ChristopherBarbour HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1450) Add deactivated node timestamp to wire format
Title: Message Title Russell Mull commented on PDB-1450 Re: Add deactivated node timestamp to wire format Here's the plan: User-deactivated nodes (via the puppet deactivate command) will continue to be called 'deactivated', for consistency. Automatically deactivated nodes will be called 'expired'. add a boolean expired column to the certnames table update existing code that checks if a node is deactivated to also check if it's expired. When processing the 'deactivate node' command for a certname that doesn't exist, create a new entry instead of ignoring it When pulling data as part of sync include deactivated and expired records in each summary query only pull over records that would not be expired locally Allow users to include deactivated and expired records in query results at least for the factsets, catalogs, reports, and nodes endpoints ...but hopefully in a generic way for all endpoints Add the 'nodes' endpoint to the sync, for pulling over deactivation status Include the node's deactivation time in the summary query
Jira (PDB-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title gepetto-bot commented on PDB-1456 Re: PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1088/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title gepetto-bot commented on PDB-1456 Re: PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1085/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1450) Make automatic expiration work with sync
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1450 Make automatic expiration work with sync Change By: Russell Mull Summary: Makeautomatic deactivation expiration workwithsync Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1450) Make automatic expiration work with sync
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1450 Make automatic expiration work with sync Change By: Russell Mull Currentlythedeactivatednodefieldisjustaboolean.Thisdoesn'tworkwellinanHA/Replicatedworld.Insteadifweincludeatimestamp Automaticexpiration ( fromthepuppetmaster),sothedatecanbereplicated. ne Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4462
Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Change By:
Henrik Lindberg
Ran:{code}$thing=hitherenotice(@(ENDINTERP))Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:${thing}Variableenjambed:hey${thing}Variablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\${thing}ENDINTERP{code}Thesinglebackslashbeforethe$causesaproblem.I'mprettysurethisisagainst[thespecificationofheredocs|https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md].Actualresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\hithere{code}Expectedresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\hithereVariablewithdoublebackslashenjambed:\\hithere{code}3.7.5and4.0.0behaveidentically. Inaddition,ifanyescape(otherthan'$'escapes)areturnedon,italsoturnsonescapingof'$'.Thisiscausedbythesamefaultylogic.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google
Jira (PDB-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title gepetto-bot commented on PDB-1456 Re: PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker ajroetker commented: @mullr I feel like I'm going crazy, it actually looks about the same (2x as long) but the query plans are definitely different... Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Henrik Lindberg commented on PUP-4374 Re: Splatting attributes into an amended attribute block isn't supported Specification updated. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1450) Add deactivated node timestamp to wire format
Title: Message Title Russell Mull commented on PDB-1450 Re: Add deactivated node timestamp to wire format Further discussion: The deactivated status DOES need to be replicated. Consider this case: X and Y have the same active node. Partition the network Y receives an update Y's TTL expires, auto-deactivating a node Heal the partition Sync, but X's TTL hasn't yet expired In this case, X should get the updated state and keep the node active, locally. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-963) Investigate usage of JSON gem in acceptance tests
Title: Message Title Justin Stoller updated an issue Facter / FACT-963 Investigate usage of JSON gem in acceptance tests Change By: Justin Stoller Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1448 'replace facts' failing due to foreign key constraint issue Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-963) Investigate usage of JSON gem in acceptance tests
Title: Message Title Justin Stoller created an issue Facter / FACT-963 Investigate usage of JSON gem in acceptance tests Issue Type: Bug Assignee: Unassigned Created: 2015/04/24 10:28 AM Priority: Normal Reporter: Justin Stoller The acceptance tests attempt to install the JSON gem everywhere for all types of installations. The tests require them and certain features for certain installation types require them. Where and when exactly is unknown. Specifically testing is blocked for AIO on Debian 8 because it does not contain the same libjson-gem that the tests try to install. Either the pre-suite needs to be updated to install the correct lib in the correct way, or if it isn't necessary to install it on the hosts for testing in AIO, the dependency should be removed from the AIO pre-suite. Add Comment
Jira (PDB-1187) Logs Metrics: (query) Provide end points for querying report logs, metrics for a specific report
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1187 Logs Metrics: (query) Provide end points for querying report logs, metrics for a specific report Change By: AJ Roetker Assignee: AJRoetker Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-3486) Update jetty_external_root_ca acceptance test to use disabled CA service
Title: Message Title Erik Dasher commented on PUP-3486 Re: Update jetty_external_root_ca acceptance test to use disabled CA service QA is the right place for this. QA needs to read both the jetty_external_root_ca test and the external ca test in the qatests repository and decide if both are needed, or if one is redundant, and document. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1391) Inconsistent behaviour of the distinct_resources request parameter
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1391 Inconsistent behaviour of the distinct_resources request parameter Change By: AJ Roetker Assignee: AJRoetker Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1452) PR (1363): (re-4451) Updates for pe-puppetdb - shrug
Title: Message Title gepetto-bot commented on PDB-1452 Re: PR (1363): (re-4451) Updates for pe-puppetdb - shrug pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1081/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1438) Attempt to upgrade to = ezbake 0.3.3
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-1438 Attempt to upgrade to = ezbake 0.3.3 Change By: Rob Browning Summary: Upgrade Attempt to upgradeto =ezbake0.3.3 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4461) puppetserver ignores manifest changes
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-4461 puppetserver ignores manifest changes Change By: Henrik Lindberg Component/s: PuppetServer Affects Version/s: SERVER2.0.0 Affects Version/s: PUP4.0.0 Key: SERVER PUP - 559 4461 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails
Jira (PUP-4461) puppetserver ignores manifest changes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4461 puppetserver ignores manifest changes Change By: Henrik Lindberg Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4461) puppetserver ignores manifest changes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4461 puppetserver ignores manifest changes Change By: Henrik Lindberg Fix Version/s: PUP4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4461) puppetserver ignores manifest changes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4461 puppetserver ignores manifest changes Change By: Henrik Lindberg Sprint: Language2015-04-29 Scrum Team: Language Story Points: 2 Scope Change Reason: Criticalissuereport-memoryleakandproducingbadinformationhiera_include Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (PDB-1455) Accommodate AIO (paths, etc.)
Title: Message Title Rob Browning created an issue PuppetDB / PDB-1455 Accommodate AIO (paths, etc.) Issue Type: Improvement Assignee: Unassigned Created: 2015/04/24 1:39 PM Priority: Normal Reporter: Rob Browning Attempting to upgrade to ezbake 0.3.3 revealed AIO issues – for example references to /usr/bin/puppetdb in acceptance/tests (which might be OK as just puppetdb). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1438) Upgrade to = ezbake 0.3.3
Title: Message Title Rob Browning commented on PDB-1438 Re: Upgrade to = ezbake 0.3.3 Initial investigation resulted in PDB-1445 – i.e. migrating to the newer ezbake will require accommodating AIO. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1456 PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/04/24 2:14 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Speed up storage.clj `hash in (?,?,?...)` queries Author: Andrew Roetker Company: Puppet Labs Github ID: ajroetker Pull Request 1366 Discussion Pull Request 1366 File Diff Pull Request Description This commit addresses an issue where the above query for both `resources` and `facts` was very slow on Postgres because we were trimming the bytea hash to a string which was causing Postgres to do a table scan. This commit fixes this
Jira (PUP-4461) puppetserver ignores manifest changes
Title: Message Title Roman Mueller commented on PUP-4461 Re: puppetserver ignores manifest changes Henrik Lindberg I had to change it to: @@puppet_system_loader = create_puppet_system_loader() (@@ not @) And yes, that solves the problem. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4435) Deprecate Puppet WEBrick and Rack servers
Title: Message Title William Hopper updated an issue Puppet / PUP-4435 Deprecate Puppet WEBrick and Rack servers Change By: William Hopper Comment: Also-shouldtherebeadocscomponentforthisticket,ordoesthisdeprecationalreadylivesomewhereinPuppet'sdocs?(Oh,andshould4.1.0bethefixversion?) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4461) puppetserver ignores manifest changes
Title: Message Title Henrik Lindberg commented on PUP-4461 Re: puppetserver ignores manifest changes Thanks Roman Mueller (yeah, doh, sorry, the rest of the code obviously refers to @@puppet_system_loader). Ok, then we know that what the cause is. Have to think about if that is the only fix we are going to make. We should change this in 3.8.1 as well. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4461) puppetserver ignores manifest changes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4461 puppetserver ignores manifest changes Change By: Henrik Lindberg Fix Version/s: PUP3.8.1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-4435) Deprecate Puppet WEBrick and Rack servers
Title: Message Title Josh Cooper commented on PUP-4435 Re: Deprecate Puppet WEBrick and Rack servers Merged in e284592 and e984e0c Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
