http://bugzilla.suse.com/show_bug.cgi?id=1171257 http://bugzilla.suse.com/show_bug.cgi?id=1171257#c5 --- Comment #5 from Alberto Planas Dominguez <aplanas@suse.com> --- (In reply to Jochen Breuer from comment #4)
Weird! I just did a fresh install and I don't get a UnicodeDecodeError.
Right. You only see the exception the first time, when you restart the salt-master, later there is no call to payload.unpackage anymore, not sure why.
But I can confirm that it's not working and that there seems to be the return missing. I've tested the same package (3000.2) for Leap 15.1 (Python 3.6) and this is working. So I guess we are running into a Python 3.8 problem. I'll do some cherry-picks that upstream did for Python 3.8 compatiblity and then I'll re-run my tests.
Good catch, can be indeed a Python 3.8 issue. The fact that I cannot see any later call to payload.unpackage makes me wonder if there are not two bugs here at least. Following the payload asset, looks weird that is using this unpackage function helper here, as the payload is AES encrypted and nested under a dict, where the payload is also serialized. The UTF error is over the inner payload that also require de-serialization. -- You are receiving this mail because: You are on the CC list for the bug.