Ask questionsarchive.extracted still fails with `UnicodeEncodeError`s

Description of Issue

as per subject, archive.extracted still fails with UnicodeEncodeErrors. I see #40578, #47546, #48684 that claim that this has been fixed, but I'm still getting it, with 2019.2.3.

IF it matters, I'm using salt-ssh instead of the regular salt. I'm hoping it shouldn't matter... but if it does, boo!

          ID: extract erlang
    Function: archive.extracted
        Name: /home/vagrant
      Result: False
     Comment: An exception occurred in this state: Traceback (most recent call last):
                File "/var/tmp/.vagrant_0b764e_salt/pyall/salt/", line 1933, in call
                File "/var/tmp/.vagrant_0b764e_salt/pyall/salt/", line 1951, in wrapper
                  return f(*args, **kwargs)
                File "/var/tmp/.vagrant_0b764e_salt/pyall/salt/states/", line 1116, in extracted
                  path_mode = os.lstat(full_path.rstrip(os.sep)).st_mode
              UnicodeEncodeError: 'ascii' codec can't encode characters in position 79-80: ordinal not in range(128)
     Started: 12:36:51.336438
    Duration: 3000.088 ms


extract erlang:
    - name: /home/{{ compile_user }}
    - source: salt://erl/otp_src_{{ otp_version }}.tar.gz
    - source_hash: {{ otp_tarball_hash }}
    - user: {{ compile_user }}

Steps to Reproduce Issue

Use the state file, and try to extract

Versions Report

Salt Version:
           Salt: 2019.2.3

Dependency Versions:
           cffi: 1.12.2
       cherrypy: unknown
       dateutil: 2.8.0
      docker-py: Not Installed
          gitdb: 2.0.6
      gitpython: 2.1.11
          ioflo: Not Installed
         Jinja2: 2.10.1
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: 1.0.7
   msgpack-pure: Not Installed
 msgpack-python: 0.5.6
   mysql-python: Not Installed
      pycparser: 2.19
       pycrypto: 3.8.1
   pycryptodome: Not Installed
         pygit2: Not Installed
         Python: 2.7.15 (default, Jan  7 2020, 18:15:51)
   python-gnupg: 0.4.4
         PyYAML: 3.13
          PyZMQ: 18.0.1
           RAET: Not Installed
          smmap: 2.0.5
        timelib: 0.2.4
        Tornado: 4.5.3
            ZMQ: 4.3.1

System Versions:
         locale: UTF-8
        machine: x86_64
        release: 19.3.0
         system: Darwin
        version: 10.15.3 x86_64

Answer questions jf

I see. Thanks for the response, @waynew . Thank you for the note about Python 2 support. I use Ubuntu 18.04 VMs, and I've had issues getting salt-ssh to work with them right out of the box, and resorted to installing python2.7-minimal for salt-ssh to work. python3-minimal is already installed by default, but without python2.7-minimal (?) I still get problems:

$ salt-ssh -i vm-new
[ERROR   ] ERROR: Failure deploying thin, retrying:


        ERROR: Python version error. Recommendation(s) follow:
        Install Python 2.6 / Python 3 Salt dependencies on the Salt SSH master
        to interact with Python 2.6 / Python 3 targets

Why should python2.7-minimal be ok, but not python3-minimal?


Related questions

Neon: name 'pip' is not defined hot 1
Typos/missing spaces in grains/ get_server_id() hot 1
Proxy minion startup problem hot 1
GPG Decryption Failed hot 1
salt-api authentication denied (http 401 is returned) using runner module hot 1
salt-master on CentOS 7 using the Python 3 packages cannot use pygit2 via normal means hot 1
GitFS locking issues hot 1
Fix this warning please. hot 1
Salt Master 2018.3.4 on Debian 9 with Python3 - Can't use gitfs at all hot 1
x509.sign_remote_certificate not working after upgrade to 2019.2.0 hot 1
win_wua.<anything> tracebacks on some computers hot 1
2019.2.1: Warning: zmq.eventloop.minitornado is deprecated in pyzmq 14.0 and will be removed hot 1
Could "pip3 install salt" break the existing salt installation? hot 1
Log filled with "Exception occurred while Subscriber handling stream: Already reading" hot 1
salt state 'pkg.install' was not found in SLS - windows os hot 1
Github User Rank List