FS#50015 - [salt-zmq] [salt-raet] Missing dependencies for salt-ssh

Attached to Project: Community Packages
Opened by Christian (kurisutian) - Monday, 11 July 2016, 11:48 GMT
Last edited by Toolybird (Toolybird) - Saturday, 01 April 2023, 01:57 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Johannes Löthberg (demize)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The following packages are missing for successfully running salt-ssh:

- python2-backports.ssl_match_hostname
- python2-ordereddict
- python2-certifi



Additional info:
* salt-raet and salt-zmq version 2016.3.1-1



Steps to reproduce:
simply run a "salt-ssh '*' test.ping" with Debian 7 servers which don't have salt installed locally. It will show several modules not installed from these missing packages.
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 01 April 2023, 01:57 GMT
Reason for closing:  None
Additional comments about closing:  This is old/stale and python2 is long gone. Refer  FS#77794  for recent salt-ssh issues.
Comment by Sébastien Luttringer (seblu) - Sunday, 07 August 2016, 20:25 GMT
These package/modules are not dependency of upstream provided packages. I don't have salt machines anymore to dig in your proposal, could you explain why these modules must be hard deps on the master because there is missing python modules on a minion less host? Is python like theses modules are not basic requirements?
Comment by Christian (kurisutian) - Wednesday, 10 August 2016, 11:12 GMT
Well, I checked this installation and used salt-ssh which basically wraps a package for a simulated minion and sends it over to the target machine through ssh. In this package all modules exist which are not on the target machine. If the target does not have python installed, this tiny agent should provide it, otherwise the installed python from the target should provide the modules.
I checked with a bare machine with no python installed and it failed because of these modules where required dependencies in the call but were not included in the tiny agent from the machine that runs salt-ssh.
So bottom line: It could not include these dependency modules since they were not installed with the salt package and so it fails once there is no python installed on the target providing these modules. And this should not be the case for salt-ssh operations which are agentless and don't dependencies on the target other than ssh based on the salt devs.

Loading...