What | Removed | Added |
---|---|---|
Assignee | pablo.suarezhernandez@suse.com | Mihai.Dinca@suse.com |
Flags | needinfo?(jeriveramoya@suse.com) |
We are covering the test.ping scenario with tests that run in docker containers and this bug can not be reproduced there. I think that the test tries to accept the minion key too early, before the minion is fully started (even though systemd reports status started it doesn't mean the minion is ready) I would suggest to change the command that runs on master in order to accept the minion key to: salt-run state.event tagmatch="salt/auth" quiet=True count=1 && salt-key -A -y This way, would wait for the minion to contact the master before trying to accepting the key. The command that tries the test.ping needs to be changed to: salt-run state.event tagmatch="salt/minion/*/start" quiet=True count=1 && salt "*" test.ping because after accepting the key, the minion is not fully ready to accept requests. Getting the start event is a signal that the minion is now ready. Please let me know what is the outcome. Thanks!