Remote crontabs for Tools that are invalid cause issues for the entire host
https://phabricator.wikimedia.org/source/toollabs/browse/master/misctools/oge-crontab
root@tools-bastion-03:~# become zhuyifei1999-test tools.zhuyifei1999-test@tools-bastion-03:~$ crontab -e Traceback (most recent call last): File "/usr/local/bin/crontab", line 337, in <module> main() File "/usr/local/bin/crontab", line 280, in main crontab_text = crontab.load() File "/usr/local/bin/crontab", line 120, in load return self._remote('-l') File "/usr/local/bin/crontab", line 94, in _remote stdoutdata, stderrdata = ssh.communicate(input=stdin) File "/usr/lib/python3.4/subprocess.py", line 960, in communicate stdout, stderr = self._communicate(input, endtime, timeout) File "/usr/lib/python3.4/subprocess.py", line 1659, in _communicate self.stdout.encoding) File "/usr/lib/python3.4/subprocess.py", line 888, in _translate_newlines data = data.decode(encoding) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf3 in position 10: invalid continuation byte
It seems there is some kind of issue with this instance, and the puppet catalog can't be applied here:
tools-cron-01.tools.eqiad.wmflabs: Error: Failed to apply catalog: Could not parse line "PATH=/usr/local/bin:/usr/bin:/bin" at tools.ato:2 clush: tools-cron-01.tools.eqiad.wmflabs: exited with exit code 1