Jira (PDOC-187) Strings 2.0.0 improvements blog post
Title: Message Title Hunter (Hunner) Haugen commented on PDOC-187 Re: Strings 2.0.0 improvements blog post Bah, wrong ticket Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-210) Add puppet-strings docs to puppetlabs-mysql as a POC
Title: Message Title Hunter (Hunner) Haugen assigned an issue to Hunter (Hunner) Haugen Puppet Strings / PDOC-210 Add puppet-strings docs to puppetlabs-mysql as a POC Change By: Hunter (Hunner) Haugen Assignee: Hunter (Hunner) Haugen Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7973) gem package provider doesn't match exact on windows
Title: Message Title Hunter (Hunner) Haugen commented on PUP-7973 Re: gem package provider doesn't match exact on windows Eric Delaney Thanks for catching this and writing the notes! That sounds just fine. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title Hunter (Hunner) Haugen commented on PUP-8040 Re: Puppet does not initialize I18N locale per thread I'm not sure I understand the need for negotiating locale on every module load. Can you provide more example of what happens, and how to reproduce a problem? My current understanding is that - if you include translations in modules that aren't part of Puppet - those translations will be used inconsistently based on what JRuby they're first loaded into. Printing FastGettext.locale during each compile when _() is called, it is initially set to en and when manually set to ja is reset to en each compile... or perhaps just each thread and I got a different thread each time. I'm not sure about that, but it was not initialized to ja for each sequential compile. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title Hunter (Hunner) Haugen commented on PUP-8040 Re: Puppet does not initialize I18N locale per thread localectl set-locale LANG=ja_JP.UTF-8 will work with puppetserver if you restart puppetserver. I've done this many times. From pry'ing in a puppetserver foreground and looking at ENV I did not see LANG in the environment. Secondly, it seems like LANGUAGE also needs to be in the environment variables for the locales to be loaded, but I didn't verify that fully. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title
Hunter (Hunner) Haugen updated an issue
Puppet / PUP-8040
Puppet does not initialize I18N locale per thread
Change By:
Hunter (Hunner) Haugen
The modules team have run into an issue with I18N in From a master/agent(s) set up. The crux few hours of investigation, the issue is that when modules are installed on the master pluginsync copies the modules over puppetserver appears to the agents - but pluginsync is not copying over the modules 'locales' directory containing the PO files so the translations are not available on the agent - meaning that on the agents all strings only appear in English regardless of which locale is selected.We believe the fix required is for pluginsync to be updated so that when it is copying modules over to the agents it will include the 'locales' directory and its contents.See below for a more detailed description track translation repositories from Hunter:- The puppetserver ignores all environment variables. /etc/puppetlabs/puppetserver/conf.d/pe-puppet-server.conf needs `jruby-puppet: environment-vars: { "LANG": "ja_JP.UTF-8" compile to compile , but either " LANGUAGE forgets " : "ja_JP.UTF-8" }` or other locales for any translation to happen in about the puppetserver.- `localectl set- locale LANG=ja_JP.UTF-8` does not affect the puppetserver (see above) after each compile , but does affect or must have the puppet-agent because the agent reads environment variables apparently. (This command creates /etc/ locale initialized in EVERY thread individually . conf iirc.) The bug of server-side locales being reset every compile Some technical details :- {{ Puppet::GettextConfig.initialize_i18n }} checks {{ translation_repositories }} before initializing {{FastGettext. locale }} , and thus doesn't set only initializes the locale in each thread once ever (see https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/module.rb#L427-L446) . - {{ FastGettext.translation_repositories }} are global for a class variable. According to the puppetserver but FastGettext readme, {{FastGettext .locale is }} must be initialized once per thread : https://github.com/grosser/fast_gettext#3 - local (according to the FastGettext readme) choose-text-domain-and-locale-for-translation - The locale should be negotiated at every module load, contrary to what this says: https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/gettext/config.rb#L83-L84 (watch out for performance implications) - agent-side _() calls (inside types & providers, for example) are executed on the agent node, but the agent node has no access to the .po files as those translation repositories should only exist on the master. We will have needed to create or reuse a master/agent file distribution mechanism (pluginsync sync's lib/ and tasks sync tasks ad-hoc, but neither sounds great for i18n be loaded once . po files per module) or bundle i18n data in the catalog (nightmare for users bandwidth) or have the master respond to i18n indirector calls?
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title Hunter (Hunner) Haugen updated an issue Puppet / PUP-8040 Puppet does not initialize I18N locale per thread Change By: Hunter (Hunner) Haugen Summary: I18N Puppet does not working for modules in Master/Agent environments initialize I18N locale per thread Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7973) gem package provider doesn't match exact on windows
Title: Message Title Hunter (Hunner) Haugen created an issue Puppet / PUP-7973 gem package provider doesn't match exact on windows Issue Type: Bug Affects Versions: PUP 5.2.0 Assignee: Unassigned Created: 2017/09/21 11:40 AM Environment: windows 2008r2, puppet-agent 5.2.0 Priority: Normal Reporter: Hunter (Hunner) Haugen When calling the gemlist and gemsplit commands (https://github.com/puppetlabs/puppet/blob/5.2.0/lib/puppet/provider/package/gem.rb#L22-L71) the provider attempts an exact match with ^ and $ however on windows only the $ is honored: C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin>gem.bat list --remote ^pry$
Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Hunter (Hunner) Haugen commented on PUP-3483 Re: Systemd provider doesn't scan for changed units Using time it appears that checking whether a unit file needs to be reloaded via systemctl show rsyslog --property=NeedDaemonReload takes about 0.007 real and doing a systemctl daemon-reload takes 0.04 real. I did not see any mechanism for making systemd auto-daemon-reload as needed, so perhaps we should check NeedDaemonReload at the beginning of any status/restart/start/stop operation, but only once per ensure evaluation (since the unit should not otherwise change during a single transaction). I did not see any way to integrate the NeedDaemonReload check as part of systemctl list-unit-files that self.instances performs. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7797) Report format 6 logs do not indicate corrective changes
Title: Message Title Hunter (Hunner) Haugen commented on PUP-7797 Re: Report format 6 logs do not indicate corrective changes That's acceptable, and kind of expected. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7797) Report format 6 logs do not indicate corrective changes
Title: Message Title Hunter (Hunner) Haugen created an issue Puppet / PUP-7797 Report format 6 logs do not indicate corrective changes Issue Type: New Feature Assignee: Unassigned Created: 2017/07/21 3:21 PM Priority: Normal Reporter: Hunter (Hunner) Haugen I need to report-process all Puppet::Util::Log objects in a format 6 report (https://docs.puppet.com/puppet/4.9/format_report.html) and see no programmatic way to do so. Please add a corrective_change boolean to the log object. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-3745) Group membership should be a type of its own.
Title: Message Title Hunter (Hunner) Haugen commented on PUP-3745 Re: Group membership should be a type of its own. It looks like gpasswd supports setting/adding/removing users WRT groups, and the provider can enumerate a groups members. So pretty easy? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7738) "puppet module install" fails on Puppet 5.0.0
Title: Message Title Hunter (Hunner) Haugen commented on PUP-7738 Re: "puppet module install" fails on Puppet 5.0.0 In retrospect, to "vendor" something means to include a released codebase in your own codebase, but the codebase present in https://github.com/puppetlabs/puppet/tree/5.0.0/lib/puppet/vendor/semantic_puppet/lib/semantic_puppet is not a pre-existing codebase. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3587) puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x
Title: Message Title Hunter (Hunner) Haugen created an issue PuppetDB / PDB-3587 puppetlabs-puppetdb : doesn't work with puppetlabs-postgresql 5.x Issue Type: Improvement Assignee: Unassigned Created: 2017/06/22 10:09 AM Priority: Normal Reporter: Hunter (Hunner) Haugen Basic Info Module Version: Describe your issue in as much detail as possible... The puppetdb module currently pins on postgresql < 5.0.0, and now that 5.0.0 is out it is incompatible. https://github.com/puppetlabs/puppetlabs-puppetdb/blob/master/metadata.json#L81 Desired Behavior: Installing a 5.x series of postgresql with puppetdb works. Actual Behavior: David Hollinger can fill this in. Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Add Comment
Jira (PUP-3732) type validation should not run for `puppet resource`
Title: Message Title Hunter (Hunner) Haugen commented on PUP-3732 Re: type validation should not run for `puppet resource` Josh Cooper I see occurrences of this at least in the F5, netapp, and Azure modules, if you want code examples. Otherwise specific scenarios may not help as it's a "gotcha" any time I'm coding any global validate block (and especially having to make "required" parameters since there is no way to make required parameters for puppet types otherwise). Eg: validate do raise ArgumentError, "Passing value or othervalue is required" if ! self[:value] and ! self[:othervalue] end Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3745) Group membership should be a type of its own.
Title: Message Title Hunter (Hunner) Haugen commented on PUP-3745 Re: Group membership should be a type of its own. As mentioned, this is not solved so reopening. If we are not going to provide such a mechanism, then feel free to re-close won'tfix with a comment. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3542) PuppetDB : Don't manage Postgresql
Title: Message Title Hunter (Hunner) Haugen moved an issue PuppetDB / PDB-3542 PuppetDB : Don't manage Postgresql Change By: Hunter (Hunner) Haugen Component/s: puppetdb Component/s: Module Key: MODULES PDB - 4811 3542 Project: Forge Modules PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3745) Group membership should be a type of its own.
Title: Message Title Hunter (Hunner) Haugen commented on PUP-3745 Re: Group membership should be a type of its own. Josh Cooper The group type does have a :manages_members feature https://github.com/puppetlabs/puppet/blob/4.10.1/lib/puppet/type/group.rb#L16 but the groupadd provider does not support it: https://github.com/puppetlabs/puppet/blob/4.10.1/lib/puppet/provider/group/groupadd.rb#L11 To approach it from the user resource side, it can manage group membership but also defaults to managing the ensure of the user: https://github.com/puppetlabs/puppet/blob/4.10.1/lib/puppet/type/user.rb#L79-L87 Assuming ensure => present on resource management is common with respect to puppet types as ensurable does default to this when properties are managed: https://github.com/puppetlabs/puppet/blob/4.10.1/lib/puppet/property/ensure.rb#L94-L103 So there is no way to assign users to groups without also managing the ensure of a user with the groupadd provider. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Hunter (Hunner) Haugen commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax I have not read the entire conversation yet (longthread is long) but generally agree with Sean Millichamp's major points. I also want to offer a few technical details. <||> collectors are often used to add resource dependencies when we are unsure of any/all of the declared resources. Similar to the autorequire et al in native types. The biggest example that comes to mind is https://github.com/puppetlabs/puppetlabs-tomcat/blob/1.7.0/manifests/instance/dependencies.pp as there can be an arbitrary number of tomcat instances with widely varying paths and many (or none) defined types using the various instances. Building out such a tree was not possible without collecting on a commonly-shared quality (that of the catalina_base or catalina_home values). From a module dev perspective, we cannot depend on the existence of the puppetdb service. We also cannot depend on the ability to export resources, though may offer solutions that can take advantage of such (eg https://github.com/puppetlabs/puppetlabs-haproxy/blob/1.5.0/manifests/backend.pp#L66). I don't think module devs care about virtual resources; they are too entangled with the collector realization and spaghetti-code anti-patterns that we just avoid them. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7506) Puppet-device looks for the transport lib in the proxy's environment, not the device's
Title: Message Title Hunter (Hunner) Haugen updated an issue Puppet / PUP-7506 Puppet-device looks for the transport lib in the proxy's environment, not the device's Change By: Hunter (Hunner) Haugen Summary: Puppet-device can't find looks for the transport lib in the device proxy 's environment , not the device's Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7506) Puppet-device can't find the transport lib in the device's environment
Title: Message Title Hunter (Hunner) Haugen created an issue Puppet / PUP-7506 Puppet-device can't find the transport lib in the device's environment Issue Type: Bug Assignee: Unassigned Created: 2017/05/09 12:37 PM Priority: Normal Reporter: Hunter (Hunner) Haugen Basic Info Puppet Version: 4.10.1 and PE 2016.4.4-rc0-137-g635e6e2 OS Name/Version: centos 7 puppetmaster centos 7 device proxy Describe your issue in as much detail as possible... Desired Behavior: Install a device module like puppetlabs-f5 to a single environment (say, f5prod) Assign a device to the f5prod environment Run puppet device -d for the f5 nodes works Actual Behavior: If a puppet device transport is supplied by a module, and the module exists in the *device's* puppet environment and not in the *proxy's* environment, then the following stacktrace results when running puppet device -d --trace: Error: Could not run: cannot load such
Jira (PUP-7440) Pattern can't allow empty string but block newlines
Title: Message Title Hunter (Hunner) Haugen commented on PUP-7440 Re: Pattern can't allow empty string but block newlines Oops hah, thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
