Closed roflmao closed 1 year ago
I don't think it is a different problem. Actually what I'm seeing is exactly what @roflmao described at the very top. I think the problem just got a little more refined along the way. I just couldn't believe that nobody would have looked at this since 2016, because it does sound like a very basic issue.
@anitakrueger just wanted here to highlight my comment in #21986 on how to work around grain targeting, it's less important now than it used to be when it comes to the mine because they fixed this (for the mine only) in 2019.2.0 with the greedy flag, but it is also applicable in other contexts as well.
EDIT:
I thought the greedy flag fixed this but it looks like it doesn't, that mine issue (the root cause of which is the same as the root cause of this issue) is still being commented on relatively recently.
Further reading:
@anitakrueger I verified your issue is fixed on the 2019.2.1 branch, so it will be included in the 2019.2.1 release. Your issue is different from the reported issue here, so we will not be able to close this as its a feature that needs to be added. Here is my verification test case:
v2019.2.0
(salt-py2) ➜ salt git:(0ca04ffbeb) sudo salt '*' grains.setval roles webserver3
newrecipe:
----------
roles:
webserver3
(salt-py2) ➜ salt git:(0ca04ffbeb) sudo salt -G 'roles:webserver3' test.ping
newrecipe:
Minion did not return. [No response]
ERROR: Minions returned with non-zero exit code
(salt-py2) ➜ salt git:(0ca04ffbeb)
2019.2.1 branch
(salt-py2) ➜ salt git:(c56fbb0f94) sudo salt '*' grains.setval roles webserver5
newrecipe:
----------
roles:
webserver5
(salt-py2) ➜ salt git:(c56fbb0f94) sudo salt -G 'roles:webserver5' test.ping
newrecipe:
True
(salt-py2) ➜ salt git:(c56fbb0f94)
Forgot to mention @anitakrueger if you could verify on the 2019.2.1 branch to ensure I am correct.
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.
This is definitely still a problem and should not be marked as stale. We've ended up working around it in another way (query our CMDB to know which servers to target before calling salt), but this is rather lame and I would much rather use Salt to do it completely since it has all of the information it needs.
Thank you for updating this issue. It is no longer marked as stale.
@roflmao Could you verify that this is still a problem with 3006.2?
Closing this due to age, the old version of Salt and Python 2. Can you retest this with the latest release of Salt 3006.2 and if still an issue, please open a new issue, which will have metrics in tracking issues.
Description of Issue/Question
While using compound matching i dont get response from minion. (it matches the host)
Setup
2016.3.2 with Ubuntu 16.04 master and Ubuntu 12.04 minion.
Versions Report
Master:
Minion: