RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1744639 - yum-cron traceback because encoding error
Summary: yum-cron traceback because encoding error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Domonkos
QA Contact: Jan Blazek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-22 15:34 UTC by Michal Domonkos
Modified: 2020-03-31 20:03 UTC (History)
1 user (show)

Fixed In Version: yum-3.4.3-165.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 20:03:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1122 0 None None None 2020-03-31 20:03:49 UTC

Description Michal Domonkos 2019-08-22 15:34:10 UTC
This bug was initially created as a copy of Bug #1425776

I am copying this bug because: 



I receive error message from yum-cron (daily, yum-cron is set to emit message by email) because of encoding error:

yum-cron:230:sendMessages:UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 76: ordinal not in range(128)

This line 230 contains:

output = ''.join(self.output)

The output is in UTF-8 (and not in ASCII) probably because I'm using cs_CZ.UTF-8 locale. Similar bug has been fixed in the past, see bug #1202680

Traceback is attached.

Comment 1 Michal Domonkos 2019-08-23 09:23:11 UTC
Upstream PR:
https://github.com/rpm-software-management/yum/pull/99

Comment 2 Michal Domonkos 2019-08-23 09:37:44 UTC
*** HOW TO TEST ***

To test this, you'll need to trigger yum's import mechanism for GPG keys when installing the downloaded updates.  The reason is that, in case of a missing key, the Czech translations of the error message contains the word "klíč" which would previously trigger the traceback.  With the patch, the error message is decoded into a proper unicode object.

Setup:
# yum install -y glibc-common  # for localization support
# rpm -qa ^gpg-pubkey | xargs rpm -e  # remove all RPM public keys
# cat /path/to/yum-cron.conf
[...]
update_messages = yes
download_updates = yes
apply_updates = yes
[...]

Test:
# LANG=cs_CZ.utf8 yum-cron /path/to/yum-cron.conf

Result (before):
[...]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 76: ordinal not in range(128)

Result (after):
No crash, just the regular output.

Comment 6 errata-xmlrpc 2020-03-31 20:03:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1122


Note You need to log in before you can comment on or make changes to this bug.