-
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
2018.3.4 TypeError: unicode argument without an encoding #51827
Comments
can you verify that the PR fixes it on 2018.3.4 as well? |
Sorry, I don't know what information you need from me. |
Fix definitely is not applied to 2018.3 branch: https://github.com/saltstack/salt/blob/2018.3/salt/_compat.py#L192 |
I can also confirm that I'm seeing the exact same issue (Salt 2018.3.4, CentOS 7.5 with Python 2.7) and manually applying the patch from #51298 resolves the issue. |
thanks for confirming. i will work on getting it backported right now. |
thanks for trying that @9numbernine9 I really appreciate that :) |
Will this bug also be fixed in upcoming debian buster? |
This broke our debian stretch upgrade to debian buster as well. Minion just prints these errors into log until it fills whole disk. Thanks! |
thanks for all the verifications. i'll go ahead and close since its verified. @patrick7 we do not have debian buster packages up on repo.saltstack.com but you should be able to install via pip when this fix is included in the 2018.3.4 release. Or you can patch the file. |
We actually also rely on debian and thanks to Benjamin Drung this was already backported to sid and is available in 2018.3.4+dfsg1-5 and newer see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928337 Thanks! |
@Ch3LL It doesn't seem that this fix is available in a 2018.3.x release yet? Presumably it will be in https://docs.saltstack.com/en/latest/topics/releases/2018.3.5.html which is yet unreleased; any EA for release? |
ping @KChandrashekhar do we have a timeline on a 2018.3.5 release? |
Same problem here on Ubuntu 18.04 and release 2018.3.4+ds-1 from your repositories. Seriously guys, you have no quality control. I can understand a bug but not an exception handling that allows code to flood disks. I understand why there is no concept of "stable" version. I am really surprised you made a commercial product out of this. I hope your stable commercial stuff don't do the same with your paying customers.... So can you give me a suggestion for some release that just works or I have to move to ansible? I'd stick to my old 2015 but it has been out of support for quite long time now. I think this should be reopened. |
Please can we get an update on when 2018.3.5 will be released? |
FYI for other people struggling with this, I had to switch all the infrastructure to 2017.7 latest, which seems stable enough now, although different version of 2017.7 wreaked havoc within 2015.x and 2017.x minions (different versions), some started filling logs saying that they could not recognize the master. It took few minions update to latest figure out the issue was in the master which I had to update to the latest 2017 as well. It's kind of a mess but looks stable now. Btw better like this since with 2018.x I had problems with some of the conditions in my states, lots of stuff was not picked up, I guess changes in Jinja parsing. Maybe there is a bug or release note about that as well. Maybe in 5 years from now when 2018 will be ok I'll take a look and report in more detail... My machines are Ubuntu 12.04, 14.04, 16.04, 18.04 . master runs on a 18.04 now. Other minions are on Centos6/7, versions 2015.x and 2017.x and it all looks stable right now. Which is nice with such variation. You guys are good when you don't behave like python. |
Will get the approximate 2018.3.5 release dates by Tuesday (4th June) |
@Tanoti @jacksontj Currently we are working on 2019.2.1 which is estimated for July. Neon is estimated to come out in Aug-sept. 2018.3.5 is estimated to be released in Oct-Nov of 2019. |
❤️ Debian Buster fixed https://tracker.debian.org/news/1040463/salt-201834dfsg1-6-migrated-to-testing/ |
In case anyone comes here looking for answers, the fix is not in 2018.3.5. |
Description of Issue/Question
Seems similar to other issues (#51298) involving 16 byte long strings, in our case the "master" entry on the minion has exactly 16 bytes and causes an exception.
We didn't address this problem with prior 2018.3 branch.
Steps to Reproduce Issue
Just installed fresh Debian 9.8. minimal, installed salt-minion, run salt-call grains.items (or any other command).
Versions Report
2018.3.4+ds-1
The text was updated successfully, but these errors were encountered: