-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
state_output option being ignored, salt 2018.3.3 #51090
Comments
im not able to replicate this. Did you restart the master after adding this configuration change? also do you see this behavior with all states or just this one? |
Hey @Ch3LL, thanks for the response. Indeed I do restart after making configuration changes, and this behavior is seen on all state files. I think I managed to identify what was causing the issue, in my configuration file |
glancing at teh code here: https://github.com/saltstack/salt/blob/v2018.3.3/salt/output/__init__.py#L142 it looks like it would grab that option there,but i think this still would be considered a bug as state_output and output are different and should work together. |
Same problem for 2019.2.0 in test mode; perhaps it is wrong fixed already (is/was working for me till 2018.3.4) ? Independent of my default usage of This example is from a fresh 2019.2.0 only instance with an additional empty line for showing the bug with a trivial state:
It's always amazing how untested even newly announced Saltstack features are... |
@Reiner030 this issue is related to using both
Going forward our main focus within salt is stability. We are now requiring all bug fixes and features to require test coverage, whereas previously this was not a requirement. We also will not merge a PR into the repo unless all tests have passed, even if the test failure is not related to the change. In the past we would merge a PR if the test failure was not related. This will ensure our test suite is consistently stable and that should mirror into the stability of salt's code base. Furthermore our goal is to run all OSs we currently run on branch tests against PRs. This will help us to catch things sooner than later. All of these changes will help ensure that in our future releases there will be more stability. Hopefully that helps ease some of your concerns for the future. |
@Ch3LL I have exactly the same issue with output for highstate but in my case it started after upgrade from So currently when I execute:
I will see output similar to this:
When I will apply single state:
I will see this output:
I'm not configuring
|
im having a hard time replicating your test case @dawidmalina
I know that we made some fixes related to the outputer that will be coming out on 2019.2.1. Any chance you can give the 2019.2.1 branch a try? |
Thx @Ch3LL I will give it a try and I will test new branch. In addition I will try to prepare some test environment in docker. |
@Ch3LL sorry for such a long delay. During test environment preparation we found issue on our side (better don't ask what was it). So I can confirm no problems on saltstack side. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Thank you for updating this issue. It is no longer marked as stale. |
Description of Issue/Question
I am attempting to utilize the option "state_output" so that my state.apply commands do not display so much information every time I run them. My understanding is that by setting state_output to options like "changes" should reduce my output, however, I receive the same level of verbosity no matter what I have tried.
Setup
Steps to Reproduce Issue
output is the same when manually specifying --state-output=changes
Versions Report
The text was updated successfully, but these errors were encountered: