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

[BUG] service.running generates unnecessary warning. #58171

Open
sergeyfd opened this issue Aug 11, 2020 · 0 comments
Open

[BUG] service.running generates unnecessary warning. #58171

sergeyfd opened this issue Aug 11, 2020 · 0 comments
Labels
Bug broken, incorrect, or confusing behavior severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone

Comments

@sergeyfd
Copy link
Contributor

sergeyfd commented Aug 11, 2020

Description
service.running generates unnecessary warning.

Setup
(Please provide relevant configs and/or SLS files (be sure to remove sensitive info).

On a system that supports systemd use something like this:

service.running:
  - name: my_service
  - no_block: True 

Steps to Reproduce the behavior

Try to apply state from above

Expected behavior
You will get a warning that 'no_block' is not supported for this system/action

Versions Report
salt 3000.2

Additional context
The reason for the warning are calls like this one:

status_kwargs, warnings = _get_systemd_only(__salt__["service.status"], kwargs)
@sergeyfd sergeyfd added the Bug broken, incorrect, or confusing behavior label Aug 11, 2020
@sagetherage sagetherage changed the title [BUG] [BUG] service.running generates unnecessary warning. Aug 12, 2020
@sagetherage sagetherage added severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around and removed needs-triage labels Sep 23, 2020
@sagetherage sagetherage added this to the Approved milestone Sep 23, 2020
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 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