-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
salt-sproxy fails to parse ansible-roster return #162
Labels
Comments
I got it to work with roster: file 10.220.0.11:
10.220.0.12: which is sufficient for me because i just need a flat file of minion_ids i can target and im not going to use salt-ssh in the future. |
I'm seeing some suspicious behaviour, reopening to investigate it soon. Thanks for reporting @felskrone! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
salt-sproxy fails to evaluate targets from ansible roster
Steps To Reproduce
The volumes/config_exchange contains my configs and pillars and get mounted into the container at /mnt. They are externally generated from another container into a shared volume.
In the container i simply symlink the configs into place, removing the existing master and roster
These are all currently empty
/srv/salt/
/srv/salt/ext
/srv/pillar/ext
This is what the environment looks like when executing sproxy commands:
The inventory seems to work fine
Trying to get a preview of the targets
Expected behavior
A return of all minions / targets defined in roster
$ salt-sproxy \* --preview-target - 10.220.0.11 - 10.220.0.12
Versions Report
Print the output from
salt-sproxy -V
inside the backticks below:Additional context
i tried the -dev version "mirceaulinic/salt-sproxy:allinone-dev" as well, same problem.
If i can be of any more help, please let me know.
The text was updated successfully, but these errors were encountered: