Open felskrone opened 4 years ago
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!
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
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.