Package: salt-ssh Version: 2018.3.4+dfsg1-6 Severity: normal Under stretch, I used salt-ssh without salt-master to manage a handful of hosts. After upgrading to buster, I ran into this error:
$ sudo salt-ssh ravenhurst --verbose -l debug test.ping [DEBUG ] Missing configuration file: /etc/salt/master [DEBUG ] Using cached minion ID from /etc/salt/minion_id: vanvanmojo Failed to prepare the Salt environment for user salt. The user is not available. The salt user is created by salt-master (though I ran into #930178 the first time I tried to install). Once I got salt-master installed, the user existed and salt-ssh could work again. Should salt-ssh depend on salt-master now? Ross -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable'), (40, 'unstable'), (30, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages salt-ssh depends on: ii python3 3.7.3-1 ii salt-common 2018.3.4+dfsg1-6 salt-ssh recommends no packages. salt-ssh suggests no packages. -- Configuration Files: /etc/salt/roster changed [not included] -- no debconf information