Jira (PUP-6865) puppet 4.8.0 breaks code that uses strftime()
Title: Message Title James Ralston commented on PUP-6865 Re: puppet 4.8.0 breaks code that uses strftime() Just to confirm: Thomas Hallgren's hunch was correct: I had updated puppet-agent on the master, but hadn't restarted the master. Restarting the master resolved the problems. The real issue here is that the puppetserver package is broken, because the server needs to be restarted if the puppet-agent package changes, but the puppetserver spec file lacks a %triggerpostun trigger on the puppet-agent package. (See PA-681 for more information and a suggested 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-6943) control ordering of classic Hiera versus environment data searching
Title: Message Title
James Ralston commented on PUP-6943
Re: control ordering of classic Hiera versus environment data searching
It feels hackish, but I believe your suggestion would work.
For example, right now, in our global (version 3) hiera.yaml file, we have:
:yaml:
:datadir: /etc/puppetlabs/code/hiera
:hierarchy:
- nodes/%{fqdn}/config
- ./%{hiera_area_0}/config
- ./%{hiera_area_1}/config
- ./%{hiera_area_2}/config
- ./%{hiera_area_3}/config
- ./%{hiera_area_4}/config
- ./%{hiera_area_5}/config
Jira (PUP-6405) Pip package provider runs every time when updating setuptools
Title: Message Title Ben Hines commented on PUP-6405 Re: Pip package provider runs every time when updating setuptools Same thing happens when trying to manage 'wheel' using pip. It's not listed in 'pip freeze' unless '--all' is specified. Why not use 'pip list' instead of 'pip freeze' (or pip freeze 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-6552) Regression: Redhat / Debian / Ubuntu can't specify 'init' provider
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6552 Regression: Redhat / Debian / Ubuntu can't specify 'init' provider Change By: Geoff Nichols Sprint: Client 2016-09-07, AP 2016-12- 14 28 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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6777 regression: incompatible character encodings: UTF-8 and ASCII-8BIT Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3631 NIM provider uses a regex that is too restrictive when parsing RPM release tags Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6612) Scope effort for i18n string externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6708 Agent does not save local copy of last_run_report.yaml if submission to report server fails Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6364) On AIX, an already installed package is not updated when using "ensure => latest"
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6364 On AIX, an already installed package is not updated when using "ensure => latest" Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6762) (SPIKE) How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6762 (SPIKE) How and when do we get PO files from Transifex? Change By: Geoff Nichols Sprint: AP 2016-11-16, AP 2016-12- 14 28 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-5334) Puppet can't remove users from groups in OSX.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5334 Puppet can't remove users from groups in OSX. Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6716) Error when purging local users on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6716 Error when purging local users on Windows Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6763) Make CI job to update POT files
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6763 Make CI job to update POT files Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6764) Add PO files with translated strings to Puppet repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Add PO files with translated strings to Puppet repo Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Geoff Nichols Sprint: AP 2016-12- 14 28 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-3035) PDB should use gzip when replicating data
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3035 PDB should use gzip when replicating data Change By: Russell Mull Affects Version/s: PE Next 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-6886) Compatibility with hiera 3 JSON/YAML files
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6886 Compatibility with hiera 3 JSON/YAML files Change By: Eric Thompson QA Risk Assessment Reason: current acceptance QA Risk Assessment: No Action QA Contact: Eric Thompson 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-6886) Compatibility with hiera 3 JSON/YAML files
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6886 Compatibility with hiera 3 JSON/YAML files Change By: Eric Thompson 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-6886) Compatibility with hiera 3 JSON/YAML files
Title: Message Title Eric Thompson commented on PUP-6886 Re: Compatibility with hiera 3 JSON/YAML files the existing tests do this (using various data providers and global hiera, hiera v4): https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/parser_functions/puppet_lookup_cmd.rb#L337 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-3035) PDB should use gzip when replicating data
Title: Message Title Brett Gray commented on PDB-3035 Re: PDB should use gzip when replicating data Swet! 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-6947) puppet server logging giant stacktraces for deprecation warnings
Title: Message Title Karen Van der Veer moved an issue Puppet / PUP-6947 puppet server logging giant stacktraces for deprecation warnings Change By: Karen Van der Veer Key: SERVER PUP - 1667 6947 Project: Puppet Server 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-3035) PDB should use gzip when replicating data
Title: Message Title Russell Mull commented on PDB-3035 Re: PDB should use gzip when replicating data Just fired up wireshark to see what it's doing right now... and it's already gzipping. Pretty good compression ratios too, saw 200k -> 20k on some of the summary responses for the 3000 node test set. 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-3207) Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release
Title: Message Title Jeremy Barlow updated an issue PuppetDB / PDB-3207 Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release Change By: Jeremy Barlow Team: Systems Engineering Sprint: SE Triage 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 (PDOC-150) README links broken after being HTMLfied
Title: Message Title David Hollinger III created an issue Puppet Strings / PDOC-150 README links broken after being HTMLfied Issue Type: Bug Assignee: Unassigned Created: 2016/11/29 3:21 PM Priority: Normal Reporter: David Hollinger III When Puppet Strings turns the README.md into an HTML document, I have found that: Markdown anchors are not properly converted and don't actually go anywhere when clicked. Links to other Markdown files are converted to HTML expecting the referenced files to also have been converted into yardoc HTML, however puppet-strings is only aware of the README.md, not any other markdown files in the root of the repository and as such you end up with a link to a 404 message in the finished yardoc page. Example: dhollinger/autofs-puppet README references a CONTRIBUTING.md file for contribution guidelines. Puppet Strings sees that link and creates an HREF to this URL: https://dhollinger.github.io/autofs-puppet/CONTRIBUTING.md. My guess is that it sees the github flavored markdown "[CONTRIBUTING.md](CONTRIBUTING.md)" and converts that directly to the the URL seen above without validating that an HTML or Markdown file exists in that path. Not sure if this is an issue related to the conversion of github flavored markdown to HTML or not, but I figured it'd be easiest to start the troubleshooting process here.
Jira (PDB-3207) Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release
Title: Message Title Jeremy Barlow updated an issue PuppetDB / PDB-3207 Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release Change By: Jeremy Barlow This ticket covers backporting the work that was done for PDB-3077 for service reload and logback sized-based rotation to a PuppetDB release which would be rolled into PE 2016.4.3.The original OSS work for this was done here:https://github.com/puppetlabs/puppetdb/pull/2087The original PE work for this was done here:https://github.com/puppetlabs/pe-puppetdb-extensions/pull/229In both cases, we should bump to a later version of lein-ezbake than the original PRs used, though. 1.1.3 or later should be fine. We'll also need to include a pe-puppetdb fix for moving initial sync logic onto a background thread. This work was done in https://github.com/puppetlabs/pe-puppetdb-extensions/pull/242. This needs to be included in order to avoid the new ezbake startup logic otherwise encountering timeout failures if the completion of the start phase is held off until after the initial sync is finished. 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-6946) Signed tarball of puppet 4.8.1 missing on https://downloads.puppetlabs.com/puppet/
Title: Message Title Stig Sandbeck Mathisen created an issue Puppet / PUP-6946 Signed tarball of puppet 4.8.1 missing on https://downloads.puppetlabs.com/puppet/ Issue Type: Bug Affects Versions: PUP 4.8.1 Assignee: Unassigned Created: 2016/11/29 2:57 PM Priority: Normal Reporter: Stig Sandbeck Mathisen Hello, The signed tarball of puppet 4.8.1 is missing on https://downloads.puppetlabs.com/puppet/ I use these as the base of the Debian (and Ubuntu) packaging of puppet. Regards, Stig Sandbeck Mathisen Add Comment
Jira (PUP-6828) Agent PKI initialization is too complicated
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-6828 Agent PKI initialization is too complicated Change By: Adrien Thebo Sprint: SE 2016-12-14 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-3207) Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release
Title: Message Title Jeremy Barlow created an issue PuppetDB / PDB-3207 Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release Issue Type: Task Assignee: Unassigned Created: 2016/11/29 2:35 PM Priority: Normal Reporter: Jeremy Barlow This ticket covers backporting the work that was done for PDB-3077 for service reload and logback sized-based rotation to a PuppetDB release which would be rolled into PE 2016.4.3. The original OSS work for this was done here: https://github.com/puppetlabs/puppetdb/pull/2087 The original PE work for this was done here: https://github.com/puppetlabs/pe-puppetdb-extensions/pull/229 In both cases, we should bump to a later version of lein-ezbake than the original PRs used, though. 1.1.3 or later should be fine. Add Comment
Jira (PUP-6926) lookup should allow rich data as values
Title: Message Title Eric Thompson commented on PUP-6926 Re: lookup should allow rich data as values created a sub-task for automation of acceptance on this one. sorry, it came late in the sprint. may carry over. let me know if this is an issue. 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-6945) acceptance: lookup rich data values
Title: Message Title Eric Thompson created an issue Puppet / PUP-6945 acceptance: lookup rich data values Issue Type: Sub-task Assignee: Eric Thompson Components: QA Created: 2016/11/29 2:27 PM Priority: Normal Reporter: Eric Thompson 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"
Jira (PUP-6926) lookup should allow rich data as values
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6926 lookup should allow rich data as values Change By: Eric Thompson QA Risk 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-6926) lookup should allow rich data as values
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6926 lookup should allow rich data as values Change By: Eric Thompson QA Contact: Eric Thompson 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-6926) lookup should allow rich data as values
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6926 lookup should allow rich data as values Change By: Eric Thompson QA Risk Assessment Reason: needs acceptance. add rich types to existing tests. 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-6933) Puppet tests fail with 'environment env2 enviroment_key lookup failed'
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6933 Puppet tests fail with 'environment env2 enviroment_key lookup failed' Change By: Eric Thompson QA Risk Assessment Reason: fix previous automation 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-6933) Puppet tests fail with 'environment env2 enviroment_key lookup failed'
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6933 Puppet tests fail with 'environment env2 enviroment_key lookup failed' Change By: Eric Thompson QA Contact: Eric Thompson 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-6933) Puppet tests fail with 'environment env2 enviroment_key lookup failed'
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6933 Puppet tests fail with 'environment env2 enviroment_key lookup failed' Change By: Eric Thompson QA Risk 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-6917) the 'site' keyword cannot be used as an attribute name when app_management is on
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6917 the 'site' keyword cannot be used as an attribute name when app_management is on Change By: Eric Thompson QA Risk Assessment: Automate 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-6917) the 'site' keyword cannot be used as an attribute name when app_management is on
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6917 the 'site' keyword cannot be used as an attribute name when app_management is on Change By: Eric Thompson QA Risk Assessment Reason: covered well by parser unit tests 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-6917) the 'site' keyword cannot be used as an attribute name when app_management is on
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6917 the 'site' keyword cannot be used as an attribute name when app_management is on Change By: Eric Thompson QA Risk 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-6917) the 'site' keyword cannot be used as an attribute name when app_management is on
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6917 the 'site' keyword cannot be used as an attribute name when app_management is on Change By: Eric Thompson QA Contact: Eric Thompson 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-6844) Ignore mercurial artifacts (.hg) when downloading plugins
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6844 Ignore mercurial artifacts (.hg) when downloading plugins Change By: Eric Thompson QA Risk Assessment Reason: pluginsync ignore pattern, low risk QA Risk Assessment: No Action QA Contact: Eric Thompson 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-6921) Improve separation of concern between String and Enum types
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6921 Improve separation of concern between String and Enum types Change By: Eric Thompson QA Risk Assessment Reason: ruby API, covered well by unit tests QA Risk 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-6921) Improve separation of concern between String and Enum types
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6921 Improve separation of concern between String and Enum types Change By: Eric Thompson QA Contact: Eric Thompson 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-6944) Reduce the windows spec matrix
Title: Message Title Josh Cooper created an issue Puppet / PUP-6944 Reduce the windows spec matrix Issue Type: Task Assignee: Unassigned Created: 2016/11/29 1:33 PM Priority: Normal Reporter: Josh Cooper We're currently testing puppet specs on win2008r2 and 2012r2 on 4 versions of ruby (2.1.9 and 2.3.1 x86 & x64). Each combination takes ~25 mins, and if there are concurrent commits to LTS-1.7, stable and master, then jobs will contend for coordinators. In QENG-4408 we talked about removing the 2012 combinations. This ticket is to implement that change in ci-job-configs. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3205) transient failure in core command_test.clj observed 11/28
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3205 transient failure in core command_test.clj observed 11/28 Change By: Rob Browning Labels: maintenance 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-6934) Determine correct directory for locale files
Title: Message Title Maggie Dreyer commented on PUP-6934 Re: Determine correct directory for locale files I have verified that using MO files to load in translations works as advertised on Windows, using the Program Files directory specified in the attached PR. 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title
Eric Thompson commented on PUP-6882
Re: Incorrect handling of escape sequence precedence
validated on el7 with puppet-agent master sha: 21f5390cac805296430f44d1dbbf8e1ec5f6ca87
[root@mjxajzbzjk1dnf8 ~]# puppet apply -e 'notify { "\u": }'
Notice: Compiled catalog for mjxajzbzjk1dnf8.delivery.puppetlabs.net in environment production in 0.07 seconds
Notice: �
Notice: /Stage[main]/Main/Notify[�]/message: defined 'message' as '�'
Notice: Applied catalog in 0.04 seconds
[root@mjxajzbzjk1dnf8 ~]# puppet apply -e 'notify { "\\u": }'
Notice: Compiled catalog for mjxajzbzjk1dnf8.delivery.puppetlabs.net in environment production in 0.06 seconds
Notice: \u
Notice: /Stage[main]/Main/Notify[\u]/message: defined 'message' as '\u'
Jira (PDB-3205) transient failure in core command_test.clj observed 11/28
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3205 transient failure in core command_test.clj observed 11/28 Change By: Rob Browning Assignee: Rob Browning Story Points: 1 Team: Systems Engineering Sprint: Hopper SE 2016-11-30 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-6663) Large volumes of RPM queries leave stale locks on the rpm database
Title: Message Title William Hopper updated an issue Puppet / PUP-6663 Large volumes of RPM queries leave stale locks on the rpm database Change By: William Hopper Release Notes Summary: Previously, Puppet did not appropriately quote the RPM query string when determining package state with the RPM provider. This caused stale locks to be left on the RPM database when large volumes of RPM queries were run. This change adds the necessary quotes to the query to prevent this from happening. 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-6663) Large volumes of RPM queries leave stale locks on the rpm database
Title: Message Title William Hopper updated an issue Puppet / PUP-6663 Large volumes of RPM queries leave stale locks on the rpm database Change By: William Hopper Fix Version/s: PUP 4.9.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-6844) Ignore mercurial artifacts (.hg) when downloading plugins
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6844
Ignore mercurial artifacts (.hg) when downloading plugins
Change By:
William Hopper
Acceptance Criteria:
When pluginsyncing, no files with the {{.hg}} extension should be downloaded.
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-6844) Ignore mercurial artifacts (.hg) when downloading plugins
Title: Message Title William Hopper updated an issue Puppet / PUP-6844 Ignore mercurial artifacts (.hg) when downloading plugins Change By: William Hopper Release Notes Summary: This change updates the list of file extensions which should be ignored when downloading plugins via pluginsync to also ignore Mercurial (.hg) artifacts. 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-6844) Ignore mercurial artifacts (.hg) when downloading plugins
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6844 Ignore mercurial artifacts (.hg) when downloading plugins Change By: William Hopper Status: Ready for CI Test Assignee: William Hopper qa 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-6933) Puppet tests fail with 'environment env2 enviroment_key lookup failed'
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6933 Puppet tests fail with 'environment env2 enviroment_key lookup failed' Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6934) Determine correct directory for locale files
Title: Message Title Maggie Dreyer commented on PUP-6934 Re: Determine correct directory for locale files The translation files for the C++ projects will have to be binary MO files, rather than PO files. For consistency, we have decided to also compile puppet's PO files to MO format, to allow for a single directory structure across projects. In order to use MO files in Puppet, we need to update the gettext-setup gem to allow specifying the file format. The PR for that is here: https://github.com/puppetlabs/gettext-setup-gem/pull/14. 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-6188) Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings
Title: Message Title Moses Mendoza commented on PUP-6188 Re: Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings I ran the specs myself on fedora 24 and they all passed - it seems likely that this test is impacted by a change in umask, and this is perhaps too brittle as-is 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-6188) Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings
Title: Message Title
Moses Mendoza commented on PUP-6188
Re: Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings
From Thomas Hallgren in hipchat:
[5:25 AM] Thomas Hallgren: The latest on puppet master doesn't run the rspec tests clean on my machine (Fedora 24). I get this failure: [5:25 AM] Thomas Hallgren: 1) Puppet::FileSystem #open uses a default mode of 100644, the same as File.open, when specifying a nil mode Failure/Error: expect(File.stat(file).mode.to_s(8)).to eq('100644') expected: "100644" got: "100664" (compared using ==)
./spec/unit/file_system_spec.rb:35:in `block (3 levels) in ' [5:27 AM] Thomas Hallgren: @moses this seems to stem from your commit on PUP-6188 "Doc FileSystem::open ::exclusive_open".
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-6188) Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-6188 Document Puppet::FileSystem.open / exclusive_open encoding usage, and make existing code explicitly use encodings Change By: Moses Mendoza Assignee: Moses Mendoza 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-3035) PDB should use gzip when replicating data
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3035 PDB should use gzip when replicating data Change By: Russell Mull Story Points: 2 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-6576) Deprecate the data_binding_terminus setting under the control of --strict
Title: Message Title Moses Mendoza commented on PUP-6576 Re: Deprecate the data_binding_terminus setting under the control of --strict merged to master at https://github.com/puppetlabs/puppet/commit/5d6aa80514cf4c1d46c4b1650f4494fe6bb88c98 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-1541) Facter does not compile with icedtea JDK
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1541 Facter does not compile with icedtea JDK Change By: Maggie Dreyer Labels: maintenance 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-6741) When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6741 When `recurse => true` is used in a file resource, tags are not applied to all recursive objects. Change By: Geoff Nichols Story Points: 2 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-6741) When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Title: Message Title Geoff Nichols assigned an issue to Ethan Brown Puppet / PUP-6741 When `recurse => true` is used in a file resource, tags are not applied to all recursive objects. Change By: Geoff Nichols Assignee: Geoff Nichols 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-6741) When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6741 When `recurse => true` is used in a file resource, tags are not applied to all recursive objects. Change By: Geoff Nichols Sprint: AP Grooming 2016-11-30 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-6741) When `recurse => true` is used in a file resource, tags are not applied to all recursive objects.
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet / PUP-6741 When `recurse => true` is used in a file resource, tags are not applied to all recursive objects. Change By: Geoff Nichols Assignee: Moses Mendoza 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-1536) Add top-level facts to output from `--list-X-groups` commands
Title: Message Title Geoff Nichols assigned an issue to Branan Riley Facter / FACT-1536 Add top-level facts to output from `--list-X-groups` commands Change By: Geoff Nichols Assignee: Maggie Dreyer Branan Riley 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6882 Incorrect handling of escape sequence precedence Change By: Eric Thompson QA Risk Assessment Reason: functional review in comments. covered well by unit tests. 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6882 Incorrect handling of escape sequence precedence Change By: Eric Thompson QA Risk 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-6882) Incorrect handling of escape sequence precedence
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6882 Incorrect handling of escape sequence precedence Change By: Eric Thompson QA Contact: Eric Thompson 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-6821) binary_file() file not found: error message unclear
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6821 binary_file() file not found: error message unclear Change By: Eric Thompson QA Risk Assessment Reason: error message clarity; covered by unit tests 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-6821) binary_file() file not found: error message unclear
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6821 binary_file() file not found: error message unclear Change By: Eric Thompson QA Risk 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-6821) binary_file() file not found: error message unclear
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6821 binary_file() file not found: error message unclear Change By: Eric Thompson Release Notes Summary: the binary_file built-in function previously had an unclear error message when a specified file was not found. 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-6821) binary_file() file not found: error message unclear
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6821 binary_file() file not found: error message unclear Change By: Eric Thompson QA Contact: Eric Thompson 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-6821) binary_file() file not found: error message unclear
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6821 binary_file() file not found: error message unclear Change By: Eric Thompson 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Eric Thompson QA Risk Assessment Reason: annoyance. covered well by mocked unit tests 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Eric Thompson QA Risk 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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: Eric Thompson QA Contact: Eric Thompson 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-2631) PDB is incapable of efficiently storing large dynamic structured facter facts
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2631 PDB is incapable of efficiently storing large dynamic structured facter facts Change By: Karen Van der Veer Sprint: SE Triage 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-2631) PDB is incapable of efficiently storing large dynamic structured facter facts
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2631 PDB is incapable of efficiently storing large dynamic structured facter facts Change By: Karen Van der Veer Sprint: SE Triage 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-6943) control ordering of classic Hiera versus environment data searching
Title: Message Title
Henrik Lindberg commented on PUP-6943
Re: control ordering of classic Hiera versus environment data searching
We are currently discussion how to best migrate. What we are proposing is that you would move the data in the migrated environments to a directory that is not interpolated by the paths in the global "classic" hiera. Thereby the global layer will interpolate something like .../$environment/hiera_data/xxx.yaml and the environment that is migrated has no hiera_data directory, instead it keeps its files under (for example) data. The global layer will then have a miss for every key, while the env layer will find it.
This assumes that data is already placed inside the environment using {{$environment]} interpolation. If all the data is in a static location you could set a top scope variable in the environments that have migrated, and then interpolate this to make the static path interpolate to a non existing location.
Would that work for you?
I think we are not very keen on making it possible to rearrange the layers as it is quite complex as it is already, but maybe it would be simpler to do what you propose. One concern is that we want to retain the ability to have a global layer that makes use of the new version and at that point we would not want to allow flipping the global and the env layers. There are also subtle issues like hiera_xxx functions and lookup / data_binding not returning the same set of values. So yeah... potentially complex.
Ping Thomas Hallgren, Lindsey Smith and Eric Sorenson for second opinions.
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
Jira (HI-546) Defining resource types by means of hiera
Title: Message Title Henrik Lindberg commented on HI-546 Re: Defining resource types by means of hiera In 4.x, Puppet has the building blocks available to let you do this yourself as R.I points out. I am therefore closing this as a "won't do". 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-1534) Puppet classes should be able to declare that they are internal
Title: Message Title
Henrik Lindberg commented on PUP-1534
Re: Puppet classes should be able to declare that they are internal
We may also want to support private parameters and variables. That is something like this:
class foo::bar(private $a, $b) {
private $x = 'sesame'
$y = 'say friend and enter'
}
This would make an instance of foo::bar visible outside foo, but $foo::bar::a and $foo::bar::x are not, while $foo::bar::b and $foo::bar::y would be.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Henrik Lindberg commented on PUP-1534 Re: Puppet classes should be able to declare that they are internal In order to support this we need to: Update grammar and AST to wire the reserved keyword into the language and resulting AST We can do this element by element (classes, defines, functions, types) Update the loaders to allow elements to only be seen by the creating module - i.e. forbid creation/call Update the runtime so that scope knows if it is a private scope or not (we need to error on cross module variable access) It may be enough to only make creation / call, override, collection and variable access operations private - once a resource is created it may be publically available for functions like defined as well as reading its parameters. This is made somewhat difficult because there is the need to be able to deal with the resource in the catalog, noticing it, etc. which will reveal its values. Further discussion is needed for this. 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
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title
Henrik Lindberg commented on PUP-1534
Re: Puppet classes should be able to declare that they are internal
I think we may already have a ticket for this (need to look). We have the "private" keyword already in the puppet language, and the idea is to use it as follows:
private class foo() { }
private define foo() { }
private function foo() { }
private type T = T2
The semantics of private is that it may only be created and referenced from the module that contains the definition. In order to make that enforceable we also need to forbid arbitrary namespaces to be used - since as things are now, any manifest can define something in any namespace.
The addition of making the "private" keyword active can be made in a minor release, but the enforcement of namespaces is not backwards compatible and have to wait until a major release.
Add Comment
This message was sent by
Jira (HI-546) Defining resource types by means of hiera
Title: Message Title
R.I.Pienaar commented on HI-546
Re: Defining resource types by means of hiera
I wouldn't suggest this should be a built in feature personally, just like hiera_include is not long for this world and lookup wont have a native version of it.
But you can easily build this yourself and stick it on the forge, untested code but you get the idea:
node default {
include classifier
}
class classifier (
String $resources_key = "resources",
String $classes_key = "classes"
) {
$resources = lookup({"name" => $resources_key, "default_value" => {}, "merge" => "deep"})
$classes = lookup({"name" => $classes_key, "default_value" => [], "merge" => "unique"})
