-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Syndics are not able to start 3007 #66237
Comments
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. |
Just to add, I had the same issue with running 3007.0. I downgrade to 3006.7 with no other changes and works without issue. Here is some debug logs
|
Hi there, I have the exact same error message, same version. 3007.0 seems to have a bug with tornado python module. In file else:
assert is_future(future)
# For concurrent futures, we use self.add_callback, so
# it's fine if future_add_done_callback inlines that call.
future_add_done_callback(
future, lambda f: self.add_callback(callback, future)
) Then run salt-syndic -l debug It runs but with errors, which is expected due to the fact that the mentioned lines are commented
I found a similar issue ( |
Agreed - your proposed change allows the So there seems to be more broken in the "syndic" functionality inside v3007.0 than just the The second PR has changed the return value of set_event_handler() inside salt/utils/event.py
The former return value was a I have tried some fixes - but had no success yet, Some more logs about the part inside salt-syndic, that is broken now:
The command run on
The errors from "salt-syndic -l trace" - started via
|
I was able to at least work around the above issues. See the patch at https://gist.github.com/markschuh/fab749f7d7940d1fc5eba0cb57b10885 But the In v3006.7 the trace log of
In v3007.0 the related log output of
Part of the difference may be caused by differences in the logging statements. Because the events on master - returned by
|
Finally I could identify a quiet small overall patch which seems to restore the Before I open this as PR I'll need to first do more tests as part of the patch touches code, that is used by salt-minion as well. Edited: I have removed changes in salt/transport/tcp.py and salt/channel/client.py because the related ERRRORs do not block syndic functionality. This is handled by fixes for #66177 instead. |
Description
A clear and concise description of what the bug is.
Assertion Error on https://github.com/saltstack/salt/blob/3007.x/salt/minion.py#L3698 ff
set_event_handler does not return a future therefore crashes salt-syndic on
self.io_loop.add_future(future, self.reconnect_event_bus)
Setup
(Please provide relevant configs and/or SLS files (be sure to remove sensitive info. There is no general set-up of Salt.)
Please be as specific as possible and give set-up details.
Steps to Reproduce the behavior
(Include debug logs if possible and relevant)
just try to start salt-syndic
Expected behavior
A clear and concise description of what you expected to happen.
no crash
Screenshots
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: