Jira (PUP-8042) Failed to apply catalog: [nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, [(provider=pip)]]
Title: Message Title Ryan Hall created an issue Puppet / PUP-8042 Failed to apply catalog: [nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, [(provider=pip)]] Issue Type: Bug Affects Versions: PUP 4.7.0 Assignee: Unassigned Created: 2017/10/10 10:20 PM Environment: Amazon Linux Priority: Major Reporter: Ryan Hall Attempting to install pip packages with the puppet resource pip. This is displayed in the the UI: Failed to apply catalog: [nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, nil, [(provider=pip)]] I read somewhere that if you use easy_install to install pip instead of installing the python-pip package it resolves the error, which i have to do with an exec (prefer not to use)... It did, however, the pip packages then will not install. Unless I re-install python-pip. Which brings the error back. I also have to update pip after it is installed??? Why do I have to manage the packages that are required for the puppet provider pip to work? Shouldn't this already be handled by puppet within the provider itself??? It also is frustrating that you do not support the environment variable like you do in yum and other providers.
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title Maggie Dreyer commented on PUP-8040 Re: Puppet does not initialize I18N locale per thread So to be clear, the logic around setting the locale in gettext/config.rb is designed to change the locale to something other than English (the default) only if FastGettext's locale is currently English AND we have a translation set that matches the system locale. What do you mean when you say "manually set to ja"? Manually setting the system locale, or updating the locale in Ruby code? Michael Smith that makes sense to me, the initialize function is hopefully setting the locale to ja when it does the work for Puppet, and then not doing anything around that code thereafter. 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-3630) Configurable facts blacklist
Title: Message Title Charlie Sharpsteen commented on PDB-3630 Re: Configurable facts blacklist +1 to what Nick said above. 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-3630) Configurable facts blacklist
Title: Message Title Nick Walker commented on PDB-3630 Re: Configurable facts blacklist Reopening this issue, I think we should prioritize it in the near-term. We're continuing to see customers with large facts run into performance issues and often they do not want to blacklist the fact because they use it in puppet code, however, they don't ever view it in the PE console or via PuppetDB in anyway. Having a fact blacklist for PuppetDB is not duplicating functionality with the facter blacklist since blocking things out of PuppetDB effectively has no effect on puppet itself where as blocking facts from facter does affect puppet. The facter blacklist as discussed above requires block groups of facts which PuppetDB should allow blocking any fact by name. There are differences and implementing a PuppetDB fact blacklist is worthwhile. 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 (FACT-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Branan Riley commented on FACT-1761 Re: Infiniband's mac (hardware) address not provided It's... not, unfortunately. It turns out the APIs we use can't return a MAC longer than 8 characters. I'll have to spend some time figuring out how `ip link` gets that information, or just give up and shell out to it. Either of those is going to be more than a single quick change to Facter's assumptions about what a MAC looks like, though 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 Michael Smith commented on PUP-8040 Re: Puppet does not initialize I18N locale per thread Ok, while testing this I'm unable to get translations actually working with environment_timeout=unlimited. Turning it to 0 lets me see translations the 1st compilation, then they break again. It doesn't seem to be the GettextConfig.initialize that's causing it either, as this always sees FastGettext.locale as ja. 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-3699) allow PQL queries to be stored and executed by name
Title: Message Title
R.I.Pienaar created an issue
PuppetDB / PDB-3699
allow PQL queries to be stored and executed by name
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/10 1:48 PM
Priority:
Normal
Reporter:
R.I.Pienaar
PQL queries can be pretty awkward to type even though they are a LOT better than the old queries. A typo can wreak havok and they are hard to debug, it would be great if we could store queries by name which would facilitate reuse and sharing between team members - or just error reduction.
So if I could store
inventory[certname] { facts.osfamily = "RedHat" and
facts.datacentre = "PDX" and
resources { type = "Package" and
Jira (FACT-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Radosław Piliszek commented on FACT-1761 Re: Infiniband's mac (hardware) address not provided Any progress? This sounded easily fixable. 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-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title
Thomas Kishel created an issue
Puppet / PUP-8041
Replace FACTER_url with --target for puppet resource with devices
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2017/10/10 12:22 PM
Priority:
Minor
Reporter:
Thomas Kishel
Since 2012, we've used FACTER_url as a workaround for puppet resource:
A limitation to watch out for in the current Puppet release is that 'puppet apply' and 'puppet resource' cannot modify network resources. However, we implemented a feature to allow puppet resource to query a F5 device. (For authors of types/providers, making changes to resources aren’t supported until apply_to_device in resources type are handled differently by puppet apply/resource commands). For now we use url facts to establish connectivity to specific F5 devices.
https://puppet.com/blog/managing-f5-big-ip-network-devices-puppet
Using FACTER_url is insecure, as it places authentication credentials either in history or in the environment. It's also ugly.
If we implement --target in puppet resource as we've done in puppet device we can lookup the target device's url and internally set {{Facter(:url). This would not require changes to existing device modules.
If we implement this as a device(name) method in Puppet::Util::NetworkDevice::Config, it would allow device tasks to use device(name) to target devices.
Jira (PUP-6854) OSX: Warning output when using puppet resource service
Title: Message Title Moses Mendoza commented on PUP-6854 Re: OSX: Warning output when using puppet resource service merged to master at https://github.com/puppetlabs/puppet/commit/222c118f2971db3e674f36f385db49e5967087f7 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-8025) `puppet module install` does not correctly install locale files
Title: Message Title Michael Smith updated an issue Puppet / PUP-8025 `puppet module install` does not correctly install locale files Change By: Michael Smith Labels: i18n 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-8026) Module code translation should be supported with puppet agent runs
Title: Message Title Michael Smith updated an issue Puppet / PUP-8026 Module code translation should be supported with puppet agent runs Change By: Michael Smith Labels: i18n 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-8024) Delay loading module translations until 'translate' is used for that module
Title: Message Title Michael Smith updated an issue Puppet / PUP-8024 Delay loading module translations until 'translate' is used for that module Change By: Michael Smith Labels: i18n 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 Michael Smith updated an issue Puppet / PUP-8040 Puppet does not initialize I18N locale per thread Change By: Michael Smith Fix Version/s: PUP 5.3.3 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 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 Michael Smith commented on PUP-8040 Re: Puppet does not initialize I18N locale per thread What system are you running on? I tend to test with CentOS 7. 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 Michael Smith 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. 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 Michael Smith commented on PUP-8040 Re: Puppet does not initialize I18N locale per thread Also, I think this should be considered in conjunction with PUP-8024, as it has significant implications for the code pointed to here. 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 Michael Smith 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. 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 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-8040) I18N not working for modules in Master/Agent environments
Title: Message Title Susan McNerney updated an issue Puppet / PUP-8040 I18N not working for modules in Master/Agent environments Change By: Susan McNerney Labels: i18n 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-3698) Build up of orphaned rows in edges and facts tables
Title: Message Title Matt Dainty commented on PDB-3698 Re: Build up of orphaned rows in edges and facts tables Thanks for the response. I'll have to try and sort out getting the servers and agents upgraded to 5.x first before I can try the newer PDB out. 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) I18N not working for modules in Master/Agent environments
Title: Message Title Geoff Nichols commented on PUP-8040 Re: I18N not working for modules in Master/Agent environments /cc Craig Gomes and Kenn Hussey 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) I18N not working for modules in Master/Agent environments
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8040 I18N not working for modules in Master/Agent environments Change By: Geoff Nichols Team: Platform Core 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) I18N not working for modules in Master/Agent environments
Title: Message Title Geoff Nichols moved an issue Puppet / PUP-8040 I18N not working for modules in Master/Agent environments Change By: Geoff Nichols Key: PA PUP - 1616 8040 Project: Puppet Agent 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-3698) Build up of orphaned rows in edges and facts tables
Title: Message Title Russell Mull commented on PDB-3698 Re: Build up of orphaned rows in edges and facts tables The edges leak issue is PDB-3515 , which is fixed in newer versions. For factsets: this code has changed substatially since this version. I recommend upgrading to the latest PDB and checking things out then. In the meantime, it's totally safe to delete these rows manually. 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-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8020 Add data types Nodes and Node to puppet for tasks/plans Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-8039) Puppet 4.10.x: Only warn once when gettext cannot be found
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8039 Puppet 4.10.x: Only warn once when gettext cannot be found Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual 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-8038) rubocop-i18n GetText/DecorateString is broken
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8038 rubocop-i18n GetText/DecorateString is broken Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action 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-3698) Build up of orphaned rows in edges and facts tables
Title: Message Title Matt Dainty created an issue PuppetDB / PDB-3698 Build up of orphaned rows in edges and facts tables Issue Type: Bug Affects Versions: PDB 4.4.0 Assignee: Unassigned Components: PuppetDB Created: 2017/10/10 6:49 AM Priority: Normal Reporter: Matt Dainty I've noticed in the PuppetDB PostgreSQL database that there seems to be a build up of what seem to be orphaned rows in both the edges and facts tables. For example: puppetdb=# SELECT COUNT(*) FROM edges WHERE certname NOT IN (SELECT certname FROM certnames); count
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-8020
Add data types Nodes and Node to puppet for tasks/plans
Change By:
Thomas Hallgren
Comment:
I can think of several solutions to the "multiple files" problem that doesn't involve using directories under the tasks folder.1. Use a zip archive. It brings other advantages too in that it is easier and more compact to transport, checksum, etc.2. Put additional files under the "files" directory. This already works with the Puppet {{file_upload}} and {{run_script}} functions. They resolve relative names in the form _/_ from as files residing in _/files/_.3. Let each file use a different extension. If needed, add a number, e.g.{noformat}init.shinit.1.csvinit.2.csv...{noformat}
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-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans I can think of several solutions to the "multiple files" problem that doesn't involve using directories under the tasks folder. 1. Use a zip archive. It brings other advantages too in that it is easier and more compact to transport, checksum, etc. 2. Put additional files under the "files" directory. This already works with the Puppet file_upload and run_script functions. They resolve relative names in the form / from as files residing in /files/. 3. Let each file use a different extension. If needed, add a number, e.g. init.sh init.1.csv init.2.csv ... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6702) Windows service in Paused state cannot be managed
Title: Message Title Adam Buxton commented on PUP-6702 Re: Windows service in Paused state cannot be managed Nathanael Cole I sooke to a customer yesterday who reckognised it is an issue with having anlternative version of Libraries PCP relies upon in path. It dawned on me that the pxp-agent uses openssl and we also have windows modules which use openssl libraries. Once I removed these from PATH the pxp-agent ran up ok. Namely, the libeay32.dll, libss32.dll and ssleay32.dll 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
