You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Windows minion (3006.x and 3007.1) configured in multimaster config (two masters) throws duplicate custom event when using salt-call event.send or the event.send state module. causing duplicate reactor executions on the same master
A few more findings, the issue seems caused by the combination of salt-call and event.send module.
If making the call from the master, using instead salt <minion> event.send or executing a state with the event.send module, the event is generated only once on each master, but on both masters, which I also think it's wrong, the event should be seen only in the master making the call like in other modules.
For instance, using another module like test.echo or test.ping, the return event is seen only in the calling master event bus, not in the other one.
using salt-call with --master option sends the event only to the desired master salt-call event.send --master=172.21.0.11 some/event
Setup
I've seen these issues in 3006 and 3007, after 3006.8 a similar issue with the /start event seemed fixed.
I'm testing this now with 3007.1 and Windows minion.
Expected behavior
Only the first active master should get only one event
The text was updated successfully, but these errors were encountered:
Description
Windows minion (3006.x and 3007.1) configured in multimaster config (two masters) throws duplicate custom event when using
salt-call event.send
or the event.send state module. causing duplicate reactor executions on the same masterA few more findings, the issue seems caused by the combination of
salt-call
andevent.send
module.If making the call from the master, using instead
salt <minion> event.send
or executing a state with the event.send module, the event is generated only once on each master, but on both masters, which I also think it's wrong, the event should be seen only in the master making the call like in other modules.For instance, using another module like
test.echo
ortest.ping
, the return event is seen only in the calling master event bus, not in the other one.using
salt-call
with--master
option sends the event only to the desired mastersalt-call event.send --master=172.21.0.11 some/event
Setup
I've seen these issues in 3006 and 3007, after 3006.8 a similar issue with the /start event seemed fixed.
I'm testing this now with 3007.1 and Windows minion.
Expected behavior
Only the first active master should get only one event
The text was updated successfully, but these errors were encountered: