Jira (FACT-1784) hypervisors fact reports false positive for LPAR/WPAR on KVM power8
Title: Message Title Casey Williams commented on FACT-1784 Re: hypervisors fact reports false positive for LPAR/WPAR on KVM power8 PR is here: https://github.com/puppetlabs/libwhereami/pull/31 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-1785) Add device-tree data source to libwhereami
Title: Message Title Casey Williams created an issue Facter / FACT-1785 Add device-tree data source to libwhereami Issue Type: Task Assignee: Unassigned Created: 2017/10/23 5:39 PM Fix Versions: whereami 0.2.0 Priority: Normal Reporter: Casey Williams arm and power architectures store some useful hypervisor information in /proc/device-tree which we can't get from DMI on those platforms. It'd be nice to have a device-tree data source to rely on in these cases (virt-what already does this). Add Comment
Jira (FACT-1784) hypervisors fact reports false positive for LPAR/WPAR on KVM power8
Title: Message Title Casey Williams created an issue Facter / FACT-1784 hypervisors fact reports false positive for LPAR/WPAR on KVM power8 Issue Type: Bug Assignee: Casey Williams Created: 2017/10/23 5:30 PM Fix Versions: whereami 0.2.0 Priority: Normal Reporter: Casey Williams While testing some puppet-agent builds, I noticed that the hypervisors fact on a power8 rhel7 machine reported that the agent was running inside an LPAR - this is because libwhereami doesn't adequately initialize its LPAR source data - will be an easy fix. Add Comment
Jira (BOLT-192) Bolt is not compatible with net-ssh 4.0 or 4.1
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-192 Bolt is not compatible with net-ssh 4.0 or 4.1 Change By: Josh Cooper Fix Version/s: BOLT 0.7.0 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-8083) NTFS reparse points return invalid path data strings for mount points (like those in a DFS share)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8083 NTFS reparse points return invalid path data strings for mount points (like those in a DFS share) Change By: Ethan Brown Summary: DFS NTFS reparse points return invalid path data strings for mount points (like those in a DFS share) 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-8083) DFS reparse points return invalid path data strings
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-8083 DFS reparse points return invalid path data strings Change By: Ethan Brown Assignee: Ethan Brown 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-8083) DFS reparse points return invalid path data strings
Title: Message Title
Ethan Brown created an issue
Puppet / PUP-8083
DFS reparse points return invalid path data strings
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/23 4:43 PM
Priority:
Normal
Reporter:
Ethan Brown
While investigating MODULES-4934, it was realized that NTFS reparse points inside of DFS mounts were using an inappropriate data structure.
This would result in Puppet::Util::Windows::File.resolve_symlink returning a path string missing the first 4 bytes (and reading an extra 4 bytes of junk data off the end of the buffer).
In short, DFS shares with reparse points never work in Puppet properly. A simple repro scenario is to use a file resource in Puppet to recursively copy from a DFS path (that contains the default hidden reparse point to the host drives C:Volume Information) like:
file { 'c:/Share1-test':
ensure => directory,
recurse => true,
Jira (BOLT-146) Configure what interpreter/shell to use
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-146 Configure what interpreter/shell to use Change By: Josh Cooper There are a few related stories here but for now lets group them together- To override the shebang on a task written by someone else- To configure interpreters for windows (ruby, puppet, powershell, python, etc) - To use set a shell for a task(ie csh for the junos tasks) - To configure windows shells (cmd vs powershell) 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-3732) (maint) pushd before uber_building
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3732 (maint) pushd before uber_building Issue Type: Bug Assignee: Unassigned Created: 2017/10/23 2:43 PM Priority: Normal Reporter: gepetto-bot 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
Jira (PDB-3731) (maint) pushd before uber_building
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3731 (maint) pushd before uber_building Issue Type: Bug Assignee: Unassigned Created: 2017/10/23 2:43 PM Priority: Normal Reporter: gepetto-bot 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
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
From a few hours of investigation, the puppetserver appears to track translation repositories from compile to compile, but either "forgets" about the locale after each compile, or must have the locale initialized in EVERY thread individually.Some technical details:- {{Puppet::GettextConfig.initialize_i18n}} checks {{translation_repositories}} before initializing {{FastGettext.locale}}, and thus only initializes the locale once ever (see https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/module.rb#L427-L446).- {{FastGettext.translation_repositories}} are a class variable. According to the FastGettext readme, {{FastGettext.locale}} must be initialized once per thread: https://github.com/grosser/fast_gettext#3-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) but the translation repositories should only needed to be loaded once.We are going to explore refactoring the gettext initialization code to skip the logic around {{available_locales}} and {{FastGettext.locale}} in favor of just setting {{FastGettext.default_locale}} to the system locale directly, since {{default_locale}} is not thread local, unlike {{FastGettext.locale}}. That library should already handle the fallback cases from this configuration (though we will be writing tests to verify this, see PUP-8080). In order to avoid breaking other users of GettextSetup, we will likely be implementing most of this directly in Puppet as gettext utils, and drop our runtime dependency on GettextSetup.It looks like we might run into a similar issue when we start trying to use more text domains (see PUP-8013 and https://github.com/grosser/fast_gettext/blob/master/lib/fast_gettext/storage.rb#L54) as the current text domain also appears to be a thread-local variable. Currently we're avoiding issues here by only using one text domain which is both set as {{FastGettext.text_domain}} and {{FastGettext.default_text_domain}}, the latter of which is not thread local.Reproduction steps in a basic PE 2017.3.1 install - {{ localectl set-locale LANG=ja_JP.UTF-8 }} - add ` {{ fail('trigger failure') ` }} to {{node default}} section of {{ /etc/puppetlabs/code/environments/production/manifests/site.pp }} - set {{ disable_i18n=false }} in {{/etc/puppetlabs/ puppet /puppet .conf }} - {{ systemctl restart pe-puppetserver }} - {{ puppet agent -t --noop }} (several times)Expect to see{quote}Error: リモートサーバからカタログを取得できませんでした Could not retrieve catalog from remote server : SERVERのエラー500 Error 500 on SERVER : サーバエラー: Evaluation Error: a Function Callの検証中にエラーが生じました。trigger failure at /etc/puppetlabs/code/environments/production/manifests/site.pp:31:3 on node a2kqzra8n7avi2i hwcijw3gfrqxsiw .delivery.puppetlabs.net{quote}Will mostly see{quote}Error: リモートサーバからカタログを取得できませんでした Could not retrieve catalog from remote server : SERVERのエラー500 Error 500 on SERVER : Server Error: Evaluation Error: Error while evaluating a Function Call, trigger failure at
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
From a few hours of investigation, the puppetserver appears to track translation repositories from compile to compile, but either "forgets" about the locale after each compile, or must have the locale initialized in EVERY thread individually.Some technical details:- {{Puppet::GettextConfig.initialize_i18n}} checks {{translation_repositories}} before initializing {{FastGettext.locale}}, and thus only initializes the locale once ever (see https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/module.rb#L427-L446).- {{FastGettext.translation_repositories}} are a class variable. According to the FastGettext readme, {{FastGettext.locale}} must be initialized once per thread: https://github.com/grosser/fast_gettext#3-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) but the translation repositories should only needed to be loaded once.We are going to explore refactoring the gettext initialization code to skip the logic around {{available_locales}} and {{FastGettext.locale}} in favor of just setting {{FastGettext.default_locale}} to the system locale directly, since {{default_locale}} is not thread local, unlike {{FastGettext.locale}}. That library should already handle the fallback cases from this configuration (though we will be writing tests to verify this, see PUP-8080). In order to avoid breaking other users of GettextSetup, we will likely be implementing most of this directly in Puppet as gettext utils, and drop our runtime dependency on GettextSetup.It looks like we might run into a similar issue when we start trying to use more text domains (see PUP-8013 and https://github.com/grosser/fast_gettext/blob/master/lib/fast_gettext/storage.rb#L54) as the current text domain also appears to be a thread-local variable. Currently we're avoiding issues here by only using one text domain which is both set as {{FastGettext.text_domain}} and {{FastGettext.default_text_domain}}, the latter of which is not thread local. Reproduction steps- localectl set-locale LANG=ja_JP.UTF-8- add `fail('trigger failure')` to /etc/puppetlabs/code/environments/production/manifests/site.pp- set disable_i18n=false in puppet.conf- systemctl restart pe-puppetserver- puppet agent -t --noop (several times)Expect to see{quote}Error: リモートサーバからカタログを取得できませんでした: SERVERのエラー500 : サーバエラー: Evaluation Error: a Function Callの検証中にエラーが生じました。trigger failure at /etc/puppetlabs/code/environments/production/manifests/site.pp:31:3 on node a2kqzra8n7avi2i.delivery.puppetlabs.net{quote}Will mostly see{quote}Error: リモートサーバからカタログを取得できませんでした: SERVERのエラー500 : Server Error: Evaluation Error: Error while evaluating a Function Call, trigger failure at /etc/puppetlabs/code/environments/production/manifests/site.pp:31:3 on node a2kqzra8n7avi2i.delivery.puppetlabs.net{quote}
Jira (PDB-3683) Update ci-job-configs to build/test Debian 9 Stretch (amd64, i386)
Title: Message Title Michael Smith assigned an issue to Morgan Rhodes PuppetDB / PDB-3683 Update ci-job-configs to build/test Debian 9 Stretch (amd64, i386) Change By: Michael Smith Assignee: Michael Smith Morgan Rhodes 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 (BOLT-91) multi-task plans swallow output from all but the last task
Title: Message Title
Dan Wittenberg commented on BOLT-91
Re: multi-task plans swallow output from all but the last task
Haven't worked through all the use cases, just what I was testing with this morning. Structured always gets tricky, why having options for the output would be nice. For stderr/exit I was mostly commenting since it appears to return it now:
$ bolt plan run exec_task::command -k --modules . nodes=host1.example.com -u testuser -p ExecutionResult({'host1.example.com' => {'stdout' => "host1.example.com\n", 'stderr' => '', 'exit_code' => 0}
,
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 (BOLT-186) Improve discoverability of winrm:// usage
Title: Message Title Jenny Mahmoudi commented on BOLT-186 Re: Improve discoverability of winrm:// usage Josh Cooper That will help a lot! Will there be a way to set something in the config file so you don't have to specify --transport at all? 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 Susan McNerney commented on PUP-8039 Re: Puppet 4.10.x: Only warn once when gettext cannot be found This is resolved for 2016.4.9 in PE 22445 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott moved an issue Puppet / PUP-8082 Add warning to Puppet Module Tool when installing a deprecated module Change By: Jesse Scott Key: PF PUP - 1316 8082 Project: Puppet Forge [Internal] 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-5634) Application declaration "nodes" parameter should accept string representation of nodes, components
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-5634 Application declaration "nodes" parameter should accept string representation of nodes, components Change By: Michael Smith Assignee: Michael Smith 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 (BOLT-91) multi-task plans swallow output from all but the last task
Title: Message Title Alex Dreyer commented on BOLT-91 Re: multi-task plans swallow output from all but the last task What would happen when more than one task ran? What would happen for tasks that returned structured output? The task spec doesn't include stderr and exitcode as part of the default task execution and they may not always be available. I can see value in capturing them this way but I'm not sure if it makes sense as a default. 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-7308) classes do not honor refresh events when running with tags
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7308 classes do not honor refresh events when running with tags Change By: Maggie Dreyer Release Notes Summary: With this change, refresh events are now correctly propagated to all tagged resources when running with tags, and some confusing debug and warning messages have been eliminated. Release Notes: Bug Fix 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 (BOLT-91) multi-task plans swallow output from all but the last task
Title: Message Title Dan Wittenberg commented on BOLT-91 Re: multi-task plans swallow output from all but the last task That's what I was thinking, each node can have a section for stdout/stderr/exit code so if in debug mode you can correlate what happened on each node if you need those details. 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-7883) Make node_terminus=ldap working with jruby/puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7883 Make node_terminus=ldap working with jruby/puppetserver Change By: Josh Cooper Release Notes Summary: Update the ldap node terminus so that puppetserver is able to retrieve node classes, parameters and environments from LDAP. Release Notes: Bug Fix 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-7986) Puppet tests do not wait for the puppet-agent install on Windows to finish
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7986 Puppet tests do not wait for the puppet-agent install on Windows to finish Change By: Kenn Hussey Release Notes: Not Needed 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 (BOLT-91) multi-task plans swallow output from all but the last task
Title: Message Title Alex Dreyer commented on BOLT-91 Re: multi-task plans swallow output from all but the last task Dan Wittenberg What would the structure of that be when different nodes took part in different tasks? Would you want a map of nodes with an array of the results for each node? 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 (BOLT-91) multi-task plans swallow output from all but the last task
Title: Message Title Dan Wittenberg commented on BOLT-91 Re: multi-task plans swallow output from all but the last task I think my preference would just have a json object returned with the status of each node, if it passed or not. If you are running this from an automation tool, you'll want to know if it worked or not on a per-node basis, and obviously and exit code for the entire run, but that kind of output would be human-readable too if you are just running commands ad-hoc. If you are running debug mode then increase the json to include output like now, but for ALL the output and not just the last thing run. You could even have an option like the other tools to change the output format, so maybe human-readable plain txt by default, or you can change to json/yaml or whatever plugin might come in the future. 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-7308) classes do not honor refresh events when running with tags
Title: Message Title Kenn Hussey commented on PUP-7308 Re: classes do not honor refresh events when running with tags Maggie Dreyer please add release notes for this issue, if applicable. 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-7883) Make node_terminus=ldap working with jruby/puppetserver
Title: Message Title Kenn Hussey commented on PUP-7883 Re: Make node_terminus=ldap working with jruby/puppetserver Josh Cooper please add release notes for this issue, if applicable. 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 (PDB-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3692 PDB migration error due to facts deduplication and null values Change By: Kenn Hussey Comment: [~russell.mull] please add release notes for this issue, if applicable. 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 (PDB-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3692 PDB migration error due to facts deduplication and null values Change By: Kenn Hussey Comment: Oops, [~russell.mull] please disregard. 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 Kenn Hussey updated an issue Puppet / PUP-8026 Module code translation should be supported with puppet agent runs Change By: Kenn Hussey Fix Version/s: PUP 5.3.3 Fix Version/s: PUP 5.3.4 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-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Kenn Hussey commented on PDB-3692 Re: PDB migration error due to facts deduplication and null values Oops, Russell Mull please disregard. 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-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Kenn Hussey commented on PDB-3692 Re: PDB migration error due to facts deduplication and null values Russell Mull please add release notes for this issue, if applicable. 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 (PDB-3630) Configurable facts blacklist
Title: Message Title Kenn Hussey commented on PDB-3630 Re: Configurable facts blacklist Zachary Kent please add release notes for this issue, if applicable. 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-8040) Puppet does not initialize I18N locale per thread
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8040 Puppet does not initialize I18N locale per thread Change By: Kenn Hussey Flagged: Impediment 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 (BOLT-192) Bolt is not compatible with net-ssh 4.0 or 4.1
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-192 Bolt is not compatible with net-ssh 4.0 or 4.1 Change By: Josh Cooper Sprint: Tasks Kanban 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-3723) Use JSONB for fact storage
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-3723 Use JSONB for fact storage Change By: Russell Mull Assignee: Russell Mull 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-7987) Add support to defined top scope variables to the Pal API
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7987 Add support to defined top scope variables to the Pal API Change By: Josh Cooper Fix Version/s: BOLT 0.6.0 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-8068) Use Puppet.lookup to resolve executor
Title: Message Title Josh Cooper commented on PUP-8068 Re: Use Puppet.lookup to resolve executor This was merged to feature_puppet-tasks in https://github.com/puppetlabs/puppet/commit/38f53af4433ccbeb5948faf39cfd43216988b8a2. 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 (BOLT-192) Bolt is not compatible with net-ssh 4.0 or 4.1
Title: Message Title Josh Cooper commented on BOLT-192 Re: Bolt is not compatible with net-ssh 4.0 or 4.1 See https://github.com/net-ssh/net-ssh/commit/c3fbcdc882f6763fa718f6adbd9d1d60eaf04b62 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-8013) Translations should be stored in different text domains based on environment
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-8013
Translations should be stored in different text domains based on environment
Change By:
Michael Smith
Users can have different sets and different versions of modules per Puppet environment. In the current system we only load module translations once, so if a user changes their environment to one with a new version of the module in it, the translations will not be updated.We should make translations environment-aware by creating a new text domain for each environment. (note that it appears the current text domain setting is thread local, like locales https://github.com/grosser/fast_gettext/blob/master/lib/fast_gettext/storage.rb#L54) When we load a module's translations, they should be added to the appropriate text domain, and that domain should be loaded when we select an environment (such as on each compilation request , start an application with a configured environment, or switch environment during an agent run ). Modules should be responsible for loading their own translation files, by adding the translations to a gettext repository and adding that repository to the correct text domain. This should be idempotent.We need to decide where to initialize the text domains themselves. On the server side, this probably happens as part of the HTTP handler for compilation. On the agent side, this is part of application startup. On the agent side, we don't need to tie text domains to environments because we only ever have one active at once.Text domains should be tied to the environment lifecycle; i.e. when an environment is refreshed, the text domains should be too, to pick up any updates to module translations that occurred. The {{EnvironmentLoader}} might be a good place to put the logic to blow away outdated text domains.[~henrik.lindberg] probably has the most expertise on the environment lifecycle and how things are loaded within an environment.
Add Comment
This message was sent by Atlassian JIRA
Jira (BOLT-192) Bolt is not compatible with net-ssh 4.0 or 4.1
Title: Message Title Josh Cooper created an issue Puppet Task Runner / BOLT-192 Bolt is not compatible with net-ssh 4.0 or 4.1 Issue Type: Improvement Assignee: Unassigned Created: 2017/10/23 9:28 AM Priority: Normal Reporter: Josh Cooper Using bolt with net-ssh 4.0 or 4.1 fails with: [root@master /]# bolt command run 'ping 127.0.0.1 -c2' -n 192.168.217.167 -u root -p puppet 192.168.217.167: Failed to connect to 192.168.217.167: invalid option(s): verify_host_key Updating to 4.2.0 fixes the issue. Bolt's dependency on net-ssh should be updated to "~> 4.2" or use an option that is valid for all 4.x versions.
Jira (PUP-8013) Translations should be stored in different text domains based on environment
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-8013
Translations should be stored in different text domains based on environment
Change By:
Michael Smith
Users can have different sets and different versions of modules per Puppet environment. In the current system we only load module translations once, so if a user changes their environment to one with a new version of the module in it, the translations will not be updated.We should make translations environment-aware by creating a new text domain for each environment. (note that it appears the current text domain setting is thread local, like locales https://github.com/grosser/fast_gettext/blob/master/lib/fast_gettext/storage.rb#L54) When we load a module's translations, they should be added to the appropriate text domain, and that domain should be loaded when the we select an environment changes (such as on each compilation request) . Modules should be responsible for loading their own translation files, by adding the translations to a gettext repository and adding that repository to the correct text domain. This should be idempotent.We need to decide where to initialize the text domains themselves. On the server side, this probably happens as part of the HTTP handler for compilation. On the agent side, this is part of application startup. On the agent side, we don't need to tie text domains to environments because we only ever have one active at once.Text domains should be tied to the environment lifecycle; i.e. when an environment is refreshed, the text domains should be too, to pick up any updates to module translations that occurred. The {{EnvironmentLoader}} might be a good place to put the logic to blow away outdated text domains.[~henrik.lindberg] probably has the most expertise on the environment lifecycle and how things are loaded within an environment.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Casey Williams updated an issue Facter / FACT-1781 Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 Change By: Casey Williams Fix Version/s: FACT 3.9.z 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-8013) Translations should be stored in different text domains based on environment
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-8013
Translations should be stored in different text domains based on environment
Change By:
Michael Smith
Users can have different sets and different versions of modules per Puppet environment. In the current system we only load module translations once, so if a user changes their environment to one with a new version of the module in it, the translations will not be updated. We should make translations environment-aware by creating a new text domain for each environment. (note that it appears the current text domain setting is thread local, like locales https://github.com/grosser/fast_gettext/blob/master/lib/fast_gettext/storage.rb#L54) When we load a module's translations, they should be added to the appropriate text domain, and that domain should be loaded when the environment changes. Modules should be responsible for loading their own translation files, by adding the translations to a gettext repository and adding that repository to the correct text domain. This should be idempotent.We need to decide where to initialize the text domains themselves. On the server side, this probably happens as part of the HTTP handler for compilation. On the agent side, this is part of application startup. On the agent side, we don't need to tie text domains to environments because we only ever have one active at once.Text domains should be tied to the environment lifecycle; i.e. when an environment is refreshed, the text domains should be too, to pick up any updates to module translations that occurred. The {{EnvironmentLoader}} might be a good place to put the logic to blow away outdated text domains.[~henrik.lindberg] probably has the most expertise on the environment lifecycle and how things are loaded within an environment.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8040
Puppet does not initialize I18N locale per thread
Change By:
Maggie Dreyer
From a few hours of investigation, the puppetserver appears to track translation repositories from compile to compile, but either "forgets" about the locale after each compile, or must have the locale initialized in EVERY thread individually.Some technical details:- {{Puppet::GettextConfig.initialize_i18n}} checks {{translation_repositories}} before initializing {{FastGettext.locale}}, and thus only initializes the locale once ever (see https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/module.rb#L427-L446).- {{FastGettext.translation_repositories}} are a class variable. According to the FastGettext readme, {{FastGettext.locale}} must be initialized once per thread: https://github.com/grosser/fast_gettext#3-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) but the translation repositories should only needed to be loaded once.We are going to explore refactoring the gettext initialization code to skip the logic around {{available_locales}} and {{FastGettext.locale}} in favor of just setting {{FastGettext.default_locale}} to the system locale directly, since {{default_locale}} is not thread local, unlike {{FastGettext.locale}}. That library should already handle the fallback cases from this configuration (though we will be writing tests to verify this, see PUP-8080). In order to avoid breaking other users of GettextSetup, we will likely be implementing most of this directly in Puppet as gettext utils, and drop our runtime dependency on GettextSetup.It looks like we might run into a similar issue when we start trying to use more text domains (see PUP-8013 and https://github.com/grosser/fast_gettext/blob/master/lib/fast_gettext/storage.rb#L54) as the current text domain also appears to be a thread-local variable. Currently we're avoiding issues here by only using one text domain which is both set as {{FastGettext.text_domain}} and {{FastGettext.default_text_domain}} , the latter of which is not thread local .
Add Comment
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8040
Puppet does not initialize I18N locale per thread
Change By:
Maggie Dreyer
From a few hours of investigation, the puppetserver appears to track translation repositories from compile to compile, but either "forgets" about the locale after each compile, or must have the locale initialized in EVERY thread individually.Some technical details:- {{Puppet::GettextConfig.initialize_i18n}} checks {{translation_repositories}} before initializing {{FastGettext.locale}}, and thus only initializes the locale once ever (see https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/module.rb#L427-L446).- {{FastGettext.translation_repositories}} are a class variable. According to the FastGettext readme, {{FastGettext.locale}} must be initialized once per thread: https://github.com/grosser/fast_gettext#3-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) but the translation repositories should only needed to be loaded once.We are going to explore refactoring the gettext initialization code to skip the logic around {{available_locales}} and {{FastGettext.locale}} in favor of just setting {{FastGettext.default_locale}} to the system locale directly, since {{default_locale}} is not thread local, unlike {{FastGettext.locale}}. That library should already handle the fallback cases from this configuration (though we will be writing tests to verify this, see PUP-8080). In order to avoid breaking other users of GettextSetup, we will likely be implementing most of this directly in Puppet as gettext utils, and drop our runtime dependency on GettextSetup. It looks like we might run into a similar issue when we start trying to use more text domains (see PUP-8013 and https://github.com/grosser/fast_gettext/blob/master/lib/fast_gettext/storage.rb#L54) as the current text domain also appears to be a thread-local variable. Currently we're avoiding issues here by only using one text domain which is both set as {{FastGettext.text_domain}} and {{FastGettext.default_text_domain}}.
Add Comment
Jira (PUP-8013) Translations should be stored in different text domains based on environment
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8013
Translations should be stored in different text domains based on environment
Change By:
Maggie Dreyer
Users can have different sets and different versions of modules per Puppet environment. In the current system we only load module translations once, so if a user changes their environment to one with a new version of the module in it, the translations will not be updated.We should make translations environment-aware by creating a new text domain for each environment. (note that it appears the current text domain setting is thread local, like locales https://github.com/grosser/fast_gettext/blob/master/lib/fast_gettext/storage.rb#L54) When we load a module's translations, they should be added to the appropriate text domain, and that domain should be loaded when the environment changes. Modules should be responsible for loading their own translation files, by adding the translations to a gettext repository and adding that repository to the correct text domain. This should be idempotent.We need to decide where to initialize the text domains themselves. On the server side, this probably happens as part of the HTTP handler for compilation. On the agent side, this is part of application startup. On the agent side, we don't need to tie text domains to environments because we only ever have one active at once.Text domains should be tied to the environment lifecycle; i.e. when an environment is refreshed, the text domains should be too, to pick up any updates to module translations that occurred. The {{EnvironmentLoader}} might be a good place to put the logic to blow away outdated text domains.[~henrik.lindberg] probably has the most expertise on the environment lifecycle and how things are loaded within an environment.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8040
Puppet does not initialize I18N locale per thread
Change By:
Maggie Dreyer
From a few hours of investigation, the puppetserver appears to track translation repositories from compile to compile, but either "forgets" about the locale after each compile, or must have the locale initialized in EVERY thread individually.Some technical details:- {{Puppet::GettextConfig.initialize_i18n}} checks {{translation_repositories}} before initializing {{FastGettext.locale}}, and thus only initializes the locale once ever (see https://github.com/puppetlabs/puppet/blob/5.3.2/lib/puppet/module.rb#L427-L446).- {{FastGettext.translation_repositories}} are a class variable. According to the FastGettext readme, {{FastGettext.locale}} must be initialized once per thread: https://github.com/grosser/fast_gettext#3-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) but the translation repositories should only needed to be loaded once.We are going to explore refactoring the gettext initialization code to skip the logic around {{available_locales}} and {{FastGettext.locale}} in favor of just setting {{FastGettext.default_locale}} to the system locale directly, since {{default_locale}} is not thread local, unlike {{FastGettext.locale}}. That library should already handle the fallback cases from this configuration (though we will be writing tests to verify this, [ticket to be filed] see PUP-8080 ). In order to avoid breaking other users of GettextSetup, we will likely be implementing most of this directly in Puppet as gettext utils, and drop our runtime dependency on GettextSetup.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8040) Puppet does not initialize I18N locale per thread
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8040 Puppet does not initialize I18N locale per thread Change By: Maggie Dreyer Story Points: 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 (HI-586) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Laura Macchi commented on HI-586 Re: Lookup ignores environment from the classifier when using rule with trusted facts Any news? Do you need any more information? 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-8080) Puppet i18n with Modules: Add basic modules tests
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8080 Puppet i18n with Modules: Add basic modules tests Change By: Eric Delaney QA Risk Assessment: Automate No Action Release Notes: Not Needed 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-8080) Puppet i18n with Modules: Add basic modules tests
Title: Message Title John Duarte updated an issue Puppet / PUP-8080 Puppet i18n with Modules: Add basic modules tests Change By: John Duarte QA Risk Assessment: Needs Assessment Automate 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-7517) Add logic for restarting hung catalog application
Title: Message Title Charlie Sharpsteen assigned an issue to Justin Stoller Puppet / PUP-7517 Add logic for restarting hung catalog application Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Justin Stoller 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-7986) Puppet tests do not wait for the puppet-agent install on Windows to finish
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7986 Puppet tests do not wait for the puppet-agent install on Windows to finish Change By: Kenn Hussey Team: Platform OS 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title John Duarte updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: John Duarte QA Risk Assessment: Needs Assessment Automate 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-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title John Duarte updated an issue Facter / FACT-1781 Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 Change By: John Duarte 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 (PUP-7517) Add logic for restarting hung catalog application
Title: Message Title Peter Souter commented on PUP-7517 Re: Add logic for restarting hung catalog application Moses Mendoza Seems Charlie Sharpsteen has fixed those feedback changes, should this be reassigned back? 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-7993) Tidy Resource 'Type' Bug
Title: Message Title Geoff Nichols assigned an issue to Unassigned Puppet / PUP-7993 Tidy Resource 'Type' Bug Change By: Geoff Nichols Assignee: Geoff Nichols 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-1783) processors['count'] wrong for LXC containers
Title: Message Title Kevin Häfeli created an issue Facter / FACT-1783 processors['count'] wrong for LXC containers Issue Type: Bug Assignee: Unassigned Created: 2017/10/23 4:40 AM Environment: Debian Jessie Kernel 4.6.0-0.bpo.1-amd64 lxc 1:2.0.3-1~bpo8+1 /opt/puppetlabs/bin/facter --version 3.6.7 (commit 52880d129e2bd6bee33fc6355a96ea5fb03fd7e8) Priority: Normal Reporter: Kevin Häfeli /opt/puppetlabs/bin/facter processors
Jira (PDB-3730) Installing puppetdb fails with psql: FATAL: database "puppetdb" does not exist
Title: Message Title
Roger Mårtensson created an issue
PuppetDB / PDB-3730
Installing puppetdb fails with psql: FATAL: database "puppetdb" does not exist
Issue Type:
Bug
Assignee:
Unassigned
Components:
Module
Created:
2017/10/23 2:41 AM
Environment:
Ubuntu 16.04 with puppet and postgreSQL repositories already added. Using puppetlabs-puppetdb v6.0.1
Priority:
Normal
Reporter:
Roger Mårtensson
When trying to install PuppetDB on a clean system I get an error.
This is how I install it: class { 'puppetdb': manage_package_repo => false, disable_ssl => true, }
The error I get is: Error: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Extension[pg_trgm]/Postgresql_psql[Add pg_trgm extension to puppetdb]: Could not evaluate: Error evaluating 'unless' clause, returned pid 5494 exit 2: 'psql: FATAL: database "puppetdb" does not exist
The reason is that it is trying to install the extension in puppetdb::database::postgresql before the database is added. Whenever the $manage_server is set is must have an requirement on the database or the database creation is moved before the adding of the extension.
