Jira (PUP-7467) Puppet removes non-managed entries from crontabs if non-ascii character found

[Larsen (JIRA)]

Title: Message Title

Larsen created an issue   Puppet / PUP-7467 Puppet removes non-managed entries from crontabs if non-ascii character found Issue Type: Bug Assignee: Unassigned Created: 2017/04/25 5:26 AM Environment: Debian Jessie puppet 3.7.2-4 Priority: Normal Reporter: Larsen I have three crontab files (root, nobody, www-data) that are managed by Puppet. There are additional entries in some of those files that are not managed by Puppet. One of those three crontabs (nobody) contains a German umlaut like "ö". When Puppet normally runs, it is using a UTF-8 locale and there will be no problems. This time however, Puppet was started via "salt cmd.run" which is resetting the locale to "C" (s. https://github.com/saltstack/salt/issues/19776). This led to this error message: Error: Puppet::Util::FileType::FileTypeCrontab could not read www-data: invalid byte sequence in US-ASCII Error: Could not prefetch cron provider 'crontab': Puppet::Util::FileType::FileTypeCrontab could not read www-data: invalid byte sequence in US-ASCII Afterwards, the crontab files only contained the entries that are managed by Puppet (all of them, not only for "nobody"!). All the other ones had been removed. Did not find the old version in the file bucket and had to restore from backup. 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.