So we have been running into an issue in our ansible rollout that hasn't occurred before sometime in mid April. About that time we started getting conflicts with services reusing the 5099 fireball port if those processes were started from ansible.
In the latest case, I set up a new hardware box and ran the ansible jobs which load up various services like iscsid, nrpe, etc. All of these usually pull a port from the 10000->65536 when started by themselves, but everyone of them pulled 5099 as their listening port. I had to end up stopping about a dozen processes before I could run ansible again. What I am wanting to know is if this is known or seen anywhere else and if there is some flag we might have setup which is triggering this that we could turn off. Thanks. -- Stephen J Smoogen. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CANnLRdjvSwnoA6WNr%2B5uTKNeO06ghBTfSiKKj%3DQnMcihhXDMWw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
