[Neon] salt-support is broken
Open
@dwoz is already working on this.
Since Jun 25, 2020.
bug
Confirmed
severity-high
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description of Issue
New salt-support feature has a few problems (there could be more, but it is hard to extensively test a broken feature):
- The default profiles https://github.com/saltstack/salt/tree/develop/salt/cli/support/profiles aren't installed by the setup.py script, so the tool is not very usable out of the box
- When I tried to run the command, it produced a lot of exceptions (at least on python3.6):
Error: Unhandled exception occurred 'master' - It doesn't run as non-root user: "No permissions to access "/var/log/salt/master", are you running as the correct user?"
- No documentation whatsoever, and also no mention in the release notes: https://docs.saltstack.com/en/develop/topics/releases/neon.html
Versions Report
sudo salt-master --versions-report
Salt Version:
Salt: 2019.2.0-n/a-a95d03d
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: Not Installed
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 2.10
libgit2: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 3.6.8 (default, Aug 20 2019, 17:12:48)
python-gnupg: Not Installed
PyYAML: 3.12
PyZMQ: 16.0.2
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.2.5
System Versions:
dist: Ubuntu 18.04 bionic
locale: UTF-8
machine: x86_64
release: 4.15.0-29-generic
system: Linux
version: Ubuntu 18.04 bionic
P.S. I understand that Salt Neon is not yet stabilized, but I decided to report this anyway when I saw a few critical errors got backported to 2019.2.1
CC: @meaksh
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.