Skip to content

timeout errors for salt calls should return an exit code other than 0 #47235

@jf

Description

@jf

Description of Issue/Question

I have salt set up to run in a CI tool, and the problem is that when salt is unable to reach a minion, or has a timeout for some reason, the status code returned is 0, which results in the CI tool not detecting it as an error.

salt unreachable-or-down-minon test.ping; echo $?

Versions Report

(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)

I do not believe this has changed in the latest version, but fyi:

Salt Version:
           Salt: 2017.7.4

Dependency Versions:
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: 2.4.2
      docker-py: Not Installed
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: 1.0.3
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: Not Installed
      pycparser: Not Installed
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: Not Installed
         Python: 2.7.12 (default, Dec  4 2017, 14:50:18)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.1.4

System Versions:
           dist: Ubuntu 16.04 xenial
         locale: UTF-8
        machine: x86_64
        release: 4.4.0-109-generic
         system: Linux
        version: Ubuntu 16.04 xenial

Metadata

Metadata

Assignees

Labels

fixed-pls-verifyfix is linked, bug author to confirm fix

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions