-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Open
Labels
RegressionThe issue is a bug that breaks functionality known to work in previous releases.The issue is a bug that breaks functionality known to work in previous releases.Salt-SSHbugbroken, incorrect, or confusing behaviorbroken, incorrect, or confusing behavior
Milestone
Description
Description
When I set the thin_dir of a roster host, I can execute state commands:
salt-ssh test-machine-1 state.show_top
[ERROR ] An Exception occurred while executing state.show_top: [Errno 13] Permission denied: '/root/.cache'
test-machine-1:
An Exception occurred while executing state.show_top: [Errno 13] Permission denied: '/root/.cache'
Setup
Here is my salt-ssh personal configuration:
~/.salt/Saltfile
# -*- yaml -*-
salt-ssh:
config_dir: ~/.salt
~/.salt/master
# -*- mode: yaml; coding: utf-8 -*-
####
#### Global parameters
####
# Unfortunately, salt does not support ~ expension
# We need to use absolute path for `root_dir`
root_dir: /home/me/.salt
pki_dir: pki
cachedir: cache
sock_dir: run
pidfile: pids
log_file: logs/master.log
key_logfile: logs/key.log
# Global level logged in file
log_level_logfile: error
# Unfortunately, salt does not support ~ expension
# We need to use absolute path for `file_roots` and `pillar_roots`
file_roots:
base:
- /home/me/.salt/srv/salt/
pillar_roots:
base:
- /home/me/.salt/srv/pillar/
####
#### Salt-SSH specific configuration
####
ssh_minion_opts:
log_level: debug
ssh_log_file: logs/ssh.log
ssh_use_home_key: True
ssh_timeout: 5
roster_defaults:
# Use ssh-agent authentication
priv: agent-forwarding
~/.salt/roster
test-machine-1:
host: 192.168.0.100
user: root
thin_dir: .cache/salt/thin
Please be as specific as possible and give set-up details.
- on-prem machine
- VM (KVM)
- VM running on a cloud service, please be explicit and add details
- container (Kubernetes, Docker, containerd, etc. please specify)
- or a combination, please be explicit
- jails if it is FreeBSD
- classic packaging
- onedir packaging
- used bootstrap to install
Steps to Reproduce the behavior
Create the salt-ssh
configuration, no need of any top.sls
or existing states.
Expected behavior
The state.show_top
should return an empty dict
:
salt-ssh test-machine-1 state.show_top --output yaml
test-machine-1: {}
Screenshots
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Salt Version:
Salt: 3006.2
Python Version:
Python: 3.10.12 (main, Aug 3 2023, 21:47:10) [GCC 11.2.0]
Dependency Versions:
cffi: 1.14.6
cherrypy: 18.6.1
dateutil: 2.8.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 3.1.2
libgit2: 1.6.4
looseversion: 1.0.2
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.2
msgpack-pure: Not Installed
mysql-python: Not Installed
packaging: 22.0
pycparser: 2.21
pycrypto: Not Installed
pycryptodome: 3.9.8
pygit2: 1.12.1
python-gnupg: 0.4.8
PyYAML: 6.0.1
PyZMQ: 23.2.0
relenv: 0.13.3
smmap: Not Installed
timelib: 0.2.4
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: debian n/a trixie
locale: utf-8
machine: x86_64
release: 6.4.0-4-amd64
system: Linux
version: Debian GNU/Linux n/a trixie
Additional context
This is a reopen of #46891 which is still valid for 3006.2
.
I made different tests:
/var/cache/salt/thin
is not working but the directory is created and populated/tmp/thin
is working
vladimir-lu and vvrein
Metadata
Metadata
Assignees
Labels
RegressionThe issue is a bug that breaks functionality known to work in previous releases.The issue is a bug that breaks functionality known to work in previous releases.Salt-SSHbugbroken, incorrect, or confusing behaviorbroken, incorrect, or confusing behavior