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

Steampipe service incorrectly says service stopped when using --force command even if service isn't running #1456

Closed
cbruno10 opened this issue Feb 15, 2022 · 0 comments · Fixed by #1775
Assignees
Labels
bug Something isn't working
Milestone

Comments

@cbruno10
Copy link
Contributor

Describe the bug
If the service is not running, when running steampipe service stop --force, it displays the message Steampipe service stopped; however, in the same situation without the --force command, it says Service is not running.

Steampipe version (steampipe -v)
v0.13.0-alpha.7

To reproduce
Stop any running Steampipe services, then run:

cbruno@M1P insightsaws % steampipe service stop --force

Expected behavior
Steampipe should say the service is not running

Additional context

cbruno@M1P insightsaws % steampipe service status
Service is not running
cbruno@M1P insightsaws % steampipe service stop
Steampipe service is not running.
cbruno@M1P insightsaws % steampipe service stop --force
Steampipe service stopped.
@cbruno10 cbruno10 added the bug Something isn't working label Feb 15, 2022
@binaek binaek self-assigned this Apr 1, 2022
@kaidaguerre kaidaguerre added this to the april_8 milestone Apr 1, 2022
kaidaguerre pushed a commit that referenced this issue Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants