Jira (PUP-7931) Support HTTPS Compression on report upload
Title: Message Title Adrian created an issue Puppet / PUP-7931 Support HTTPS Compression on report upload Issue Type: New Feature Affects Versions: PUP 5.1.0 Assignee: Adrian Created: 2017/09/11 7:08 AM Environment: All OS, all agents etc. Priority: Normal Reporter: Adrian On very low bandwidth connections (cellular and such) the reports can be very costly. I have developed a patch which I will be submitting shortly to enable optional HTTPS compression for the report uploads. While this is not supported directly by puppet-server, having a proxy in front allows for the compression and gives more options for low bandwidth connections Add Comment
Jira (PUP-2935) De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7
Title: Message Title
adrian commented on an issue
Re: De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7
These are the three manifest involved. https://gist.github.com/b9605efeab711ea2e1bc
The idea is pass a json to monitorizacion::checks::collectd params parameter. This json contains one array (Threshold), where the user could define several different thresholds. In ruby or other programming language I will use a loop to go over the array and generate each of the thresholds. As this is difficult in puppet I use the idea seen here: https://tobrunet.ch/2013/01/iterate-over-datastructures-in-puppet-manifests/ When a array is passed to a defined type, it is executed once per element.
Inside each threshold object there is another array, and the same strategy is used, sending to a defined type to go over all elements of the array.
Also I have to insert and id element to avoid duplicated resources (for example if two different thresholds have the same type with same parameters).
P.D.: any constructive criticism is welcome
Add Comment
Puppet / PUP-2935
De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7
With that environment, if I execute: {code} # puppet apply --catalog client1-catalog.json Error: Could not run: Could not deserialize catalog from pson: Could not intern from pson: Could not intern from data: Could not find relationship target Notify[{\type\=\A\}] {code} If I execute in Ubuntu 14.04 with Puppet 3.6.2 ruby-json 1.8.0-1build...
Jira (PUP-2935) Error deserializing JSON in CentOS
Title: Message Title
adrian created an issue
Puppet / PUP-2935
Error deserializing JSON in CentOS
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Andy Parker
Attachments:
client1-catalog.json
Components:
DSL
Created:
15/Jul/14 11:10 AM
Environment:
puppet 3.6.2 ruby 1.8.7 (2011-06-30 patchlevel 352) json 1.8.1 (gem) CentOS 6.4
Priority:
Normal
Reporter:
adrian
With that environment, if I execute:
# puppet apply --catalog client1-catalog.json
Error: Could not run: Could not deserialize catalog from pson: Could not intern from pson: Could not intern from data: Could not find relationship target Notify[{\type\=\A\}]
Jira (PUP-2893) Delete nagios parameters
Title: Message Title
adrian created an issue
Puppet / PUP-2893
Delete nagios parameters
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
04/Jul/14 4:33 AM
Environment:
Ubuntu 14.04 ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] puppet-3.6.2 facter-2.1.0 hiera-1.3.4
Priority:
Normal
Reporter:
adrian
If I apply this manifest: nagios_host { hostname: ensure = present, target = /tmp/host.nagios, address = 1.1.1.1, host_name = nombrehost, notes_url = info.cgi/$HOSTNAME$, }
It generates this file: define host { address 1.1.1.1 host_name nombrehost notes_url info.cgi/$ }
If later I stop using notes_url: nagios_host { hostname: ensure = present, target = /tmp/host.nagios, address = 1.1.1.1, host_name = nombrehost, # notes_url = info.cgi/$HOSTNAME$, }
The configuration file is not modified, and notes_url remains setted.
How could be done to remove that parameter?
A quick
Jira (PUP-1109) Convert puppet startup script to upstart
Title: Message Title adrian commented on an issue Re: Convert puppet startup script to upstart Upstart is deprecated: http://www.markshuttleworth.com/archives/1316 Add Comment Puppet / PUP-1109 Convert puppet startup script to upstart May be a won't-fix, but converting puppet init.d scripts to upstart has significant benefits on distributions that use upstart. The reason I'm interested in this is relying on the respawn stanza, which would allow us to work around PUP-202. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2772) init.d script wrong pidfile
Title: Message Title
adrian commented on an issue
Re: init.d script wrong pidfile
Created pull request with the pidfile changed: https://github.com/puppetlabs/puppet/pull/2762
Add Comment
Puppet / PUP-2772
init.d script wrong pidfile
The init.d script installed with the Ubuntu package (https://github.com/puppetlabs/puppet/blob/master/ext/debian/puppetmaster.init) set the pidfile to /var/run/puppet/${NAME}.pid but the pidfile is actually in /var/lib/puppet/run/${NAME}.pid Seems that the instruction: start-stop-daemon --start --quiet --pidfile /var/lib/puppet/run/${NAME}.pid \ ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2772) init.d script wrong pidfile
Title: Message Title
adrian created an issue
Puppet / PUP-2772
init.d script wrong pidfile
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Release Engineering
Components:
RE
Created:
12/Jun/14 9:36 AM
Environment:
puppetmaster-3.6.2-1puppetlabs1
Priority:
Normal
Reporter:
adrian
The init.d script installed with the Ubuntu package (https://github.com/puppetlabs/puppet/blob/master/ext/debian/puppetmaster.init) set the pidfile to /var/run/puppet/$ {NAME}.pid but the pidfile is actually in /var/lib/puppet/run/${NAME}
.pid
Seems that the instruction: start-stop-daemon --start --quiet --pidfile /var/lib/puppet/run/$ {NAME}
.pid \ --startas $DAEMON – $NAME $DAEMON_OPTS --masterport=$PORT doesn't work correctly.
Jira (PUP-2649) hiera_include with Puppet 3.5
Title: Message Title
adrian created an issue
Puppet / PUP-2649
hiera_include with Puppet 3.5
Issue Type:
Bug
Affects Versions:
3.6.1, 3.6.0, 3.5.1, 3.5.0
Assignee:
Andy Parker
Components:
DSL
Created:
23/May/14 2:36 AM
Priority:
Normal
Reporter:
adrian
With Puppet 3.5 comes deprecation of import (http://docs.puppetlabs.com/puppet/latest/reference/lang_import.html), so all node definitions should be in different files each of one should begin with node ..., it is correct?
Which is the correct way to use hiera_include in Puppet 3.5+? Because in the doc (http://docs.puppetlabs.com/hiera/1/puppet.html#assigning-classes-to-nodes-with-hiera-hierainclude) it says In your main manifest, write the line hiera_include('classes'). Put this outside any node definition.
Add Comment
Jira (PUP-1757) Sporadic Error 400 on SERVER: Could not find class xxx for node [node] on [node] problems
Title: Message Title adrian commented on an issue Re: Sporadic Error 400 on SERVER: Could not find class xxx for node [node] on [node] problems I have the same issue with client: puppet-3.4.3-1.el6.noarch facter-1.7.4-1.el6.x86_64 And master: hiera-1.3.2-1.el6.noarch puppet-3.3.2-1.el6.noarch puppetdb-1.5.2-1.el6.noarch facter-1.7.3-1.el6.x86_64 puppetdb-terminus-1.5.2-1.el6.noarch puppet-server-3.3.2-1.el6.noarch From time to time the following error occurs: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class monitorizacion::basic at /var/lib/puppet/initiatives/monitoring/modules/monitorizacion/manifests/check.pp:8 on node xx Add Comment Puppet / PUP-1757 Sporadic Error 400 on SERVER: Could not find class xxx for node [node] on [node] problems Using the following Puppet packages: puppetdb-1.2.0-1.el6.noarch puppet-3.2.0-0.1rc1.el6.noarch puppet-dashboard-1.2.23-1.el6.noarch puppetdb-terminus-1.2.0-1.el6.noarch puppet-server-3.2.0-0.1rc1.el6.noarch ..with Ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] ..on RHEL 2.6.32-220.13.1.el6.x86_64 Dashboard-based ENC. Puppet... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2627) Collecting defined types in masterless configuration
Title: Message Title adrian created an issue Puppet / PUP-2627 Collecting defined types in masterless configuration Issue Type: Bug Affects Versions: 3.6.0 Assignee: Andy Parker Components: DSL Created: 20/May/14 3:22 PM Environment: puppet-3.6.0-1.el6.noarch puppetdb-terminus-2.0.0-1.el6.noarch facter-1.7.2-1.el6.x86_64 hiera-1.3.2-1.el6.noarch CentOS 6.4 Labels: masterless defined types exported resources Priority: Normal Reporter: adrian I am setting an development environment with three hosts in masterless configuration. One node plays the puppetdb role. Another one is the client, exporting some resources (in particular, some defined types). The last one is the server, collecting the client's exported resources. I have configured the
Jira (PUP-2627) Collecting defined types in masterless configuration
Title: Message Title
adrian updated an issue
Puppet / PUP-2627
Collecting defined types in masterless configuration
Change By:
adrian
Iamsettingandevelopmentenvironmentwiththreehostsinmasterlessconfiguration.Onenodeplaysthepuppetdbrole.Anotheroneistheclient,exportingsomeresources(inparticular,somedefinedtypes).Thelastoneistheserver,collectingtheclient'sexportedresources.Ihaveconfiguredthethreeofthemfollowingthisdochttp://docs.puppetlabs.com/puppetdb/latest/connect_puppet_apply.htmlTheproblemiswhentheservertriestocollecttheexporteddefinedtype:Mycustom::Definedtype||{}Thefollowingerrorisshow:Error:Puppet::Parser::CompilerfailedwitherrorArgumentError:wrongnumberofarguments(0for1)onnodelocalhostWrappedexception:wrongnumberofarguments(0for1)Error:Puppet::Parser::CompilerfailedwitherrorArgumentError:wrongnumberofarguments(0for1)onnodelocalhostThiserrorisshowincorrectlyaspointedinhttps://tickets.puppetlabs.com/browse/PUP-2506Fixingthatissuethe(proper)errorshowis:Error:CouldnotfindtypeMycustom::Definedtypeonnodeserver.comTheworkaround(orsolution)thatIhavefoundistoremovethisfrom/etc/puppet/routes.yamlresource:terminus:ralcache:puppetdbIdon'tfullyunderstantwhatthatisfor,butreadingthebeforementioneddoc,seemsthatistokeepthepuppetresourcesubcommandfrommalfunctioning,butmakingsometestsIcannotmaketoworktheresourcesubcommand: # $ puppetresourcefile/etc/passwdError:Couldnotrun:Nocontenttypeinhttpresponse;cannotparseThiscommandisaskingtopuppetdb:GET/production/resource/file//etc/passwd?HTTP/1.0Andpuppetdbisreturninga404.Theworkaroundtomakethatcommandworksistosetstoreconfigs=falsein/etc/puppet/puppet.conf,butinthatcaseisnotpossibletocollectresources.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2627) Collecting defined types in masterless configuration
Title: Message Title
adrian updated an issue
Puppet / PUP-2627
Collecting defined types in masterless configuration
Change By:
adrian
Iamsettingandevelopmentenvironmentwiththreehostsinmasterlessconfiguration.Onenodeplaysthepuppetdbrole.Anotheroneistheclient,exportingsomeresources(inparticular,somedefinedtypes).Thelastoneistheserver,collectingtheclient'sexportedresources.Ihaveconfiguredthethreeofthemfollowingthisdochttp://docs.puppetlabs.com/puppetdb/latest/connect_puppet_apply.htmlTheproblemiswhentheservertriestocollecttheexporteddefinedtype:Mycustom::Definedtype||{}Thefollowingerrorisshow:Error:Puppet::Parser::CompilerfailedwitherrorArgumentError:wrongnumberofarguments(0for1)onnodelocalhostWrappedexception:wrongnumberofarguments(0for1)Error:Puppet::Parser::CompilerfailedwitherrorArgumentError:wrongnumberofarguments(0for1)onnodelocalhostThiserrorisshowincorrectlyaspointedinhttps://tickets.puppetlabs.com/browse/PUP-2506Fixingthatissuethe(proper)errorshowis:Error:CouldnotfindtypeMycustom::Definedtypeonnodeserver.comTheworkaround(orsolution)thatIhavefoundistoremovethisfrom/etc/puppet/routes.yamlresource:terminus:ralcache:puppetdbIdon'tfullyunderstantwhatthatisfor,butreadingthebeforementioneddoc,seemsthatistokeepthepuppetresourcesubcommandfrommalfunctioning,butmakingsometestsIcannotmaketoworktheresourcesubcommand:$puppetresourcefile/etc/passwdError:Couldnotrun:Nocontenttypeinhttpresponse;cannotparseThiscommandisaskingtopuppetdb:GET/production/resource/file//etc/passwd?HTTP/1.0Andpuppetdbisreturninga404.Theworkaroundtomakethatcommandworksistosetstoreconfigs=falsein/etc/puppet/puppet.conf,butinthatcaseisnotpossibletocollectresources. Tosummarize:#ItisneededtofixPUP-2506#RALseemstobebrokenwithcollectingresources#puppetresourcedoesn'tseemtofollowroutes.yaml
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2506) Trivial Ruby bug in Puppet::Resource::Ral
Title: Message Title
adrian commented on an issue
Re: Trivial Ruby bug in Puppet::Resource::Ral
I think this small change will be enough:
def type( request )
Puppet::Type.type(type_name(request)) or raise Puppet::Error, Could not find type #{type_name(request)}
end
Add Comment
Puppet / PUP-2506
Trivial Ruby bug in Puppet::Resource::Ral
The bug is triggered when the Puppet::Error string is interpolated. The #type method is called recursively and fails with an ArgumentError: wrong number of arguments (0 for 1). {code:none} def type( request ) Puppet::Type.type(type_name(request)) or raise Puppet::Error, Could not find type #{type} end {code} bq. https://github.com/puppet...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian commented on an issue Re: Allow wildcards in hierarchy Yeah, you are right. 1. could be easy to fix 2. fixing yaml could be easy, but could be dozens of custom backends that will get broken 3. My problem is I want projects to define their own hostgroups, host templates, etc, and one node, Icinga/Nagios host, to implement all of them. But sure, reading and parsing dozens of json files in each lookup is definitely a bad idea. I am thinking moving to some other backend as mysql or redis. Thanks! Add Comment Hiera / HI-120 Allow wildcards in hierarchy It would be great to allow wildcards when defining the hierarchy in hiera.yaml. Example: In want to have a directory tree like this: hiera/project-name/common.json hiera/project-name/webservers.json But the number of projects is variable. So I want to define a hiera.yaml like: :backends: - json :json: :datadir: /tmp/pruebas-hiera/hie... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian created an issue Hiera / HI-120 Allow wildcards in hierarchy Issue Type: Improvement Assignee: Eric Sorenson Created: 23/Dec/13 8:11 AM Priority: Normal Reporter: adrian It would be great to allow wildcards when defining the hierarchy in hiera.yaml. Example: In want to have a directory tree like this: hiera/project-name/common.json hiera/project-name/webservers.json But the number of projects is variable. So I want to define a hiera.yaml like: :backends: json :json: :datadir: /tmp/pruebas-hiera/hiera :hierarchy: */webservers */common In that files, for instance, will be the users that some node have to create. Add Comment
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian updated an issue Hiera / HI-120 Allow wildcards in hierarchy Change By: adrian Itwouldbegreattoallowwildcards (*) whendefiningthehierarchyinhiera.yaml.Example:Inwanttohaveadirectorytreelikethis:hiera/project-name/common.jsonhiera/project-name/webservers.jsonButthenumberofprojectsisvariable.SoIwanttodefineahiera.yamllike::backends:-json:json::datadir:/tmp/pruebas-hiera/hiera:hierarchy:-*/webservers-*/commonInthatfiles,forinstance,willbetheusersthatsomenodehavetocreate. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian commented on an issue Re: Allow wildcards in hierarchy I have created a pull request: https://github.com/puppetlabs/hiera/pull/169 Add Comment Hiera / HI-120 Allow wildcards in hierarchy It would be great to allow wildcards when defining the hierarchy in hiera.yaml. Example: In want to have a directory tree like this: hiera/project-name/common.json hiera/project-name/webservers.json But the number of projects is variable. So I want to define a hiera.yaml like: :backends: - json :json: :datadir: /tmp/pruebas-hiera/hie... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
