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] TypeError in transport/tcp.py #66435
Comments
It's not just the master. The minion breaks too |
I'm running into this issue as well on my system. Interestingly after manually installing tornado I get an error about pyzmq version conflict. I'm running
|
Yep had that too so installed from pip but then a bunch of new errors came up in the end installed salt from pip and that resulted in more errors.
|
For me the minion was fixed by installing py39-tornado-6.4, at least I don't see any issues there. After rolling back to previous verison in freebsd I do get this error on the master:
|
same here, 3007 is totally broken under FreeBSD.. was this even tested? |
In the freebsd PR there is a patch that reverts us back to 3006, I can confirm that works on my systems: My goal is to test 3007 via pip once we get changes reverted in our ports tree, I am also surprised that this didn't get caught until after the changes were published. |
Description
Issue in SaltStack master 3007.0.
On FreeBSD, upgraded to 3007.0, it complained it needs Tornado. I Installed Tornado 6.3.3, the master started, but then any command results in this:
Also see this bug report on FreeBSD Bugzilla: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278149
I also installed Salt on a new machine and it behaves the same way.
Setup
FreeBSD running on AWS. No jails.
Steps to Reproduce the behavior
Install py39-salt on a fresh FreeBSD 14, install py39-tornado, start salt-master, then try to run any command.
Expected behavior
Run the command, don't error out
Screenshots
N/A, trace above
Versions Report
I killed the machine, sorry, but it's 3007.0.
The text was updated successfully, but these errors were encountered: