Jira (PUP-7206) Change to puppet agent renders ::fqdn no longer valid for vhost name in hiera file for puppetlabs-apache module
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7206 Change to puppet agent renders ::fqdn no longer valid for vhost name in hiera file for puppetlabs-apache module Change By: Geoff Nichols Team: Puppet Developer Experience 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-7206) Change to puppet agent renders ::fqdn no longer valid for vhost name in hiera file for puppetlabs-apache module
Title: Message Title Geoff Nichols moved an issue Puppet / PUP-7206 Change to puppet agent renders ::fqdn no longer valid for vhost name in hiera file for puppetlabs-apache module Change By: Geoff Nichols Affects Version/s: puppet-agent 1.9.1 Affects Version/s: puppet-agent 1.9.0 Affects Version/s: PUP 4.9.0 Affects Version/s: PUP 4.9.1 Affects Version/s: PUP 4.9.2 Key: PA PUP - 946 7206 Project: Puppet Agent Add Comment
Jira (PUP-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Henrik Lindberg commented on PUP-7205 Re: Backport Hiera 5 eyaml support to Puppet 4.9.x Both Thomas and I are for this (we wanted this to go into 4.9.0 in the first place). 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Henrik Lindberg commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Josh Cooper Given that we fixed a number of quite fundamental bugs in 4.9.2 this is probably a duplicate. It is hard for me to see what the actual problem seen here is. Given that 4.9.2 is rolling out now the best is to try again on 4.9.2 to see if problem is still present. 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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x Change By: Lindsey Smith Fix Version/s: PUP 4.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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x Change By: Lindsey Smith Team: Puppet Developer Experience 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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Lindsey Smith created an issue Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x Issue Type: Task Assignee: Unassigned Created: 2017/02/10 5:01 PM Priority: Critical Reporter: Lindsey Smith Support for eyaml in Hiera 5 must be backported to Puppet 4.9.x so that PE LTS adopters can continue using the popular eyaml backend. Currently eyaml support is only in the 5.0 branch. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7151) selmodule type should explicitly specify encoding when reading selmodversion_file
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7151 selmodule type should explicitly specify encoding when reading selmodversion_file Change By: Moses Mendoza Story Points: 1 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-7151) selmodule type should explicitly specify encoding when reading selmodversion_file
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7151 selmodule type should explicitly specify encoding when reading selmodversion_file Change By: Moses Mendoza Sprint: AP Grooming 2017-02-22 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-7152) AIX user provider should specify passwd file encoding explicitly
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7152 AIX user provider should specify passwd file encoding explicitly Change By: Moses Mendoza Story Points: 1 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-7152) AIX user provider should specify passwd file encoding explicitly
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7152 AIX user provider should specify passwd file encoding explicitly Change By: Moses Mendoza Sprint: AP Grooming 2017-02-22 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-7152) AIX user provider should specify passwd file encoding explicitly
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7152 AIX user provider should specify passwd file encoding explicitly Change By: Moses Mendoza Fix Version/s: PUP 5.0.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-7152) AIX user provider should specify passwd file encoding explicitly
Title: Message Title Moses Mendoza commented on PUP-7152 Re: AIX user provider should specify passwd file encoding explicitly merged to master at https://github.com/puppetlabs/puppet/commit/b78a4cc060ae57248a498854df08499b6b262158 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module 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 (PUP-7042) Mark non-debug messages for externalization
Title: Message Title Maggie Dreyer commented on PUP-7042 Re: Mark non-debug messages for externalization Review for this is being tracked by PUP-7144. Resolving this following confirmation from David Lutterkort and Larissa Lane on MODULES-4300 that the approach taken for this ticket is good. 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-7202) excessive INFO logging when files arent found
Title: Message Title Jeremy Barlow commented on PUP-7202 Re: excessive INFO logging when files arent found Josh Cooper Yeah, I'm pretty sure you're right about the log statement originating from within the Puppet Ruby code. Puppet Server registers its own log destination with Puppet in order to route messages logged via Puppet's log utils through to Puppet Server's log output. It should respect the log level - info vs. debug - in the event we were to decide to change the level for this particular message. 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-7202) excessive INFO logging when files arent found
Title: Message Title Josh Cooper commented on PUP-7202 Re: excessive INFO logging when files arent found I believe puppet's code raises the exception, which I think puppetserver logs, but since there can be multiple sources, we should only log if none of the sources are found. /cc Jeremy Barlow 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7199
Update to puppet-agent 1.9.0-1jessie breaks puppet master
Change By:
Josh Cooper
Hello,after upgrading puppet-agent to version 1.9 on our puppet servera class defined in hieradata/os/Debian.yaml will not be rolled outany more. Thus due to purge is active files are deleted.Switching back to puppet-agent version 1.8.3 solved the problem.Any of these hiera yaml files contain a section{noformat}classes:{noformat}Mayby merging ist not done as defined any more:{code:java}:deep_merge_options: :knock_out_prefix: '--' sort_merge_arrays: true merge_hash_arrays: true{code} Environment{code:java}$ cat hiera.yaml---:backends: - yaml:yaml:# datadir is empty here, so hiera uses its defaults:# - /etc/puppetlabs/code/environments/%{environment}/hieradata on *nix# - %CommonAppData%\PuppetLabs\code\environments\%{environment}\hieradata on Windows# When specifying a datadir, make sure the directory exists. :datadir: /etc/puppetlabs/code/environments/%{environment}/hiera:hierarchy:# - "node/%{::fqdn}" - "node/%{::trusted.certname}" - "role/%{::role}" - "os/%{::osfamily}__%{::lsbdistcodename}" - "os/%{::osfamily}" - "users" - "common":logger: puppet:merge_behavior: deeper:deep_merge_options: :knock_out_prefix: '--' sort_merge_arrays: true merge_hash_arrays: true{code}
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
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Josh Cooper commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Henrik Lindberg is this a dup? 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7199
Update to puppet-agent 1.9.0-1jessie breaks puppet master
Change By:
Josh Cooper
Environment:
Debian GNU/Linux 8 (jessie)puppetlabs-release-pc1 1.1.0-4jessiepuppet-agent 1.9.0-1jessie {code:java}$ cat hiera.yaml---:backends: - yaml:yaml:# datadir is empty here, so hiera uses its defaults:# - /etc/puppetlabs/code/environments/%{environment}/hieradata on *nix# - %CommonAppData%\PuppetLabs\code\environments\%{environment}\hieradata on Windows# When specifying a datadir, make sure the directory exists. :datadir: /etc/puppetlabs/code/environments/%{environment}/hiera:hierarchy:# - "node/%{::fqdn}" - "node/%{::trusted.certname}" - "role/%{::role}" - "os/%{::osfamily}__%{::lsbdistcodename}" - "os/%{::osfamily}" - "users" - "common":logger: puppet:merge_behavior: deeper:deep_merge_options: :knock_out_prefix: '--' sort_merge_arrays: true merge_hash_arrays: true{code}
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-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title R.I.Pienaar commented on PUP-7204 Re: Add support for mapped paths in hiera.yaml version 5 Henrik Lindberg that looks pretty good to me 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-1569) Add Ubuntu 16.10 to Ubuntu facts acceptance test
Title: Message Title Maggie Dreyer commented on FACT-1569 Re: Add Ubuntu 16.10 to Ubuntu facts acceptance test It JUST passed. Resolving 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 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-1569) Add Ubuntu 16.10 to Ubuntu facts acceptance test
Title: Message Title Kenn Hussey commented on FACT-1569 Re: Add Ubuntu 16.10 to Ubuntu facts acceptance test Maggie Dreyer did you see that pipeline run yet? 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-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Henrik Lindberg commented on PUP-7204 Re: Add support for mapped paths in hiera.yaml version 5 Ping R.I.Pienaar - proposal based on idea in HI-257 for hiera.yaml version 5 format. 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-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-7204 Add support for mapped paths in hiera.yaml version 5 Issue Type: New Feature Assignee: Unassigned Created: 2017/02/10 2:16 PM Priority: Normal Reporter: Henrik Lindberg The feature of being able to map an array variable to multiple paths in the hierarchy has been on the wish list for quite some time. This was originally requested in HI-257 (then rejected, because there was no easy way of supporting this in the old hiera 3 format). Now in hiera.yaml version 5, this is doable. Proposed design: As yet an alternative to the existing path, paths etc. we add a mapped_paths that operates on a fact that is a collection, and maps that into an array of paths. mapped_paths: - -
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7204 Add support for mapped paths in hiera.yaml version 5 Change By: Henrik Lindberg Fix Version/s: PUP 5.0.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-7016) 5.0.0 Lookup features
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7016 5.0.0 Lookup features Change By: Henrik Lindberg Epic for features in "hiera 5" / lookup. A continuation of PUP-6484 (productize lookup) targeting puppet 4.9.0.* Hocon support* Ensuring that popular hiera (3) backends like eyaml works* T.B.D 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-3295) [WIP] host puppetserver in tests
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3295 [WIP] host puppetserver in tests Issue Type: Bug Assignee: Unassigned Created: 2017/02/10 1:50 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 https://groups.google.com/d/opto
Jira (PUP-7201) Additional certificate attributes should be exposed in trusted hash
Title: Message Title Henrik Lindberg commented on PUP-7201 Re: Additional certificate attributes should be exposed in trusted hash Side note: Puppet has data types for time (Timespan, and Timestamp) in the type system already. 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-7189) Add a fact value to log entries for subsequent classification
Title: Message Title Michael Smith updated an issue Puppet / PUP-7189 Add a fact value to log entries for subsequent classification Change By: Michael Smith Sprint: Puppet 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-7189) Add a fact value to log entries for subsequent classification
Title: Message Title Michael Smith commented on PUP-7189 Re: Add a fact value to log entries for subsequent classification I think the way we'd propose solving this is to pull data from PuppetDB and categorize logs in post-processing. Is that something that could work? 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-6823) Puppet filebucket command does not pick up proper server address from server_list config property
Title: Message Title Michael Smith updated an issue Puppet / PUP-6823 Puppet filebucket command does not pick up proper server address from server_list config property Change By: Michael Smith Sprint: Puppet 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-6823) Puppet filebucket command does not pick up proper server address from server_list config property
Title: Message Title Michael Smith updated an issue Puppet / PUP-6823 Puppet filebucket command does not pick up proper server address from server_list config property Change By: Michael Smith Team: Agent & Platform Sprint: AP Grooming 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-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Michael Smith updated an issue Puppet / PUP-5609 Puppet apply doesn't protect shared files with a lock Change By: Michael Smith Sprint: Puppet 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-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5609 Puppet apply doesn't protect shared files with a lock 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 (PUP-7203) puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-7203 puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name Change By: Lindsey Smith Team: Puppet Developer Experience 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-7203) puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name
Title: Message Title Rob Nelson created an issue Puppet / PUP-7203 puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name Issue Type: Bug Affects Versions: PUP 4.9.2 Assignee: Unassigned Created: 2017/02/10 12:52 PM Priority: Normal Reporter: Rob Nelson I configured a jenkins job named `freestyle controlrepo` which results in the workspace path of `/var/lib/jenkins/jobs/freestyle controlrepo/workspace/`. When running `bundle exec rake test` , the following error occurs: ``` $ bundle exec rake test ---> syntax:manifests ---> syntax:templates ---> syntax:hiera:yaml Error: puppet module install takes 1 argument, but you gave 3 Error: Try 'puppet help module install' for usage rake aborted! Failed to install module ajjahn/dhcp to spec/fixtures/modules/dhcp /var/lib/jenkins/jobs/freestyle controlrepo/workspace/vendor/ruby/2.1.0/gems/puppetlabs_spec_helper-2.0.1/lib/puppetlabs_spec_helper/rake_tasks.rb:326:in `block (2 levels) in ' /var/lib/jenkins/jobs/freestyle controlrepo/workspace/vendor/ruby/2.1.0/gems/puppetlabs_spec_helper-2.0.1/lib/puppetlabs_spec_helper/rake_tasks.rb:304:in `each' /var/lib/jenkins/jobs/freestyle controlrepo/workspace/vendor/ruby/2.1.0/gems/puppetlabs_spec_helper-2.0.1/lib/puppetlabs_spec_helper/rake_tasks.rb:304:in `block in ' /var/lib/jenkins/jobs/freestyle controlrepo/workspace/vendor/ruby/2.1.0/gems/puppetlabs_spec_helper-2.0.1/lib/puppetlabs_spec_helper/rake_tasks.rb:368:in `block in ' /usr/local/rvm/gems/ruby-2.1.9/gems/bundler-1.14.3/lib/bundler/cli/exec.rb:74:in `load' /usr/local/rvm/gems/ruby-2.1.9/gems/bundler-1.14.3/lib/bundler/cli/exec.rb:74:in
Jira (PUP-7191) Puppet errors when managing non-existent service on AIX
Title: Message Title Moses Mendoza assigned an issue to Branan Riley Puppet / PUP-7191 Puppet errors when managing non-existent service on AIX Change By: Moses Mendoza Assignee: Moses Mendoza 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-7202) excessive INFO logging when files arent found
Title: Message Title
R.I.Pienaar created an issue
Puppet / PUP-7202
excessive INFO logging when files arent found
Issue Type:
Bug
Affects Versions:
PUP 4.8.2
Assignee:
Unassigned
Created:
2017/02/10 11:09 AM
Priority:
Normal
Reporter:
R.I.Pienaar
When one use the common pattern like this:
file{"/foo":
source => ["puppet:///modules/x/foo.${fqdn}", "puppet:///modules/x/foo"]
}
Jira (FACT-1570) Facter errors with "failed to associate process with job object"
Title: Message Title Ethan Brown commented on FACT-1570 Re: Facter errors with "failed to associate process with job object" Some info from SO on access denied errors stemming from AssignProcessToJobObject - https://stackoverflow.com/questions/89588/assignprocesstojobobject-fails-with-access-denied-error-when-running-under-the MSDN docs for AssignProcessToJobObject indicate more sources of access denied. 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-1570) Facter errors with "failed to associate process with job object"
Title: Message Title
Maggie Dreyer updated an issue
Facter / FACT-1570
Facter errors with "failed to associate process with job object"
Change By:
Maggie Dreyer
During an acceptance run, Facter failed on windows2016-6432a with the following error:{ { code} } 2017-02-10 10:50:23.266215 ERROR leatherman.execution:614 - failed to associate process with job object: Access is denied. (5).2017-02-10 10:50:23.266215 WARN puppetlabs.facter - failed to associate process with job object.: facts requiring Ruby will not be resolved.{ { code} } This error appeared in the {{no_errors_on_stderr}} test, right at the beginning of the Facter run.
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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Andrey Galkin commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters ... and definitely, timestamps should not come to play when we generate a new catalog. It's obvious that agent provided data is the actual state. 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Andrey Galkin commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters In my testing, all nodes are synced through ntpdate initially and then through constantly running ntpd against the same source. Time drift is no more than 0.01 seconds. Each puppet agent run takes way much time. Regarding timestamp, also related: #PDB-3248 IMO, it does not look right at all to compare timestamps. I understand, it can be a sort of mitigation for highly available PuppetDB setup, but it would obviously be much safer to have UUID of agent + counter (generation) of facts/resources. 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-1570) Facter errors with "failed to associate process with job object"
Title: Message Title Maggie Dreyer created an issue Facter / FACT-1570 Facter errors with "failed to associate process with job object" Issue Type: Bug Affects Versions: FACT 3.6.1 Assignee: Unassigned Created: 2017/02/10 9:11 AM Priority: Normal Reporter: Maggie Dreyer During an acceptance run, Facter failed on windows2016-6432a with the following error: code 2017-02-10 10:50:23.266215 ERROR leatherman.execution:614 - failed to associate process with job object: Access is denied. (5). 2017-02-10 10:50:23.266215 WARN puppetlabs.facter - failed to associate process with job object.: facts requiring Ruby will not be resolved. code This error appeared in the no_errors_on_stderr test, right at the beginning of the Facter run. Add Comment
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Jeremy Barlow commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Henrik Lindberg, I'm drawing blanks on this but maybe you remember better. I had thought that there might be some code in one of the terminii on the server which compares a timestamp from the agent request to the timestamp of facts that had been previously cached and, if the agent timestamp was sufficiently older, would cause the facts cached on the server to be used instead. Does that ring a bell for you? I wonder in the case of this ticket whether there might have been a significant difference in local time configured on the agent node vs. the two master nodes. If the three were all set to roughly the same time and there were no significant delay in processing the catalog request on the master, would the problem no longer be reproducible? A ticket that seems like it may be related is PUP-3438. It would seem if we were to eliminate the behavior of facts cached on the server being used in lieu of the facts actually provided with the catalog request, that this sort of problem wouldn't occur. 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-7201) Additional certificate attributes should be exposed in trusted hash
Title: Message Title Sean Millichamp created an issue Puppet / PUP-7201 Additional certificate attributes should be exposed in trusted hash Issue Type: New Feature Assignee: Unassigned Components: Platform Created: 2017/02/10 8:43 AM Priority: Normal Reporter: Sean Millichamp The $trusted hash should contain additional certificate attributes. At a minimum 'not_after' and 'not_before' but others such as 'serial' and 'signature_algorithm' might also be useful. Possible use cases for 'not_before' and 'not_after': Examine the 'not_before' date and generate warnings or failures during catalog compilation if required trusted certificate extensions are not present. This allows adding checks for hard extension requirements while allowing backwards compatibility / support for certificates issued prior to a certain time. Examine the 'not_after' date and generate warnings to the user during a Puppet run about an impending client certificate expiration. The times should be stored in something easily machine-consumable or convertable (such as integer values in Unix time).
Jira (PUP-7200) Add "is_virtual" fact for AIX
Title: Message Title Tim Purkerson created an issue Puppet / PUP-7200 Add "is_virtual" fact for AIX Issue Type: New Feature Assignee: Unassigned Created: 2017/02/10 8:41 AM Environment: AIX Priority: Normal Reporter: Tim Purkerson The fact "is_virtual" is not returned on AIX. Would like that fact to be available to the AIX platform. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sh
Jira (PUP-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Erik Dalén commented on PUP-5609 Re: Puppet apply doesn't protect shared files with a lock I rebased my PR for this against the master branch: https://github.com/puppetlabs/puppet/pull/4584 So, there is a fix for this waiting for merge 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-7169) puppet 4.9.0 breaks hiera-eyaml
Title: Message Title
Thomas Hallgren commented on PUP-7169
Re: puppet 4.9.0 breaks hiera-eyaml
Robert Heinzmann, the unit test that for the Hiera version 3 'deep' merge behavior covers this ('deep' maps to 'unconstrained_deep' in version 5). I don't think an acceptance test is necessary.
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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Andrey Galkin commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Guys, it's a race condition, I am quite sure for that: I put delay (breakpoint + wait 10 seconds + continue) between extract_facts_from_request_facts() and node_from_request() in Puppet::Resource::Catalog::Compiler then everything works as expected. /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:51 Now, I wonder if that can be reproduced on single server instance as well... 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-7169) puppet 4.9.0 breaks hiera-eyaml
Title: Message Title Robert Heinzmann commented on PUP-7169 Re: puppet 4.9.0 breaks hiera-eyaml Just one remark - is there a CI test for this test case now ? 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-7170) puppet 4.9.0 breaks existing hiera config
Title: Message Title Robert Heinzmann commented on PUP-7170 Re: puppet 4.9.0 breaks existing hiera config Ok, accepted - however Semantic Versioning is spelled differently. 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Andrey Galkin commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Some more info: I did restart of both PuppetServer and PuppetDB. The issue remains. It seems obvious that by some reason, PuppetServer uses old facts for compilation, but then submits new facts to YAML cache and database. I've specially checked that both PostgreSQL and YAML cache at /opt/puppetlabs/server/data/puppetserver/yaml/facts/cacheissue.example.com.yaml contain value which is not present anywhere on agent's host. So, every run switches the values. Current fact from client goes to database, but PuppetServer uses the previous value for compilation. All packages come from PuppetLabs OpenSource repo. 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.
