-
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
Exception - NameError: global name '_check_32' is not defined #12177
Comments
I'm having same issue, CentOS 6.5
|
I have the same issue for a noarch pkg on CentOS 6.5.
|
Thanks for the reports. Very strange, as the @jadickin On which OS did you see the error? RHEL 6.5 like the others? @terminalmage could you potentially test this on a RHEL 6.5 machine? Curious if we can reproduce. |
Yeah, this is an issue with binary package verification. And there's no good way to fix this since the _check_32() function is being called from within a function that is being imported into pkg_resource.py. I've decided to remove binary package verification altogether. It's unnecessary since the state will still fail if the desired package name differs from the actual package name, due to the desired package name not appearing in the return data from To those experiencing this issue right now, I have ported that change to 2014.1.3 and saved the result in this pastebin. Save it as pkg_resource.py within the This fix will be in 2014.1.4, so make sure to remove that file and re-sync the modules before upgrading to 2014.1.4, or else the sync'ed version will take precedence over future releases, leading to unforeseen issues. |
Thanks for the quick workaround! If you're curious, I was using the latest Amazon Linux AMI, 2014.03. |
@jadickin Did the workaround work for you, then? I tested myself before posting that, but I just wanted to be sure. |
The workaround did work, and the instructions for using it were really good. I've been digging into saltstack for a couple weeks, but I wouldn't have been able to do much without the explanation. 😄 |
Great! Glad I could help 😄 |
This work around didn't work for me. Now I get this error with all pkg.installed uses. salt-master-2014.1.0-1.el6.noarch
|
Have the same bug. The solution in #12177 (comment) works for me. |
I encountered the following exception in the 2014.1.3 minion release. I looked at the code a bit, but I'm not a python developer.
2014.1.0 minions didn't have any problems running the state.
The state in question was this...
salt --versions-report
outputThe text was updated successfully, but these errors were encountered: