Jira (PDB-1241) Resource event timestamps should be normalized
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1241 Resource event timestamps should be normalized Change By: Steve Barlow Scope Change Reason: FoundwhenworkingonPDB-908 Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1240) PR (1261): Bump to latest ezbake plugin - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1240 PR (1261): Bump to latest ezbake plugin - kbarber Change By: Steve Barlow Scope Change Reason: StayinginsyncwithEZBAKEupdatethathappenedduringsprint Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4051) Master unable to reliably reload puppet.conf
Title: Message Title Henrik Lindberg commented on PUP-4051 Re: Master unable to reliably reload puppet.conf We do not recommend using webrick for production nor any long running scenarios. It is not likely we will spend any more resources on webrick as the plan is to move to Puppet Server. Closing this as a won't fix. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3296 Remove handling and mention of :before and :after for parameters Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3296 Remove handling and mention of :before and :after for parameters Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4047) consider 'non productive expression' to be warning
Title: Message Title James Sweeny commented on PUP-4047 Re: consider 'non productive _expression_' to be warning Thanks for opening this Henrik Lindberg. In my opinion, we shouldn't even warn in cases like the example above, since there's absolutely nothing functionally wrong with the code from a user's perspective. If it's a style concern, I would rather this be in a linter than squawking during every compile (similar to having variables within single quotes). That said, there are probably other examples you can think of where this kind of warning/error would actually prevent something unexpected from happening, so it might just be something we have to get more specific about. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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 commented on PUP-2315 Re: function call error message about mis-matched arguments is hard to understand First task is to create a set of examples that can be used in a UX study. It should show simple type mismatch, type mismatch with a deep structure, given lambda where none is accepted, type mismatch when invoking the lambda (simple and a deep structure). The samples should show the problems discussed in this ticket; what the error messages look like today, and what they would look like if we make the suggested improvements (different ways). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4017) Make parser an environment specific setting
Title: Message Title Henrik Lindberg commented on PUP-4017 Re: Make parser an environment specific setting merged to stable at: ffb62e4 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4017) Make parser an environment specific setting
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4017 Make parser an environment specific setting Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4017) Make parser an environment specific setting
Title: Message Title Henrik Lindberg commented on PUP-4017 Re: Make parser an environment specific setting predocs environment-v2,md document updated with the new environment setting. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) Invalid parameter provider for custom types/providers
Title: Message Title Henrik Lindberg assigned an issue to Nicholas Fagerlund Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Henrik Lindberg Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4017) Make parser an environment specific setting
Title: Message Title Henrik Lindberg commented on PUP-4017 Re: Make parser an environment specific setting merged to master: 597a446731ef4643fb8fbbb8a5e6309c3f6416ad Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4011) Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4011 Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4 Change By: Kenn Hussey Scope Change Reason: BugfromQA,wasblockingwork Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3127 LDAP - introduce LDAP-Certificat Directory Change By: Kenn Hussey Scope Change Reason: Communitypullrequestwork Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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 Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-2315 function call error message about mis-matched arguments is hard to understand Change By: Thomas Hallgren Assignee: HenrikLindberg ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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 Thomas Hallgren updated an issue Puppet / PUP-2315 function call error message about mis-matched arguments is hard to understand Change By: Thomas Hallgren Sprint: Language2015-03-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3094) Distribute separate binaries for master and ca
Title: Message Title Scott Garman updated an issue Puppet / PUP-3094 Distribute separate binaries for master and ca Change By: Scott Garman Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3094) Distribute separate binaries for master and ca
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3094 Distribute separate binaries for master and ca Change By: Kenn Hussey Scope Change Reason: Communitypullrequestwork Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3939) Update OpenBSD service provider to support new syntax of rcctl
Title: Message Title Scott Garman updated an issue Puppet / PUP-3939 Update OpenBSD service provider to support new syntax of rcctl Change By: Scott Garman Component/s: TypesandProviders Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) Invalid parameter provider for custom types/providers
Title: Message Title Eric Thompson commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Nicholas Fagerlund i think the fix makes it work the way you'd expect. If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. Previously the autoloader would load types and providers from the default environment (production) during one phase of the compilation. The fix is to ensure we autoload types and providers from the same environment that is specified. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-400) Manage hidden windows packages
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-400 Manage hidden windows packages Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title
Richard Clamp updated an issue
Puppet / PUP-4046
Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Change By:
Richard Clamp
Usinghiera_include()withpuppet-agentasofversion0.3.2.29.g49f7b1b-1.el7producesthefollowingerror.{code}[root@puppet4manifests]#/opt/puppetlabs/puppet/bin/puppetapplydefault.pp-tInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsError:EvaluationError:ErrorwhileevaluatingaFunctionCall,uninitializedconstantHiera::PuppetFunctionat/etc/puppetlabs/puppet/manifests/default.pp:17:1onnodepuppet4.vm.super-visions.comError:EvaluationError:ErrorwhileevaluatingaFunctionCall,uninitializedconstantHiera::PuppetFunctionat/etc/puppetlabs/puppet/manifests/default.pp:17:1onnodepuppet4.vm.super-visions.com{code}default.pp{code}hiera_include('classes',[]){code}hiera.yaml{code}---:backends:-yaml:hierarchy:-defaults-%{clientcert}-%{environment}-global:yaml:#datadirisemptyhere,sohierausesitsdefaults:#-/etc/puppetlabs/code/hieradataon*nix#-%CommonAppData%\PuppetLabs\hiera\varonWindows#Whenspecifyingadatadir,makesurethedirectoryexists.:datadir:/etc/puppetlabs/hieradata{code}/etc/puppetlabs/hieradataisempty,sameresultwithaglobal.yamlfiletestedandworkingonpuppet-agent-0.3.2.22.g8642ba7-1.el7(andbefore).puppet.confisemptyMoretestingshowsthefollowing:Whenaddingany/allofthefollowinglines'before'thehiera_include()inthe.ppfiletheerrorchanges.{code}$a=hiera('a','a')$b=hiera_hash('b',{})$c=hiera_array('c',[]){code} Thedifferenterror: Withthepatchfrom {code}[root@puppet4~]#puppetapply/etc/puppetlabs/puppet/manifests/default.pp-tInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsError:EvaluationError:ErrorwhileevaluatingaFunctionCall,Functionhiera_include():cannotcallfunction'include'-noloaderspecifiedat/etc/puppetlabs/puppet/manifests/default.pp:23:1onnodepuppet4.vm.super-visions.comError:EvaluationError:ErrorwhileevaluatingaFunctionCall,Functionhiera_include():cannotcallfunction'include'-noloaderspecifiedat/etc/puppetlabs/puppet/manifests/default.pp:23:1onnodepuppet4.vm.super-visions.com{code}
Add Comment
Jira (PUP-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title
Richard Clamp updated an issue
Puppet / PUP-4046
Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Change By:
Richard Clamp
Usinghiera_include()withpuppet-agentasofversion0.3.2.29.g49f7b1b-1.el7producesthefollowingerror.{code}[root@puppet4manifests]#/opt/puppetlabs/puppet/bin/puppetapplydefault.pp-tInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsError:EvaluationError:ErrorwhileevaluatingaFunctionCall,uninitializedconstantHiera::PuppetFunctionat/etc/puppetlabs/puppet/manifests/default.pp:17:1onnodepuppet4.vm.super-visions.comError:EvaluationError:ErrorwhileevaluatingaFunctionCall,uninitializedconstantHiera::PuppetFunctionat/etc/puppetlabs/puppet/manifests/default.pp:17:1onnodepuppet4.vm.super-visions.com{code}default.pp{code}hiera_include('classes',[]){code}hiera.yaml{code}---:backends:-yaml:hierarchy:-defaults-%{clientcert}-%{environment}-global:yaml:#datadirisemptyhere,sohierausesitsdefaults:#-/etc/puppetlabs/code/hieradataon*nix#-%CommonAppData%\PuppetLabs\hiera\varonWindows#Whenspecifyingadatadir,makesurethedirectoryexists.:datadir:/etc/puppetlabs/hieradata{code}/etc/puppetlabs/hieradataisempty,sameresultwithaglobal.yamlfiletestedandworkingonpuppet-agent-0.3.2.22.g8642ba7-1.el7(andbefore).puppet.confisemptyMoretestingshowsthefollowing:Whenaddingany/allofthefollowinglines'before'thehiera_include()inthe.ppfiletheerrorchanges.{code}$a=hiera('a','a')$b=hiera_hash('b',{})$c=hiera_array('c',[]){code}Withthepatchfrom https://github.com/puppetlabs/puppet/pull/3655appliedtheerrorchangesto: {code}[root@puppet4~]#puppetapply/etc/puppetlabs/puppet/manifests/default.pp-tInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsError:EvaluationError:ErrorwhileevaluatingaFunctionCall,Functionhiera_include():cannotcallfunction'include'-noloaderspecifiedat/etc/puppetlabs/puppet/manifests/default.pp:23:1onnodepuppet4.vm.super-visions.comError:EvaluationError:ErrorwhileevaluatingaFunctionCall,Functionhiera_include():cannotcallfunction'include'-noloaderspecifiedat/etc/puppetlabs/puppet/manifests/default.pp:23:1onnodepuppet4.vm.super-visions.com{code}
Add Comment
Jira (PUP-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title
Stefan Goethals updated an issue
Puppet / PUP-4046
Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Change By:
Stefan Goethals
Usinghiera_include()withpuppet-agentasofversion0.3.2.29.g49f7b1b-1.el7producesthefollowingerror.{code}[root@puppet4manifests]#/opt/puppetlabs/puppet/bin/puppetapplydefault.pp-tInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsError:EvaluationError:ErrorwhileevaluatingaFunctionCall,uninitializedconstantHiera::PuppetFunctionat/etc/puppetlabs/puppet/manifests/default.pp:17:1onnodepuppet4.vm.super-visions.comError:EvaluationError:ErrorwhileevaluatingaFunctionCall,uninitializedconstantHiera::PuppetFunctionat/etc/puppetlabs/puppet/manifests/default.pp:17:1onnodepuppet4.vm.super-visions.com{code}default.pp{code}hiera_include('classes',[]){code}hiera.yaml{code}---:backends:-yaml:hierarchy:-defaults-%{clientcert}-%{environment}-global:yaml:#datadirisemptyhere,sohierausesitsdefaults:#-/etc/puppetlabs/code/hieradataon*nix#-%CommonAppData%\PuppetLabs\hiera\varonWindows#Whenspecifyingadatadir,makesurethedirectoryexists.:datadir:/etc/puppetlabs/hieradata{code}/etc/puppetlabs/hieradataisempty,sameresultwithaglobal.yamlfiletestedandworkingonpuppet-agent-0.3.2.22.g8642ba7-1.el7(andbefore).puppet.confisemptyMoretestingshowsthefollowing:Whenaddingany/allofthefollowinglines'before'thehiera_include()inthe.ppfiletheerrorchanges.{code}$a=hiera('a','a')$b=hiera_hash('b',{})$c=hiera_array('c',[]){code}The new different error:{code}[root@puppet4~]#puppetapply/etc/puppetlabs/puppet/manifests/default.pp-tInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsError:EvaluationError:ErrorwhileevaluatingaFunctionCall,Functionhiera_include():cannotcallfunction'include'-noloaderspecifiedat/etc/puppetlabs/puppet/manifests/default.pp:23:1onnodepuppet4.vm.super-visions.comError:EvaluationError:ErrorwhileevaluatingaFunctionCall,Functionhiera_include():cannotcallfunction'include'-noloaderspecifiedat/etc/puppetlabs/puppet/manifests/default.pp:23:1onnodepuppet4.vm.super-visions.com{code}
Add Comment
Jira (PUP-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title Stefan Goethals commented on PUP-4046 Re: Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction Thanks for the quick fix. That indeed gets rid of the first error. Now i get the second error: Error: Evaluation Error: Error while evaluating a Function Call, Function hiera_include(): cannot call function 'include' - no loader specified at /etc/puppetlabs/puppet/manifests/default.pp:23:1 on node puppet4.vm.super-visions.com Do you want me to open a separate bug for that? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) Invalid parameter provider for custom types/providers
Title: Message Title Nicholas Fagerlund commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Eric Thompson Okay, so it sounds like the problem was just with providers, and just with resources that specified the provider attribute, right? Could you please update the description to describe that? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) Invalid parameter provider for custom types/providers
Title: Message Title Nicholas Fagerlund assigned an issue to Eric Thompson Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Nicholas Fagerlund Assignee: NicholasFagerlund EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4047) consider 'non productive expression' to be warning
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-4047
consider 'non productive _expression_' to be warning
Issue Type:
Improvement
Assignee:
Unassigned
Components:
DSL
Created:
2015/02/26 9:46 AM
Fix Versions:
PUP 3.7.5
Priority:
Normal
Reporter:
Henrik Lindberg
The new valiidator emits errors for non productive expressions. This because they are meaningless (produce values that are thrown away and does not cause side effects) and probably mask other problems.
While this is good in general - there are cases when developing code that makes this annoying.
Consider this:
if true {
Jira (PUP-4047) consider 'non productive expression' to be warning
Title: Message Title Henrik Lindberg commented on PUP-4047 Re: consider 'non productive _expression_' to be warning ping James Sweeny Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson Summary: Invalidparameterproviderforcustom types/providers shouldbeloadedfromspecifiedenvironment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Eric Thompson QA Contact: ErikDasher EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson assigned an issue to Michael Smith Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Eric Thompson Assignee: EricThompson MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1267) KahaDB Recovery after PostgreSQL database disconnect
Title: Message Title Brian Wong created an issue PuppetDB / PDB-1267 KahaDB Recovery after PostgreSQL database disconnect Issue Type: Bug Affects Versions: PDB 2.2.2 Assignee: Unassigned Created: 2015/02/26 11:49 AM Environment: PostgreSQL 9.3.5, CentOS 7, and PuppetDB 2.2.2 Labels: kahadb postgresql Priority: Normal Reporter: Brian Wong Our database had some connectivity problems but was recovered within a few minutes. In the PuppetDB logs I saw: 2015-02-25 20:11:02,872 ERROR [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms and trying again. Attempts left: 5. Exception: java.net.NoRouteToHostException: No route to host 2015-02-25 20:11:11,890 ERROR [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms and trying again. Attempts left: 4. Exception: java.net.NoRouteToHostException: No route to host 2015-02-25 20:11:20,908 ERROR [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms
Jira (PUP-4048) Custom/external fact can supply non-authoritative environment to Hiera
Title: Message Title Ranjit Viswakumar updated an issue Puppet / PUP-4048 Custom/external fact can supply non-authoritative environment to Hiera Change By: Ranjit Viswakumar Security: Internal Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/728/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1184) Logs: Add logs storage and retrieval support
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1184 Logs: Add logs storage and retrieval support Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4049) System module path should be a thing on Windows
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-4049
System module path should be a thing on Windows
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/02/26 12:05 PM
Priority:
Normal
Reporter:
Josh Cooper
puppet's `basemodulepath` defaults to:
:basemodulepath = {
:default = $codedir/modules#{File::PATH_SEPARATOR}/opt/puppetlabs/puppet/modules,
The system module path is hardcoded to be *nix specific. The default value should be updated to a place that makes sense on Windows, likely C:\ProgramData\PuppetLabs\puppet\modules.
https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md will need to be updated too.
Jira (PUP-1467) DIE :undef, DIE!
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-1467
DIE :undef, DIE!
Change By:
Nicholas Fagerlund
I'mnotsureifthisshouldbeflaggedasabug,afeature,orarefactorbecausethisissuecoversallthree.:)YesterdayafternoonIdiscoveredatemplateinafairlypopularmodulethatdidnotworkcorrectlyonpuppet3.2.1duetoit'suseof`:undef`.Thefixwastoreplace`:undef`with`#nil?`.@@-14,10+14,10@@server{ssl_protocols%=@ssl_protocols%;ssl_ciphers%=@ssl_ciphers%;ssl_prefer_server_cipherson;-%if@auth_basic!=:undef-%+%unless@auth_basic.nil?-%auth_basic%=@auth_basic%;%end-%-%if@auth_basic_user_file!=:undef-%+%unless@auth_basic_user_file.nil?-%auth_basic_user_file%=@auth_basic_user_file%;%end-%Itappearsthatinatleastsomecases(perhapslimitedtoerb?)real`nil`sareleakingoutinsteadof`:undef`.I'veunabletopassan`:undef`intoatemplateatallintestingineither3.2.1or3.2.3.Idon'tknowifthishaseverworkedorisaregression.{code}$catundef_test.ppnotify{'undeclared':message=inline_template('%=@foo==:undef%:%=@foo.nil?%')}$empty=''notify{'empty':message=inline_template('%=@empty==:undef%:%=@empty.nil?%')}$undef=undefnotify{'undef':message=inline_template('%=@undef==:undef%:%=@undef.nil?%')}$false=falsenotify{'false':message=inline_template('%=@false==:undef%:%=@false.nil?%')}$puppet--version3.2.3$puppetapplyundef_test.ppNotice:false:falseNotice:/Stage[main]//Notify[false]/message:defined'message'as'false:false'Notice:false:falseNotice:/Stage[main]//Notify[empty]/message:defined'message'as'false:false'Notice:false:trueNotice:/Stage[main]//Notify[undeclared]/message:defined'message'as'false:true'Notice:false:trueNotice:/Stage[main]//Notify[undef]/message:defined'message'as'false:true'Notice:Finishedcatalogrunin0.11seconds{code}Upondiggingintothepuppetsource,itappearsthatusageandtestingfor`:undef`isinconsistentinthecore.Consider`Puppet::Parser::Scope#true?`thattestsfor`:undef`tobeusedasabooleanvalue.https://github.com/puppetlabs/puppet/blob/3.2.3/lib/puppet/parser/scope.rb#L113-L122.Elsewhereinthesameclass`:undef`isbeingcheckedfordirectlyhttps://github.com/puppetlabs/puppet/blob/3.2.3/lib/puppet/parser/scope.rb#L392Thecaseagainst`:undef`*Itviolatestheprincibleof'leastsurprise'inthatitduplicatesabuiltinlanguagefeature*Inatleastsomecircumstances`nil`leaksoutinplaceof`:undef`*Testcoverageof`:undef`isinsufficent*Usageof`:undef`appearsinconsistentinthecoreI'dagruethatinsteadoftryingtoreplicate/maintainexternallyvisibleinconsistentbehaviorthatitwouldbebettertojustremove`:undef`completelyanddealwiththeAPIchangeallatonce,perhapsina3.3.0release.UPDATETheresolutionofthisisthatPuppet4.0.0and3xwithfutureparserwill :*Alwaysuse translatepuppet {{ nil undef }} internally to representanundefined nilwhenitcallstoruby,andviceversa.(WithinPuppetcode,{{undef}}remainsaspecial value except ofthetype{{Undef}},asdescribed[inthespec|https : //github.com/puppetlabs/puppet-specifications/blob/master/language/types_values_variables.md#undef].)Theexceptionsare: * *whenitcalls 3x functions defined (written usingthe3xfunctionAPI whereundefinedparametervaluesmustbegivenas )-theywillreceivean empty strings,butwherestructures stringinsteadofnilforthetoplevelarguments ( notinside hashesandarrays maycontain{{ etc,where nil }}valueswiththemeaningthattheyareundefined ispassed). *
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) types/providers should be loaded from specified environment
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Nicholas Fagerlund Theautoloadercurrentlyloads Whencompilingacatalog, typesandproviders arevalidated,butwhilePuppetwillloadtypes fromthe agent-requestedenvironment(moduloonlyloadsprovidersfromthe defaultenvironment(production)duringonephaseofthecompilation.Weshouldensureweautoloadtypesandprovidersfromthesameenvironmentthatisspecified.oneexample:Ifyouhaveacustomtype/providerinanotherenvironmentthatisbroken,itshouldnotproduceanerrorinanotherenvironment.originaldescription:InPuppet3Iamgettinganerroronalldefinitionsforcustomtypes.ItsaysError400onSERVER:InvalidparameterproviderProvidershouldbeagivenparameterforcustomtypesbecauseotherwisethereisnowaytospecifywhichprovidershouldbeusedwithit.Thisispotentiallyaverymajorbug.PleaseletmeknowhowIcanhelpsoyou'reabletoreproduceandfixtheissue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1268) Add validation for run interval and numhosts to benchmark
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1268 Add validation for run interval and numhosts to benchmark Issue Type: Bug Assignee: Unassigned Created: 2015/02/26 11:50 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Ryan Senior Currently when you attempt to launch benchmark without a run interval or numhosts, you get an unintuitive NumberFormatException. We should just include a basic check for the param and write out a nice error message if the user doesn't include it. Add Comment
Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-1515
types/providers should be loaded from specified environment
Change By:
Nicholas Fagerlund
Whencompilingacatalog,typesandprovidersarevalidated,butwhilePuppetwillloadtypesfromtheagent -requested 's environment (modulo ,it onlyloadsprovidersfromthe compilingmaster's defaultenvironment(production) duringonephaseofthecompilation . Weshouldensureweautoloadtypesandprovidersfrom Thisisaproblembecause the sameenvironment method that createsthe{{provider}}parameter is specified sometimescalledduetocodeinthe*provider,*notthetype . oneexample: If youhave acustom resource type /provider onlyexists in another anon-default environment ,andyoudeclarearesource that isbroken specifiesavalueforthe{{provider}}attribute , itshouldnotproduce thiscancause an {{invalidparameterprovider}} error inanother .TheexpectedbehavioristhatPuppetwillautoloadtypesandprovidersfromtheagent's environment. originaldescription:InPuppet3Iamgettinganerroronalldefinitionsforcustomtypes.ItsaysError400onSERVER:InvalidparameterproviderProvidershouldbeagivenparameterforcustomtypesbecauseotherwisethereisnowaytospecifywhichprovidershouldbeusedwithit.Thisispotentiallyaverymajorbug.PleaseletmeknowhowIcanhelpsoyou'reabletoreproduceandfixtheissue. Finalresolution:Whenvalidatingresourcesduringcatalogcompilation,Puppetwillloadtypesandprovidersfromtheenvironmentthatthecatalogisbeingcompiledfor.(Modulothatotherbugthatcausescross-environmentcontamination.)
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You
Jira (PUP-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Nicholas Fagerlund assigned an issue to Charlie Sharpsteen Puppet / PUP-1515 When compiling a catalog, providers should be loaded from specified environment Change By: Nicholas Fagerlund Assignee: NicholasFagerlund CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1515 When compiling a catalog, providers should be loaded from specified environment Change By: Nicholas Fagerlund Summary: types/ Whencompilingacatalog, providersshouldbeloadedfromspecifiedenvironment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Michael Smith created an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Issue Type: Bug Assignee: Unassigned Created: 2015/02/26 12:06 PM Priority: Normal Reporter: Michael Smith According to https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md#puppet-agent-windows, :codedir is at C:\ProgramData\PuppetLabs\code. The install.rb in Puppet sets it to C:\ProgramData\PuppetLabs\puppet\code, which is incorrect. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Component/s: Windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson Ifyouhaveacustomtype/providerinanotherenvironmentthatisbroken,itshouldnotproduceanerrorinanotherenvironment.Theautoloadercurrentlyloadstypesandprovidersfromthedefaultenvironment(production)duringonephaseofthecompilation.Weshouldensureweautoloadtypesandprovidersfromthesameenvironmentthatisspecified.originaldescription: InPuppet3Iamgettinganerroronalldefinitionsforcustomtypes.ItsaysError400onSERVER:InvalidparameterproviderProvidershouldbeagivenparameterforcustomtypesbecauseotherwisethereisnowaytospecifywhichprovidershouldbeusedwithit.Thisispotentiallyaverymajorbug.PleaseletmeknowhowIcanhelpsoyou'reabletoreproduceandfixtheissue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt wkalt commented: @senior has raised the issue that we don't ship the acceptance directory, so as written package users won't be able to use the -D flag. This shouldn't be merged until we figure out what to do there. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1256) PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker
Title: Message Title gepetto-bot commented on PDB-1256 Re: PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker wkalt commented: +1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1190) Logs: (query) Anonymization for report logs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1190 Logs: (query) Anonymization for report logs Change By: Kenneth Barber Sprint: PuppetDB2015- 04 03 - 08 25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson Ifyouhaveacustomtype/providerinanotherenvironmentthatisbroken,itshouldnotproduceanerrorinanotherenvironment. Theautoloadercurrentlyloadstypesandprovidersfromthedefaultenvironment(production)duringonephaseofthecompilation.Weshouldensureweautoloadtypesandprovidersfromthesameenvironmentthatisspecified. oneexample: Ifyouhaveacustomtype/providerinanotherenvironmentthatisbroken,itshouldnotproduceanerrorinanotherenvironment. originaldescription:InPuppet3Iamgettinganerroronalldefinitionsforcustomtypes.ItsaysError400onSERVER:InvalidparameterproviderProvidershouldbeagivenparameterforcustomtypesbecauseotherwisethereisnowaytospecifywhichprovidershouldbeusedwithit.Thisispotentiallyaverymajorbug.PleaseletmeknowhowIcanhelpsoyou'reabletoreproduceandfixtheissue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Eric Thompson Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson assigned an issue to Nicholas Fagerlund Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson commented on PUP-3632 Re: Update paths and defaults for the unified FS layout Michael Smith this can probably be resolved if your experience with the acceptance test tells you it is appropriate. please ping me with the PR when you are done. thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/726/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4051) Master unable to reliably reload puppet.conf
Title: Message Title Rolf created an issue Puppet / PUP-4051 Master unable to reliably reload puppet.conf Issue Type: Bug Assignee: Andy Parker Components: Server Created: 2015/02/26 12:53 PM Priority: Normal Reporter: Rolf The webrick puppet master watches its config file for changes. When the file changes, it then will reload the file, and try to apply a new settings catalog. However, depending on what the settings catalog will end up doing, this may throw an error, which results in the master process shutting down. You can reproduce this problem by simply starting a puppet master daemon, opening the /etc/puppet/puppet.conf file, and inserting the line: ssldir = /var/lib/puppet/ssl2 This should cause the master to crash. The problem stems from the fact that the master has dropped privileges as part of daemonizing. Therefore there are certain changes to the system that it simply can't
Jira (PUP-4051) Master unable to reliably reload puppet.conf
Title: Message Title
Rolf updated an issue
Puppet / PUP-4051
Master unable to reliably reload puppet.conf
Change By:
Rolf
Thewebrickpuppetmasterwatchesits{{config}}fileforchanges.Whenthefilechanges,itthenwillreloadthefile,andtrytoapplyanewsettingscatalog.However,dependingonwhatthesettingscatalogwillendupdoing,thismaythrowanerror,whichresultsinthemasterprocessshuttingdown. Youcanreproducethisproblembysimplystarting Whiledebugginganunrelatedpuppetdbissue,Ichangeddebug_levelon a vagranttestingrecipeIusefortestingroleswithexportedresources.Iaddedlog_level=debugandsuddenlymynodeswouldstartgetting puppet masterdaemon,openingthe{{/etc/puppet/puppet runfailures . conf}}file, Arestartwasneeded and inserting the line:{noformat}ssldir=/var/lib/ nodeswouldthengetsuccessful puppet /ssl2 runs. {noformat} This It should cause benotedthat the master catalogwouldcompilejustfine.Inparticular,thefailureswerearoundhieradatafromparentclasses.Icompiledthecatalog to crash verifythehieralookupwasfoundappropriately . Theproblemstemsfromthefact PUP-2834wasclosedaswont-fixbutIthinkminimally thatthe masterhasdroppedprivilegesaspart puppetconfigautoreloadshouldbedisabledonwebrickinstances.Thiskind of daemonizing erroneousbehaviormakestroubleshootingallbutimpossible . Thereforetherearecertainchangestothesystemthatitsimplycan'tperform.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you 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-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Elyse Salberg commented on PUP-1515 Re: When compiling a catalog, providers should be loaded from specified environment Not to hijack this ticket, but I just ran into a situation where I update a module with a custom type/provider, and while I could see the updated type/provider in my environments, the agent could not utilize them until I restarted the pe-puppetserver process. If we're talking about loading providers from specified environments, could there be a situation of needing to kick the pe-puppetserver process in between, or was my situation different / unrelated? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1247) Get the TK max-threads fixes on stable
Title: Message Title Russell Mull commented on PDB-1247 Re: Get the TK max-threads fixes on stable Upon further investigation, PDB-813 already included code to handle old-style cert-whitelist config. Since it applies pretty cleanly to stable, I'm going with a straight backport. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Heidi Pio updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Heidi Pio Scope Change Reason: Blockerworkthatneedstobecompletedasap Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Scope Change Reason: Blockerworkthatneedstobecompletedasap Windowsacceptancebrokenwithoutthesechanges Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Sprint: Client Windows 2015-03- 04 11 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Assignee: EthanBrown Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Scrum Team: ClientPlatform Windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Lindsey Smith assigned an issue to Lindsey Smith Puppet / PUP-1515 When compiling a catalog, providers should be loaded from specified environment Change By: Lindsey Smith Assignee: CharlieSharpsteen LindseySmith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown commented on PUP-4050 Re: Install.rb uses incorrect path on Windows for codedir With the changes introduced by PUP-4034 / PUP-4037 to change default Windows path for :vardir, default values in the acceptance setup were incidentally broken. This wasn't noticed immediately, since acceptance for Windows packages has been recently disabled. This was an oversight and should have been addressed in https://github.com/puppetlabs/puppet/pull/3646, but was not. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Acceptance suite uses incorrect paths on Windows for codedir
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-4050
Acceptance suite uses incorrect paths on Windows for codedir
Change By:
Ethan Brown
Accordingtohttps://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md#puppet-agent-windows,{{:codedir}}isat{{C:\ProgramData\PuppetLabs\code}}.Theinstall.rbinPuppetsetsitto{{C:\ProgramData\PuppetLabs\puppet\code}},whichisincorrect. Additionally,theexistingYAMLfilesbeingusedforacceptancethatfeaturethesepathsshouldbemodified:https://github.com/puppetlabs/puppet/blob/master/acceptance/config/nodes/win2012r2-rubyx64.yamlhttps://github.com/puppetlabs/puppet/blob/master/acceptance/config/nodes/win2012r2-rubyx86.yaml
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-4050) Acceptance suite uses incorrect paths on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Acceptance suite uses incorrect paths on Windows for codedir Change By: Ethan Brown Summary: Install.rb Acceptancesuite usesincorrect path paths onWindowsforcodedir Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1099) make the /v4/catalogs endpoint use certname key instead of name
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1099 make the /v4/catalogs endpoint use certname key instead of name Change By: Russell Mull Assignee: RussellMull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1247) Get the TK max-threads fixes on stable
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1247 Get the TK max-threads fixes on stable Change By: Russell Mull Assignee: RussellMull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4050) Acceptance suite and install.rb use incorrect paths on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Acceptance suite and install.rb use incorrect paths on Windows for codedir Change By: Ethan Brown Summary: Acceptancesuite uses andinstall.rbuse incorrectpathsonWindowsforcodedir Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-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.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Thomas Hallgren commented on PUP-3296 Re: Remove handling and mention of :before and :after for parameters A comment in the code suggests that by removing :before and :after it should be OK to also remove the call option altogether. This seems to be the case. Valid settings for this option today is :instead or :none and this is not needed since it's only use is to check if a block has been given or not (can be checked by just looking at the value.block). My question is, is there a need to support the call option for backward compatibility? Do we expect to encounter user code with :call = :instead or :call = :none? If so, what do we do with it? One option is to always mark it as deprecated and to error out if :instead is used without a block or :none is used with one. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-4045
Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/02/26 1:58 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Using a slightly modified version of the code from Pro Puppet I am getting the following error:
Jun 13 01:36:33 media puppet-agent[18196]: (/Stage[main]/Mysql::Config/File[mysql_data_dir]) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
The file resource in mysql/manifests/config.pp is as follows:
file { mysql_data_dir : path = $mysql::params::data_directory, group = mysql, owner = mysql, recurse = true, require = File[my.cnf], }
And for this particular $operatingsystem (Fedora) the value for $data_directory in mysql/manifests/params.pp is :
$data_directory = /var/lib/mysql
By default mysql on a Fedora system places its mysql.sock file in the data directory but it appears when a you try and change the permissions recursively, puppet doesn't know what to do with the socket file.
I can place the socket file elsewhere as a work around but I believe that puppet needs to ignore socket files when changing permissions.
[root@media modules]# puppet --version 2.6.8
Jira (PUP-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title Stefan Goethals created an issue Puppet / PUP-4046 Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction Issue Type: Bug Affects Versions: PUP 4.x Assignee: Kylo Ginsberg Components: Client Created: 2015/02/26 3:58 AM Environment: Vagrant Atlas box puppetlabs/centos-7.0-64-nocm Priority: Normal Reporter: Stefan Goethals Using hiera_include() with puppet-agent as of version 0.3.2.29.g49f7b1b-1.el7 produces the following error. [root@puppet4 manifests]# /opt/puppetlabs/puppet/bin/puppet apply default.pp -t
Jira (PUP-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title
Stefan Goethals updated an issue
Puppet / PUP-4046
Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Change By:
Stefan Goethals
Usinghiera_include()withpuppet-agentasofversion0.3.2.29.g49f7b1b-1.el7producesthefollowingerror.{code}[root@puppet4manifests]#/opt/puppetlabs/puppet/bin/puppetapplydefault.pp-tInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsError:EvaluationError:ErrorwhileevaluatingaFunctionCall,uninitializedconstantHiera::PuppetFunctionat/etc/puppetlabs/puppet/manifests/default.pp:17:1onnodepuppet4.vm.super-visions.comError:EvaluationError:ErrorwhileevaluatingaFunctionCall,uninitializedconstantHiera::PuppetFunctionat/etc/puppetlabs/puppet/manifests/default.pp:17:1onnodepuppet4.vm.super-visions.com{code}default.pp{code}hiera_include('classes',[]){code}hiera.yaml{code}---:backends:-yaml:hierarchy:-defaults-%{clientcert}-%{environment}-global:yaml:#datadirisemptyhere,sohierausesitsdefaults:#-/etc/puppetlabs/code/hieradataon*nix#-%CommonAppData%\PuppetLabs\hiera\varonWindows#Whenspecifyingadatadir,makesurethedirectoryexists.:datadir:/etc/puppetlabs/hieradata{code}/etc/puppetlabs/hieradataisempty,sameresultwithaglobal.yamlfiletestedandworkingonpuppet-agent-0.3.2.22.g8642ba7-1.el7(andbefore).puppet.confisempty Moretestingshowsthefollowing: Whenaddingany/allofthefollowinglines'before'thehiera_include()inthe.ppfiletheerrorchanges.{code}$a=hiera('a','a')$b=hiera_hash('b',{})$c=hiera_array('c',[]){code}Thenewerror:{code}[root@puppet4~]#puppetapply/etc/puppetlabs/puppet/manifests/default.pp-tInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsInfo:LoadingfactsError:EvaluationError:ErrorwhileevaluatingaFunctionCall,Functionhiera_include():cannotcallfunction'include'-noloaderspecifiedat/etc/puppetlabs/puppet/manifests/default.pp:23:1onnodepuppet4.vm.super-visions.comError:EvaluationError:ErrorwhileevaluatingaFunctionCall,Functionhiera_include():cannotcallfunction'include'-noloaderspecifiedat/etc/puppetlabs/puppet/manifests/default.pp:23:1onnodepuppet4.vm.super-visions.com{code}
Add Comment
Jira (PUP-3845) Windows Unified Installer should track internal component versions
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3845 Windows Unified Installer should track internal component versions Change By: Steve Barlow Scope Change Reason: AIODiscovery Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1257) PR (1280): (maint) Switch us to use c4.large instances for acceptance - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1257 PR (1280): (maint) Switch us to use c4.large instances for acceptance - kbarber Change By: Steve Barlow Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1256) PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker
Title: Message Title gepetto-bot commented on PDB-1256 Re: PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker senior commented: +1 from me too, will get it merged this evening Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3845) Windows Unified Installer should track internal component versions
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3845 Windows Unified Installer should track internal component versions Change By: Steve Barlow Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4001) Packaging should create default module directories for puppet
Title: Message Title Melissa Stone commented on PUP-4001 Re: Packaging should create default module directories for puppet This was merged in at https://github.com/puppetlabs/puppet-agent/commit/272efd2ef821fe120da848a0b02f7e5d2888a5ce Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4052) puppet module generate uses invalid default license identifier
Title: Message Title Kylo Ginsberg commented on PUP-4052 Re: puppet module generate uses invalid default license identifier I believe this is a dup of PUP-3894 , so closing. Please reopen if that's not the case! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4034) Update MSI for AIO
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4034 Update MSI for AIO Change By: Steve Barlow Scope Change Reason: AIODiscovery Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal This can be verified without using mco. 1) Start a puppet master (webrick or puppet-server, whatever is easiest for you). It can be a little easier if you turn on --verbose, because it will be obvious when the agent checks in. 2) Start an agent daemonized pointing at the puppet master (you'll see that it checks in with the master, this is SOP not part of this fix). 3) Send the agent a USR1 signal. Find the agent pid, and issue 'kill -USR1 pid'. In about 5 seconds (exact timing isn't a requirement), you should see the agent checking in with the master. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1239) PR (1258): Remove pinning against a git sha1 for beaker now ezbake helpers have been released - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1239 PR (1258): Remove pinning against a git sha1 for beaker now ezbake helpers have been released - kbarber Change By: Steve Barlow Scope Change Reason: StayinginsyncwithEZBAKEupdatethathappenedduringsprint Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1242) PR (1264): Remove some unused legacy query code - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1242 PR (1264): Remove some unused legacy query code - kbarber Change By: Steve Barlow Scope Change Reason: Somecodecleanupandremoval.Didnotblockanyticketbutwastrivialanddidnotwanttoleaveinastechdebt. Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-3986 Expand predefined OID's for Puppet's extension attributes Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4001) Packaging should create default module directories for puppet
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-4001 Packaging should create default module directories for puppet Change By: Melissa Stone Assignee: MelissaStone Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Henrik Lindberg commented on PUP-1515 Re: When compiling a catalog, providers should be loaded from specified environment Elyse Salberg The problem you are describing is most likely something else. This ticket is for a problem when the compiler validates a resource and picks a provider from the wrong environment. Sounds more related to similar problems with pluginsync. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3296 Remove handling and mention of :before and :after for parameters Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-3296
Remove handling and mention of :before and :after for parameters
Change By:
Nicholas Fagerlund
{{Puppet::Resource::ValueCollection}}and{{Puppet::Property}}bothmentionusing{{:before}}and{{:after}}butthatishasn'tbeensupportedforyears.Weneedtoremovethementionofitandanycodethatistryingtohandleit,evenifonlytoerror.Theremightbesimplificationsthatcanbedonebecauseofthis(thecommentsseemtoindicatethis). Fordocs-thiswasprobablyonlyaninternalaffairastheremovedcapabilitywasprobablynotmentionedinanyuserdocumentationfrompuppetlabs.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1003) You shall not pass! error could be more informative
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1003 You shall not pass! error could be more informative Change By: Steve Barlow Scope Change Reason: Wasincludedjustaftersprintplanning.Intentionwastohaveitinsprint.Misclick. Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4051) Master unable to reliably reload puppet.conf
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-4051 Master unable to reliably reload puppet.conf Change By: Henrik Lindberg Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1244) Status: (query) Add capability for latest-report? handling for reports
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1244 Status: (query) Add capability for latest-report? handling for reports Change By: Steve Barlow Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1249 PR (1270): (maint) benchmark improvements - wkalt Change By: Steve Barlow Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1243) We should accept null fields for noop for incoming commands
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1243 We should accept null fields for noop for incoming commands Change By: Steve Barlow Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1248) Write Initial PuppetDB 3.0 Release Notes
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1248 Write Initial PuppetDB 3.0 Release Notes Change By: Steve Barlow Scope Change Reason: Russjoinedteam.Pulledinsometasksforhim Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1258) PR (1281): (maint) Switch to different subnet-id for different availability zone - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1258 PR (1281): (maint) Switch to different subnet-id for different availability zone - kbarber Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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.
