Jira (PUP-7813) Yum package provider: ensure => latest fails when packages update available
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7813 Yum package provider: ensure => latest fails when packages update available Change By: Geoff Nichols Sprint: Platform OS 2017-08-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 (FACT-1734) Add a system profiler data source to detect hypervisors in MacOS
Title: Message Title Casey Williams updated an issue Facter / FACT-1734 Add a system profiler data source to detect hypervisors in MacOS Change By: Casey Williams Sprint: Platform OS 2017-08-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 (FACT-1734) Add a system profiler data source to detect hypervisors in MacOS
Title: Message Title Casey Williams created an issue Facter / FACT-1734 Add a system profiler data source to detect hypervisors in MacOS Issue Type: Task Assignee: Casey Williams Created: 2017/08/18 3:25 PM Priority: Normal Reporter: Casey Williams SMBIOS is not usable under MacOS, but the system_profiler's SPHardwareDataType object contains some useful information: boot_rom_version model_identifier system_serial_number I haven't found anything useful outside of these, but they should be enough to confirm VirtualBox and VMware at least. Add Comment
Jira (PUP-7830) Adding a user with a numeric group name fails
Title: Message Title Adam Bottchen commented on PUP-7830 Re: Adding a user with a numeric group name fails This is a limitation in the useradd tool provided by the OS, not a bug in Puppet. As specified in the documentation, Puppet uses OS supplied tools to manage users and groups. In this case, that means the use of useradd. Unfortunately, regardless of POSIX standards, useradd does not support supplementary groups that start with a digit: # grep 123 /etc/group 123:x:502: # /usr/sbin/useradd -G 123 -M testuser useradd: group '123' does not exist This is the command the user provider on EL distros will use, so our regex is merely preventing one from running into the limitation of the useradd command. If the regex at https://github.com/puppetlabs/puppet/blob/4.10.x/lib/puppet/type/user.rb#L288 were removed, the Puppet run would just fail on the useradd command itself with the error above. In general it is discouraged to have user or group names that are entirely numeric just from a system administration standpoint. That said, if existing account data requires it, a different resource will be needed to manage it. For example, an augeas or file_line resource against /etc/group, or an exec directly modifying it. Until the underlying useradd system tool provides this functionality, the Puppet user provider will be limited by it. Add Comment
Jira (PUP-5068) Windows - Allow logging to a different event log
Title: Message Title Ethan Brown commented on PUP-5068 Re: Windows - Allow logging to a different event log Yeah, we've tossed that idea around Rob Reynolds. That incurs a bit of work with reading the INI during upgrade, etc if we intend to also allow it be specified at the command line as an MSI property. The other snag there is that if the configured user doesn't have access to create the event log, then that's a problem - but maybe that's rare and worthy of just a warning because the typical configuration should 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-7813) Yum package provider: ensure => latest fails when packages update available
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7813 Yum package provider: ensure => latest fails when packages update available Change By: Kenn Hussey Fix Version/s: PUP 5.2.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 (FACT-1728) facter -p dies with an inscrutable error if puppet crashes
Title: Message Title Scott McClellan assigned an issue to qa Facter / FACT-1728 facter -p dies with an inscrutable error if puppet crashes Change By: Scott McClellan Status: Ready for CI Test Assignee: Scott McClellan 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-7511) Test puppet-agent against FIPS-compliant system openssl library
Title: Message Title Trevor Vaughan commented on PUP-7511 Re: Test puppet-agent against FIPS-compliant system openssl library Jayant Sane Apologies for not getting back to you on this sooner. We tested your build and it DOES work. We had no issues, and we did validate that it was properly linked against the OS libraries. 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-7813) Yum package provider: ensure => latest fails when packages update available
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-7813 Yum package provider: ensure => latest fails when packages update available Change By: Eric Sorenson Fix Version/s: PUP 4.10.7 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title Thomas Kishel commented on PUP-6966 Re: Tidy and File cannot remove fifo or socket files Yay! Thanks 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-7618) PSON -> JSON Testing
Title: Message Title John Duarte commented on PUP-7618 Re: PSON -> JSON Testing Waiting on tests associated with subtasks to be merged. 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-1667) Add support for hyperv virtualization detection
Title: Message Title Geoff Nichols assigned an issue to Branan Riley Facter / FACT-1667 Add support for hyperv virtualization detection Change By: Geoff Nichols Assignee: Casey Williams 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 (FACT-1663) Add support for xen virtualization detection
Title: Message Title Geoff Nichols assigned an issue to Branan Riley Facter / FACT-1663 Add support for xen virtualization detection Change By: Geoff Nichols Assignee: Scott McClellan 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-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title John Duarte commented on PUP-6966 Re: Tidy and File cannot remove fifo or socket files No further testing required. I have resolved. 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-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title John Duarte updated an issue Puppet / PUP-6966 Tidy and File cannot remove fifo or socket files Change By: John Duarte QA Risk Assessment: Manual 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-7830) Adding a user with a numeric group name fails
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-7830 Adding a user with a numeric group name fails Change By: Adam Bottchen CS Priority: Needs Priority Reviewed CS Impact: This is actively blocking a customer from deploying due to the fact they use numbers for group names CS Severity: 5 - Critical CS Business Value: 1 - ? CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are
Jira (PUP-7645) Ensure that translations are available in released puppet gems
Title: Message Title Kenn Hussey commented on PUP-7645 Re: Ensure that translations are available in released puppet gems Ah, makes sense. Thanks, Maggie Dreyer! 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-7645) Ensure that translations are available in released puppet gems
Title: Message Title Maggie Dreyer commented on PUP-7645 Re: Ensure that translations are available in released puppet gems I think rather the epics need to be retargeted. Phase 3 should be 5.y, Phase 2 should be 5.2, as it is intended to contain things we wanted to get into Hoyt. PA-1104 should likewise be in Phase 2 and targeted at 5.2, since it only got merged yesterday (and didn't make it into 5.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-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title Maggie Dreyer commented on PUP-6966 Re: Tidy and File cannot remove fifo or socket files Confirmed this went out in 5.1.0, so it has cleared CI. Moving. 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-7645) Ensure that translations are available in released puppet gems
Title: Message Title Kenn Hussey commented on PUP-7645 Re: Ensure that translations are available in released puppet gems Maggie Dreyer should this issue be moved to PA-1273 (targeted for 5.2) so that PA-1104 (targeted for 5.1) can be closed? 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-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title Kenn Hussey commented on PUP-6966 Re: Tidy and File cannot remove fifo or socket files Erik Dasher is the build available yet (now that 5.1 has shipped) or does this issue need a different fix version? 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-7678) Add functions 'all' and 'any'
Title: Message Title Kenn Hussey commented on PUP-7678 Re: Add functions 'all' and 'any' Erik Dasher can this be resolved? 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-7851) puppet module build: packs source file permissions into the tarball
Title: Message Title
Kevin Reeuwijk updated an issue
Puppet / PUP-7851
puppet module build: packs source file permissions into the tarball
Change By:
Kevin Reeuwijk
When running {{puppet module build}} on a module the existing permissions on the files and directories are inherited into the tarball. If the source permissions are restrictive (0640 in my case), and the module gets deployed onto target systems using r10k (or similar tools) the resulting module installation exhibits surprising/unexpected behaviour. Especially when the deployment user is not the same as the user running the puppet master (e.g. r10k and foreman), the end-user has to add more scripting to workaround this.Leaking source permissions into the tarball is undesired from both a compatibility and a security perspective.Annoyingly, if the module is downloaded from Github is it does work, as Github doesn't inherit permissions. That's something all the components relating to the Forge should do as well.Fixing this will require multiple approaches:* Updating the puppet module face to insure 'puppet module build' creates a tarball without permissions inherited (all files 0644, all directories 0755, all uid/gids 0/0)* Updating the Forge so it will at least check tarballs for source permissions more restrictive than 0644 and report this back to the module's owner.* Updating documentation on this issue, and how to resolve it* Updating r10k to enforce consistent permissions on deployment of modules from any source.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You
Jira (PUP-7848) Capitals in variable names in EPP templates hang threads forever
Title: Message Title Henrik Lindberg commented on PUP-7848 Re: Capitals in variable names in EPP templates hang threads forever Nacho Barrientos I think it is worth discussing first on puppet-dev mailing list. If that results in a workable approach then do add a ticket. 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-7848) Capitals in variable names in EPP templates hang threads forever
Title: Message Title Nacho Barrientos commented on PUP-7848 Re: Capitals in variable names in EPP templates hang threads forever BTW, I'd like to take the opportunity to ask something. Is there any kind of watchdog that can be configured at puppetserver level to automatically destroy instances that are misbehaving like these ones (perhaps based on the CPU wall time, age...)? We're already using over here max-requests-per-instance but for obvious reasons it's not useful in this case. Bugs like this one are quite dangerous and can quickly degrade the performance of a production system. The more agents exercising the bad code and triggering the issue, the faster the load goes up. There should be a way to tell Puppetserver how to protect itself. Should I open a separate ticket 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 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-7851) puppet module build: packs source file permissions into the tarball
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-7851
puppet module build: packs source file permissions into the tarball
Copy-editing, and a little bit of adjustment of the text. This will need more grooming, and ticketing out subtasks to their respective teams.
cc Eric Sorenson
Change By:
David Schmitt
Acceptance Criteria:
Fixing this will require multiple approaches:* Updating Puppet to insure 'puppet module build' creates a tarball without permissions inherited* Updating the Forge so it will at least check tarballs for source permissions more restrictive than 0644 and report this back to the module's owner.* Updating documentation on this issue and how to resolve it* Updating r10k to strip existing permissions from modules received from the Forge
Summary:
Puppet puppet module build : packs source file permissions into the tarball
When running ' {{ puppet module build ' }} on a module the existing permissions on the files and directories are inherited into the tarball. If the source permissions are restrictive (0640 in my case), and the module gets deployed onto target systems using r10k (or similar tools) the resulting Forge module ends up inaccessible for installation exhibits surprising/unexpected behaviour. Especially when the deployment user is not the same as the user running the puppet master (e.g. r10k and Foreman in POSS foreman), the end-user has to add more scripting to workaround this .Leaking source permissions into the tarball is undesired from both a compatibility and a security perspective.Annoyingly, if the module is downloaded from Github is does work, as Github doesn't inherit permissions. That's something all the components relating to the Forge should do as well. Fixing this will require multiple approaches:* Updating the puppet module face to insure 'puppet module build' creates a tarball without permissions inherited (all files 0644, all directories 0755, all uid/gids 0/0)* Updating the Forge so it will at least check tarballs for source permissions more restrictive than 0644 and report this back to the module's owner.* Updating documentation on this issue, and how to resolve it* Updating r10k to enforce consistent permissions on deployment of modules from any source.
Jira (PUP-7851) Puppet module build packs source file permissions into the tarball
Title: Message Title David Schmitt moved an issue Puppet / PUP-7851 Puppet module build packs source file permissions into the tarball Change By: David Schmitt Key: FORGE PUP - 391 7851 Project: Puppet Forge 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-7850) Add plan to puppet language
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-7850 Add plan to puppet language Issue Type: New Feature Assignee: Unassigned Created: 2017/08/18 4:08 AM Priority: Normal Reporter: Henrik Lindberg placeholder Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) --
Jira (PUP-7850) Add plan to puppet language
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-7850 Add plan to puppet language Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7760) Array to String formatter adds a trailing space to a separator
Title: Message Title Henrik Lindberg commented on PUP-7760 Re: Array to String formatter adds a trailing space to a separator This must have passed CI by now. Is it in 5.1.x branch? 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-7848) Capitals in variable names in EPP templates hang threads forever
Title: Message Title Henrik Lindberg commented on PUP-7848 Re: Capitals in variable names in EPP templates hang threads forever Merged to 4.10.x - not yet merged to any 5.x branches as there seems to be some kind of traffic accident ... 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-7849) Error "\xC3" on US-ASCII when puppetmasters stars first time
Title: Message Title Henrik Lindberg commented on PUP-7849 Re: Error "\xC3" on US-ASCII when puppetmasters stars first time Not sure how to help you with this. Puppet 3.x has reached EOL - there will be no more releases in the 3.x series. In puppet 4 and 5 there has been a lot of work related to both unicode and binary data. It is hard to say if the problem you have run into here is fixed specifically since there is no way to reproduce the problem. Hence, the only suggestion I can offer is to upgrade to puppet 4 (or 5). If you can find a reproducer it is of value to test that on later puppet so we can fix the problem. For now I am going to close this ticket as Incomplete. If there is more information that we can act on, please reopen. 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-7849) Error "\xC3" on US-ASCII when puppetmasters stars first time
Title: Message Title Emilio created an issue Puppet / PUP-7849 Error "\xC3" on US-ASCII when puppetmasters stars first time Issue Type: Bug Assignee: Unassigned Components: Puppet Server Created: 2017/08/18 1:31 AM Environment: Using Foreman 1.15.3 Puppetmaster 3.8.7 puppet client 3.8.7 Priority: Normal Reporter: Emilio When puppetmaster starts first time (with a reboot) , it's not working web, a lot of errors: 09:59:27 puppet-pre puppet-master[1599]: (at /usr/lib/ruby/vendor_ruby/pu ppet/settings.rb:1141:in `issue_deprecation_warning') Aug 18 09:59:28 puppet-pre puppet-master[1620]: Reopening log files Aug 18 09:59:28 puppet-pre puppet-master[1620]: Starting Puppet master version 3.8. 7 Aug 18 09:59:43 puppet-pre puppet-master[1620]: Removing mount "war_files": /WAR do es not exist or is not a directory Aug 18 09:59:43 puppet-pre puppet-master[1620]: Removing mount "filecopy_data": /FI LES does not exist or is not a directory Aug 18 09:59:43 puppet-pre puppet-master[1620]: "\xC3" on US-ASCII Aug 18 09:59:43 puppet-pre puppet-master[1620]: "\xC3" on US-ASCII Aug 18 09:59:44 puppet-pre puppet-master[1620]: "\xC3" on US-ASCII Aug 18 09:59:44 puppet-pre puppet-master[1620]: "\xC3" on US-ASCII but if you stop it manualy and restarts, it works correctly.
