Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

salt.modules.upstart.status don't work anymore on non-upstart services #5027

Closed
jeanlucmongrain opened this issue May 15, 2013 · 4 comments
Closed
Assignees
Labels
Bug broken, incorrect, or confusing behavior cannot-reproduce cannot be replicated with info/context provided severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone

Comments

@jeanlucmongrain
Copy link
Contributor

Tested on Ubuntu 12.04 with Salt 0.15.1:

prepare the test:

root@integration-2:~# apt-get install postgresql
[snip]
root@integration-2:~# service postgresql status
Running clusters: 9.1/main
root@integration-2:~# salt-call service.status postgresql
local:
    True

good, what we expect.

root@integration-2:~# service postgresql stop
 * Stopping PostgreSQL 9.1 database server                                                                                                                                               [ OK ]
root@integration-2:~# service postgresql status
Running clusters:
root@integration-2:~# salt-call service.status postgresql
[snip]
local:
    True

fail!

@jeanlucmongrain
Copy link
Contributor Author

this break pretty much all my states for things that use /etc/init.d/ startup script such as, in my case:

  • postgresql
  • elasticsearch
  • rabbitmq
  • ntp
  • nagios
  • denyhosts

and probably more

@basepi
Copy link
Contributor

basepi commented May 15, 2013

Thanks for the report. We'll look into it.

@terminalmage
Copy link
Contributor

I am unable to replicate on 12.04 with the latest code from git:

(saltdev)root@virtubuntu:/home/ejohnson/saltdev# ls -l /etc/init.d/ntp
-rwxr-xr-x 1 root root 1818 Oct 26  2011 /etc/init.d/ntp
(saltdev)root@virtubuntu:/home/ejohnson/saltdev# ls -l /etc/init/ | grep ntp
(saltdev)root@virtubuntu:/home/ejohnson/saltdev# salt-call -c etc/salt service.status ntp
[INFO    ] Configuration file path: /home/ejohnson/saltdev/etc/salt/minion
[INFO    ] Package debconf-utils is not installed.
[INFO    ] Executing command 'service ntp status' in directory '/root'
local:
    True
(saltdev)root@virtubuntu:/home/ejohnson/saltdev# salt-call -c etc/salt service.stop ntp

[INFO    ] Configuration file path: /home/ejohnson/saltdev/etc/salt/minion
[INFO    ] Package debconf-utils is not installed.
[INFO    ] Executing command 'service ntp stop' in directory '/root'
local:
    True
(saltdev)root@virtubuntu:/home/ejohnson/saltdev# salt-call -c etc/salt service.status ntp
[INFO    ] Configuration file path: /home/ejohnson/saltdev/etc/salt/minion
[INFO    ] Package debconf-utils is not installed.
[INFO    ] Executing command 'service ntp status' in directory '/root'
local:
    False

Do you have the ability to test against git?

@ghost ghost assigned terminalmage Jun 6, 2013
@terminalmage
Copy link
Contributor

I tested this on 12.04 LTS with the most recent official release (0.15.3) and was also not able to reproduce this. I'm going to mark the issue as closed, as it appears to have been fixed between 0.15.1 and 0.15.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior cannot-reproduce cannot be replicated with info/context provided severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Projects
None yet
Development

No branches or pull requests

3 participants