salt: [BUG] Minion and master report different saltversions
Description
On a master (ubuntu 20.04, 3006.9 salt packages installed) if I run “salt ‘*’ grains.get saltversion” The responses are all as expected. But on a minion, if I run salt-call grains.get saltversion I get a different, incorrect response.
Also, on the master, salt --version returns 3007.1, despite 3006.9 being installed.
Setup Just recently upgraded from 3002.8 to 3006.9 (big jump, yes, I know.)
Please be as specific as possible and give set-up details.
- [ x] on-prem machine
- [ x] VM (Virtualbox, KVM, etc. please specify)
- 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
- [x ] classic packaging
- onedir packaging
- used bootstrap to install
Steps to Reproduce the behavior On master: saltmaster1:~# salt-call grains.get saltversion local: 3007.1
saltmaster1:~# salt ‘saltmaster1*’ grains.get saltversion saltmaster1.peak6.net: 3006.9
saltmaster1:~# salt --version salt 3007.1 (Chlorine)
saltmaster1:~# dpkg -l | grep salt ii salt-api 3006.9 amd64 Generic, modular network access system ii salt-common 3006.9 amd64 shared libraries that salt requires for all packages ii salt-master 3006.9 amd64 remote manager to administer servers via salt ii salt-minion 3006.9 amd64 client package for salt, the distributed remote execution system
Expected behavior All of the above commands should return 3006.9
Screenshots If applicable, add screenshots to help explain your problem.
Versions Report salt --versions-report Salt Version: Salt: 3007.1
Python Version: Python: 3.8.10 (default, Mar 25 2024, 10:42:49)
Dependency Versions: cffi: 1.17.1 cherrypy: 18.10.0 dateutil: 2.9.0.post0 docker-py: Not Installed gitdb: 2.0.6 gitpython: 3.0.7 Jinja2: 2.10.1 libgit2: Not Installed looseversion: 1.3.0 M2Crypto: Not Installed Mako: Not Installed msgpack: 1.1.0 msgpack-pure: Not Installed mysql-python: Not Installed packaging: 24.2 pycparser: 2.22 pycrypto: 2.6.1 pycryptodome: 3.21.0 pygit2: Not Installed python-gnupg: 0.5.3 PyYAML: 5.3.1 PyZMQ: 26.2.0 relenv: Not Installed smmap: 2.0.5 timelib: 0.3.0 Tornado: 6.4.1 ZMQ: 4.3.5
Salt Package Information: Package Type: Not Installed
System Versions: dist: ubuntu 18.04.2 focal locale: utf-8 machine: x86_64 release: 5.4.0-164-generic system: Linux version: Ubuntu 18.04.2 focal
PASTE HERE
Additional context Add any other context about the problem here.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 17 (1 by maintainers)
looking at that it looks like they did have a pip installed version. which could account for the random update to 3007.1 when they ran the pip install saltext-vault. as I’m sure you have salt as a dependency of vault and it would have tried to install the latest compatible version. the call script in /usr/local does point to a pip installed version of salt as well. pip within a venv.
it is possible someone did something similar here. ran pip install instead of salt-pip install for something that required salt. such as libpepper. or a saltext. which would pull in the latest version of salt into the environment that hosts pip. the pip installed version would overwrite the call scripts making it the default version.
there were problems with straight updating from nononedir to onedir without uninstalling first. but they were not the package being installed into the system python which it can’t do. they were more along the lines of being unable to start salt as incompatible versions were fighting over the call scripts. and libraries being confused.
but agree. the directions given would fix it.