Jira (PUP-1643) Puppet 3.4.3 Release
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-1643 Puppet 3.4.3 Release Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title
Trevor Vaughan updated an issue
Hiera / HI-183
Really need the ability to lookup hashes and arrays from other parts of Hiera.
Change By:
Trevor Vaughan
So,backintheoldRedminesystem,therewasfeature# 23302 23323 ,whichneededtobeabletolookuphashesandarraysfromotherpartsofHiera.Iwouldliketoreinstatethatrequestheresincethecurrentsolutiononlypartiallymeetscommondatamanagementconsolidationneeds.Forinstance,considerthisscenario:{code}==hiera.yaml==%{module_name}/defaultdefault==default.yaml==trusted_domains:-sales.local-dev.local==web_server/default.yaml==web_server::trusted_domains:-sales.local-dev.local==email_server/default.yaml==email_server::trusted_domain:-sales.local-dev.local{code}Nowthisisobviouslycontrived,butitmakesitverystraightforwardtohavethedefaultsforeachmoduleonthesystemseparatedandnotinasinglehugefile.Eveninasinglefile,youwouldhavethesameissuewithhavingtogothrougheachandeveryfieldandmakeupdateswhichwould,ofcourse,bequiteerrorprone.Ifwecouldsimplyreferencetheoriginalhieravariableandhavethearraycarriedacrosstheboard,itwouldmakeeverythingjustworkwiththeopportunityoflocaloverrides.
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-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title
Trevor Vaughan updated an issue
Hiera / HI-183
Really need the ability to lookup hashes and arrays from other parts of Hiera.
Change By:
Trevor Vaughan
So,backintheoldRedminesystem,therewasfeature#23323 (http://projects.puppetlabs.com/issues/23323) ,whichneededtobeabletolookuphashesandarraysfromotherpartsofHiera.Iwouldliketoreinstatethatrequestheresincethecurrentsolutiononlypartiallymeetscommondatamanagementconsolidationneeds.Forinstance,considerthisscenario:{code}==hiera.yaml==%{module_name}/defaultdefault==default.yaml==trusted_domains:-sales.local-dev.local==web_server/default.yaml==web_server::trusted_domains:-sales.local-dev.local==email_server/default.yaml==email_server::trusted_domain:-sales.local-dev.local{code}Nowthisisobviouslycontrived,butitmakesitverystraightforwardtohavethedefaultsforeachmoduleonthesystemseparatedandnotinasinglehugefile.Eveninasinglefile,youwouldhavethesameissuewithhavingtogothrougheachandeveryfieldandmakeupdateswhichwould,ofcourse,bequiteerrorprone.Ifwecouldsimplyreferencetheoriginalhieravariableandhavethearraycarriedacrosstheboard,itwouldmakeeverythingjustworkwiththeopportunityoflocaloverrides.
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-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Trevor Vaughan commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. Sorry about that, it was 23323, I updated the issue with the proper links. Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... 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 (PUP-1712) Add Ubuntu 14.04 to acceptance
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-1712 Add Ubuntu 14.04 to acceptance Issue Type: Task Assignee: Unassigned Created: 15/Feb/14 8:07 AM Fix Versions: 3.6.0 Priority: Normal Reporter: Kylo Ginsberg 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
Jira (PUP-1711) Add Ubuntu 14.04 packages
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-1711 Add Ubuntu 14.04 packages Issue Type: Task Assignee: Melissa Stone Components: RE Created: 15/Feb/14 8:06 AM Fix Versions: 3.6.0 Priority: Normal Reporter: Kylo Ginsberg Let's use this ticket for commit to the puppet repo. And RelEng can create a matching RE ticket if need be. Also, I assigned this to Melissa Stone because we were talking about it the other day, but of course reassign if that makes sense Add Comment
Jira (PUP-1711) Add Ubuntu 14.04 packages
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1711 Add Ubuntu 14.04 packages Change By: Kylo Ginsberg Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title mike jeski commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log I still see this issue on nodes running ubuntu 12.04 and Debian 6.0.8. fiddling with the rb.log does nothing. ext4 filesystems. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Adrien Thebo commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. Is this similar to what's described at http://docs.puppetlabs.com/hiera/1/release_notes.html#feature-hiera-sub-lookups-from-within-interpolation-tokens ? Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... 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
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Trevor Vaughan commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. It appears to be exactly http://projects.puppetlabs.com/issues/23301. The sub-lookup link still references looking up only strings (as far as I can tell). You still can't look up hashes or arrays. Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (FACT-151) Structured data should be supported
Title: Message Title
Jason Antman commented on an issue
Re: Structured data should be supported
Why should this just be a hash? IMO, the expectation from most of us who use Facter mainly through Puppet, is that $::factname should be able to be any puppet data type - string, boolean, hash, array, etc.
Add Comment
Facter / FACT-151
Structured data should be supported
Facter currently only supports a flat result list, and it should instead support structured data - basically, a hash of hashes and arrays. This should probably be able to be represented in two ways - either a hash of hashes/arrays, or namespaces. That is, this: pre {:top = {:middle = {:bottom = value}}} /pre Could also be represented as: ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Nick Walker commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log mike jeski You said you tried fiddling with rb.log. Have you tried applying the change described in this PR? https://github.com/jpartlow/puppet/commit/1004eaea5cd5fcadcd94709c5a4d314e3f297cef Also what version of puppet are you running? The PR above was merged in Puppet 3.4.2. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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 (PUP-1713) removing nagios_* resource from manifest doesn't remove from resulting file
Title: Message Title
Erik M Jacobs created an issue
Puppet / PUP-1713
removing nagios_* resource from manifest doesn't remove from resulting file
Issue Type:
Bug
Affects Versions:
3.3.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
15/Feb/14 2:31 PM
Environment:
CentOS 2.6.32-431.el6.x86_64 Puppet 3.3.2-1.el6 EPEL
Priority:
Normal
Reporter:
Erik M Jacobs
If you declare a nagios_service resource, it is created in the resulting file. Ex:
nagios_service { 'Load':
use = 'local-service',
host_name = 'server',
service_description = 'Load',
check_command = 'check_nrpe!check_load',
contact_groups = 'admin',
target = '/etc/nagios/conf.d/nagios_service.cfg',
}
However, if you then remove this resource declaration from a manifest and do the puppet run again, this service is not removed.
Jira (PUP-1713) removing nagios_* resource from manifest doesn't remove from resulting file
Title: Message Title
Daniele Sluijters commented on an issue
Re: removing nagios_* resource from manifest doesn't remove from resulting file
This is true with all Puppet resources. If a resource is not in a manifest it means it isn't managed, not that it should be removed. Can you imagine what would happen to a system the first time you start Puppet if that would be the case, it would wipe the system clean. There's no option to the nagios types to fully manage the file, it will only manage the entries it knows about and leave the others alone.
If you want this to happen you need to set that block to ensure = absent, and have it run once. The purging of (exported) Nagios resource has been broken since the dawn of time but perhaps https://ask.puppetlabs.com/question/567/remove-old-nagios-services-hosts/ can help you further.
Add Comment
Puppet / PUP-1713
removing nagios_* resource from manifest doesn't remove from resulting file
If you declare a nagios_service resource, it is created in the resulting file. Ex: {code} nagios_service { 'Load': use = 'local-service', host_name = 'server', service_description = 'Load', check_command = 'check_nrpe!check_load', contact_groups = 'admin', target = '/etc/nagios/conf.d/nagios_service.cfg', } {co...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1713) removing nagios_* resource from manifest doesn't remove from resulting file
Title: Message Title Daniele Sluijters assigned an issue to Daniele Sluijters Puppet / PUP-1713 removing nagios_* resource from manifest doesn't remove from resulting file Change By: Daniele Sluijters Assignee: KyloGinsberg DanieleSluijters 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 (PDB-462) HTTP/2.0
Title: Message Title Daniele Sluijters created an issue PuppetDB / PDB-462 HTTP/2.0 Issue Type: Improvement Assignee: Unassigned Created: 15/Feb/14 3:18 PM Labels: puppetdb Priority: Normal Reporter: Daniele Sluijters As a spec for HTTP/2.0 is starting to slowly emerge and people are starting to experiment with it I think it's a good time to bring up this issue. I'm sure some investigation will have to be done and the libraries that are used will have to be updated to support HTTP/2.0. Even though it's still early days it there should at least be an issue about it. Add Comment
Jira (PDB-462) HTTP/2.0
Title: Message Title Daniele Sluijters commented on an issue Re: HTTP/2.0 This could also be interesting wrt PDB-29. Add Comment PuppetDB / PDB-462 HTTP/2.0 As a spec for HTTP/2.0 is starting to slowly emerge and people are starting to experiment with it I think it's a good time to bring up this issue. I'm sure some investigation will have to be done and the libraries that are used will have to be updated to support HTTP/2.0. Even though it's still early days it there should at least be an issue about it. 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 (PUP-778) PR (2086): Initial refactoring of yumrepo. - apenney
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-778 PR (2086): Initial refactoring of yumrepo. - apenney Change By: Kylo Ginsberg Assignee: AdrienThebo 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 (PUP-1481) Incorrect PID on first start after installation on Ubuntu
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1481 Incorrect PID on first start after installation on Ubuntu Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1121) Node regex beginning with dash results in invalid tag
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1121 Node regex beginning with dash results in invalid tag Change By: Adrien Thebo Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1465) PR (2273): (doc) Updating README.md, LICENSE - highb
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-1465 PR (2273): (doc) Updating README.md, LICENSE - highb Change By: Adrien Thebo Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Adrien Thebo commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. I'm still not sure I understand what you need here, do you just need to be able to do array concatenation/hash merging of top level values? Could you provide a bit more detail on how you would like to see different levels of the hierarchy merged? Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-515) Consider validating file path for named autoloaded elements
Title: Message Title Henrik Lindberg commented on an issue Re: Consider validating file path for named autoloaded elements This is https://tickets.puppetlabs.com/browse/PUP-1434 (the #5041 from redmine migrated). Suggest keeping PUP-1434 about 3x, and this issue (PUP-515) about Puppet 4 and new loaders. Add Comment Puppet / PUP-515 Consider validating file path for named autoloaded elements Currently, named elements can be created in a container that it is logically not a part of. Redmine #5041, #5044, and #5043 discusses various ways. None of the suggestions are perfect, and some are more aggressive with backwards compatibility issues. Options: * Generic first * load from most generic to more specific * Most specific file first... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more
Jira (PUP-519) node inside a class (and several other places) is illegal
Title: Message Title Henrik Lindberg commented on an issue Re: node inside a class (and several other places) is illegal Yes, this is still relevant - don't think this is validated. While there is now a new validator I don't think it checks this. Add Comment Puppet / PUP-519 node inside a class (and several other places) is illegal It is illegal to place a node _expression_ inside of a class, define. Is it also illegal to place it in conditional logic? 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 (PUP-496) Create performance lab
Title: Message Title Henrik Lindberg commented on an issue Re: Create performance lab No, the work on benchmarking did create a performance lab. While there are additional things we want to do, these should be separate tasks. Maybe create an epic for performance lab (kind of disk, dedicated hardware, stable / comparable results, etc.). Was the work on creating benchmarks covered by other tickets? Add Comment Puppet / PUP-496 Create performance lab We will need to do extensive performance work and need a good toolchain and ways to measure and analyze performance. This task is about gathering requirements, exploring solutions, and coming up with a recommendation, then implementing it. This will require creating additional tasks. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1714) Freebsd Package Manager rewrite (as fbsd)
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1714
Freebsd Package Manager rewrite (as fbsd)
Issue Type:
New Feature
Assignee:
Unassigned
Created:
15/Feb/14 10:42 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
A re-write of the Freebsd package manager (freebsd.rb) to fix a couple of things (package file source selection, etc) and support upgrading of packages - all using only base OS tools. This manager does not compile ports, and only works on .tbz package files.
Features: installable, uninstallable, upgradeable.
Notes:
:name - must be the port origin, not the package (short) name.
:source - must be the specific local file or URL to path
Configuration example:
package { shells/bash: provider = fbsd, alias = bash, source = /path/to/local/package.tbz ensure = latest, }
Jira (PUP-1715) Freebsd Package Manager rewrite (as fbsd)
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1715
Freebsd Package Manager rewrite (as fbsd)
Issue Type:
New Feature
Assignee:
Unassigned
Created:
15/Feb/14 10:42 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
A re-write of the Freebsd package manager (freebsd.rb) to fix a couple of things (package file source selection, etc) and support upgrading of packages - all using only base OS tools. This manager does not compile ports, and only works on .tbz package files.
Features: installable, uninstallable, upgradeable.
Notes:
:name - must be the port origin, not the package (short) name.
:source - must be the specific local file or URL to path
Configuration example:
package { shells/bash: provider = fbsd, alias = bash, source = /path/to/local/package.tbz ensure = latest, }
Jira (PUP-1716) Package management broken for FreeBSD 10
Title: Message Title Jo Rhett created an issue Puppet / PUP-1716 Package management broken for FreeBSD 10 Issue Type: Bug Assignee: Unassigned Created: 15/Feb/14 11:10 PM Priority: Normal Reporter: Jo Rhett Package management is broken for FreeBSD 10 which does not use the pkg_add, pkg_info, etc tools. There is already a module on the forge which implements the new provider: https://github.com/xaque208/puppet-pkgng/blob/master/lib/puppet/provider/package/pkgng.rb or Puppet Forge zleslie/pkgng This system can also be used with FreeBSD 9 and in my testing has proved to be superior to the current package tools. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1717) Puppet Dashboard delayed job worker infinitely retrying due to MySQL error
Title: Message Title Peter Ryszkiewicz created an issue Puppet / PUP-1717 Puppet Dashboard delayed job worker infinitely retrying due to MySQL error Issue Type: Bug Affects Versions: 3.3.2 Assignee: Unassigned Created: 15/Feb/14 11:46 PM Environment: production Priority: Normal Reporter: Peter Ryszkiewicz The Puppet Dashboard workers are getting stuck on a job due to a MySQL error. This is causing the worker to infinitely keep retrying to add the yaml info to the MySQL db. The job includes trying to add a very long (300KB) entry to the MySQL db. My setup followed the one at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html so the dashboard talks to a MySQL db. The yaml report (at /usr/share/puppet-dashboard/spool) contains a entry that contains a very long message, roughly 300KB worth of text (this text is the content of a text file that Puppet distributes to my nodes). I've attached a stripped down yaml report. The worker also generates logs at /usr/share/puppet-dashboard/log, and I've included a small sample. The delayed job worker keeps trying to add this yaml report to the database so often, the delayed_job logs generate hundreds of MB worth of text every day. The reason why it generates so much log data is because every log line includes the content of 300KB of text. Multiplying this 300KB by 2 worker attempts per
Jira (PUP-1717) Puppet Dashboard delayed job worker infinitely retrying due to MySQL error
Title: Message Title Peter Ryszkiewicz updated an issue Puppet / PUP-1717 Puppet Dashboard delayed job worker infinitely retrying due to MySQL error Attaching yaml and log files Change By: Peter Ryszkiewicz Attachment: report.yaml Attachment: delayed_job.log 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 (PUP-1717) Puppet Dashboard delayed job worker infinitely retrying due to MySQL error
Title: Message Title Peter Ryszkiewicz updated an issue Puppet / PUP-1717 Puppet Dashboard delayed job worker infinitely retrying due to MySQL error Change By: Peter Ryszkiewicz ThePuppetDashboardworkersaregettingstuckonajobduetoaMySQLerror.ThisiscausingtheworkertoinfinitelykeepretryingtoaddtheyamlinfototheMySQLdb.Thejobincludestryingtoaddaverylong(300KB)entrytotheMySQLdb.Mysetupfollowedtheoneathttp://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.htmlsothedashboardtalkstoaMySQLdb.Theyamlreport(at/usr/share/puppet-dashboard/spool)contains a an entrythatcontainsaverylongmessage,roughly300KBworthoftext(thistextisthecontentofatextfilethatPuppetdistributestomynodes).I'veattachedastrippeddownyamlreport.Theworkeralsogenerateslogsat/usr/share/puppet-dashboard/log,andI'veincludedasmallsample.Thedelayedjobworkerkeepstryingtoaddthisyamlreporttothedatabasesooften,thedelayed_joblogsgeneratehundredsofMBworthoftexteveryday.Thereasonwhyitgeneratessomuchlogdataisbecauseeveryloglineincludesthecontentof300KBoftext.Multiplyingthis300KBby2workerattemptsperminuteby1440minutesperdayequalsroughly864MBperdayoflogs.Thisisveryexcessiveforasingleworkerproblem.Granted,thelogsgetrotatedandcompressed,buttheystillneedtogetcleanedupunnecessarily.ThePuppetDashboardalwayshas1pendingtaskandnevergetsclearedup.I'mguessingitwillgoawayonceIdeletetheoffendingyamlfile.Here'sasnippetfromthedelayed_job.log:Report.create_from_yaml_filefailedwithActiveRecord::StatementInvalid:Mysql::Error:Datatoolongforcolumn'details'atrow1:INSERTINTO`delayed_job_failures`(`read`,`updated_at`,`created_at`,`summary`,`details`,`backtrace`)VALUES(...)Allattachmentshadsensitivedataremoved.Imention300KBinthesensitiveareas. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
