salt: service.restart salt-minion fails on Ubuntu 14.04.5 LTS

This fails

salt-call service.restart salt-minion -l all

[DEBUG   ] LazyLoaded file.touch
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 197, in call
    ret['return'] = func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/salt/modules/daemontools.py", line 135, in restart
    if stop(name) and start(name):
  File "/usr/lib/python2.7/dist-packages/salt/modules/daemontools.py", line 90, in stop
    __salt__['file.touch']('{0}/down'.format(_service_path(name)))
  File "/usr/lib/python2.7/dist-packages/salt/modules/file.py", line 2698, in touch
    raise CommandExecutionError(exc.strerror)
CommandExecutionError: No such file or directory
Error running 'service.restart': No such file or directory

Setup

Default Ubuntu 14.04.5 LTS installation

Versions Report

Salt Version:
           Salt: 2016.3.4

Dependency Versions:
           cffi: 0.8.6
       cherrypy: Not Installed
       dateutil: 1.5
          gitdb: Not Installed
      gitpython: Not Installed
          ioflo: 1.3.7
         Jinja2: 2.7.2
        libgit2: Not Installed
        libnacl: 1.4.3
       M2Crypto: Not Installed
           Mako: 0.9.1
   msgpack-pure: 0.1.3
 msgpack-python: 0.4.6
   mysql-python: 1.2.5
      pycparser: 2.10
       pycrypto: 2.6.1
         pygit2: Not Installed
         Python: 2.7.6 (default, Jun 22 2015, 17:58:13)
   python-gnupg: Not Installed
         PyYAML: 3.10
          PyZMQ: 15.2.0
           RAET: 0.6.3
          smmap: 0.8.2
        timelib: 0.2.4
        Tornado: 4.2.1
            ZMQ: 4.1.2

System Versions:
           dist: Ubuntu 14.04 trusty
        machine: x86_64
        release: 3.13.0-100-generic
         system: Linux
        version: Ubuntu 14.04 trusty

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 16 (13 by maintainers)

Commits related to this issue

Most upvoted comments

@PChambino thanks for the replication steps here. Looks like you also go the issue resolved. @githubcdr did you want to check teh fix in #37748 and se if that works for you as well?