/ salt Public
[BUG] Possible concurrency issue with reactor/orchestrate running on master only #57626
broken, incorrect, or confusing behavior
Release code name and version
2nd top severity, seen by most users, causes major problems
I have a salt master which is configured with 3 reactor/orchestrate pairs. The master listens to messages from network devices via napalm-logs, then performs 3 tasks -
updates a mariadb with the event details
updates the db with the host details
runs a python script which connects to the network device and collects further information to add to the db.
As the number of messages has increased, I'm noticing that more of the jobs are failing with either of these 2 responses. The errors are sporadic and not linked to specific network devices.
state.orchestrateonly run one job at a time, so if a second
state.orchestrateis called from the reactor, whilst the first is running, the second job will fail?
salt --versions-report(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
I've upgraded to 3000.3 and still experience the same behaviour.
The text was updated successfully, but these errors were encountered: