Skip to content
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] salt-call hangs after highstate for Windows minion 3005 and 3005.1 (Tiamat), has to be manually killed [BUG] #63028

Closed
3 tasks
geisingerDev opened this issue Nov 7, 2022 · 13 comments
Labels
Bug broken, incorrect, or confusing behavior Duplicate Duplicate of another issue or PR - will be closed Windows

Comments

@geisingerDev
Copy link

geisingerDev commented Nov 7, 2022

Description
Highstate doesn't end with salt-call on the 3005 and 3005.1 Windows minion.

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.

  • on-prem physical machine
  • vmware vm
  • ec2

Steps to Reproduce the behavior
run salt-call state.highstate

Expected behavior
The highstate should end without manual intervention.

Screenshots
image

Versions Report

Salt Version:
Salt: 3005.1

Dependency Versions:
cffi: 1.11.5
cherrypy: Not Installed
dateutil: 2.6.1
docker-py: Not Installed
gitdb: 4.0.1
gitpython: 3.0.9
Jinja2: 3.0.3
libgit2: 1.1.0
M2Crypto: 0.35.2
Mako: Not Installed
msgpack: 0.6.2
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.14
pycrypto: Not Installed
pycryptodome: 3.10.1
pygit2: 1.6.1
Python: 3.6.8 (default, Jun 14 2022, 12:54:58)
python-gnupg: Not Installed
PyYAML: 6.0
PyZMQ: 20.0.0
smmap: 3.0.1
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4

Salt Extensions:
SSEAPE: 8.10.0.3

System Versions:
dist: rhel 8.6 Ootpa
locale: UTF-8
machine: x86_64
release: 4.18.0-372.32.1.el8_6.x86_64
system: Linux
version: Red Hat Enterprise Linux 8.6 Ootpa

(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
Master 3005.1
Minion 3005.1

PASTE HERE

Additional context
Add any other context about the problem here.
image

@geisingerDev geisingerDev added Bug broken, incorrect, or confusing behavior needs-triage labels Nov 7, 2022
@welcome
Copy link

welcome bot commented Nov 7, 2022

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.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

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.
If you have additional questions, email us at [email protected]. We’re glad you’ve joined our community and look forward to doing awesome things with you!

@geisingerDev geisingerDev changed the title [BUG] salt-call hangs after highstate for Windows minion 3005.1, has to be manually killed [BUG] [BUG] salt-call hangs after highstate for Windows minion 3005 and 3005.1, has to be manually killed [BUG] Nov 7, 2022
@OrangeDog
Copy link
Contributor

Duplicate: #62937

@OrangeDog OrangeDog added Duplicate Duplicate of another issue or PR - will be closed Windows labels Nov 7, 2022
@geisingerDev geisingerDev changed the title [BUG] salt-call hangs after highstate for Windows minion 3005 and 3005.1, has to be manually killed [BUG] [BUG] salt-call hangs after highstate for Windows minion 3005 and 3005.1 (Tiamat), has to be manually killed [BUG] Nov 7, 2022
@twangboy
Copy link
Contributor

twangboy commented Nov 7, 2022

Closing this in favor of #62937. Thanks @OrangeDog

@geisingerDev
Copy link
Author

How can you close a bug without resolution?

@geisingerDev
Copy link
Author

is there a fix for Tiamat? we have to roll it out to all our systems

@geisingerDev
Copy link
Author

@twangboy

@OrangeDog
Copy link
Contributor

OrangeDog commented Nov 8, 2022

Because it's a duplicate. See the linked issue for a resolution.

@geisingerDev
Copy link
Author

we are not using the classic package. is the resolution the same or we have to wait as you mentioned in #62937.

"If you are using a OneDir/Tiamat package, you will have to wait for the fix (either a patched build, or a new release)."

@geisingerDev
Copy link
Author

geisingerDev commented Nov 8, 2022

as we know the master is at 20.0.0 of pyzmq, so you just want the minions updated to it? or i have to upgrade the master pyzmq to 22.0.3 as well? @twangboy please let us know thank you

@OrangeDog
Copy link
Contributor

All the details are in the linked issue.

@geisingerDev
Copy link
Author

image

@geisingerDev
Copy link
Author

i guess we will have to wait

@geisingerDev
Copy link
Author

geisingerDev commented Nov 8, 2022

@OrangeDog i think the details are missing in the other link. are you saying we have to upgrade the master and minions to pyzmq 22.0.3 even for Tiamat because there is conflicting information on that page. We just need to know as it affects a big chunk of our environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Duplicate Duplicate of another issue or PR - will be closed Windows
Projects
None yet
Development

No branches or pull requests

3 participants