-
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
grains.filter_by list broken? #51478
Comments
looks like i'm able to replicate this. glancing at the code it seems we might need to loop through the list before making the call to |
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. |
keep open edit: has this been addressed yet? |
Thank you for updating this issue. It is no longer marked as stale. |
nope, we changed our settings with stalebot to not close issues with bug/feature labels so this should not go stale again. |
I'm seeing the same issue, when I use a list of grains nothing matches at all: With a scalar value/simple string it works just fine: (Master and all minions but the OpenBSD one are running 3005.1) |
Description of Issue/Question
Per the docs,
grains.filter_by
'sgrain
parameter supposedly accepts a list:However, this:
does not work, as it returns blank and defaults to the (incorrect, for those keys) default values. This can be shown at the commandline:
Yet:
salt -L 'arch,centos6_32' grains.get osfinger:
salt -L 'arch,centos6_32' grains.get os:
I've tried multiple variations on the list syntax.
grain1,grain2
: Nothing returns.[grain1,grain2]
: The following error is returned:["grain1","grain2"]
: Same as[grain1,grain2]
.["grain1,grain2"]
: Same as[grain1,grain2]
.grain1:grain2
: (As expected, as this is reserverd for dicts, but worth a shot because of the referenced error line) Nothing returns.[grain1:grain2]
: Nothing returns.etc.
It happens on python 3.4 as well:
Versions Report
Happening on all my minions. Master and all minions are on 2018.3.3, mix of python 3.4 and 2.7.
The text was updated successfully, but these errors were encountered: