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 1452147 - corruption in anaconda-tb-* file (OMITTED BINARY DATAerrors: strict)
Summary: corruption in anaconda-tb-* file (OMITTED BINARY DATAerrors: strict)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-meh
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Kolman
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 986515
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-18 12:35 UTC by Radek Vykydal
Modified: 2021-01-15 07:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 986515
Environment:
Last Closed: 2021-01-15 07:36:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Radek Vykydal 2017-05-18 12:35:48 UTC
+++ This bug was initially created as a clone of Bug #986515 +++

Description of problem:

There is corruption in anaconda-tb-* log files reporting some UnicodeDecodeError exceptions. Specifically, this string is corrupt:

OMITTED BINARY DATAerrors: strict

Examples are:
Bug 969309: Attachment 776074 [details]
Bug 981608: Attachment 769164 [details]

Version-Release number of selected component (if applicable):
python-meh-0.25-1.fc19.noarch (per Bug 981608 packaging.log)
anaconda 19.30.13-1
Fedora-19-x86_64-DVD.iso

How reproducible:
Always.

Steps to Reproduce:
1. Generate a UnicodeDecodeError exception by entering non-Latin characters in the "Full name" text box of the User Creation dialog of the installer.

Examples:
Bug 969309 - anaconda crashes when typing non-latin character in user creation 
Bug 981608 - UnicodeDecodeError: 'utf8' codec can't decode byte 0xd0 in position 0: unexpected end of data 

Actual results:
This string appears in the anaconda-tb-* log:
OMITTED BINARY DATAerrors: strict

Expected results:
Clearly delimited exception reporting text and meta-reporting of omitted binary data.

Even better would be hex-encoded binary data similar to "hexdump -C" output.

Additional info:
See also:
Bug 886983 - binary data embedded in anaconda-tb

Reproduced in a VM with:
$ qemu-kvm -m 4096 -hda f19-test-1.img -cdrom ~/xfr/fedora/F19/Fedora-19-x86_64-DVD.iso -vga std -boot menu=on

--- Additional comment from Steve Tyler on 2013-07-20 00:41:35 EDT ---

Snippet from Bug 969309: Attachment 776074 [details]:

anaconda 19.30.13-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/encodings/utf_8.py", line 16, in decode
    return codecs.utf_8_decode(input, errors, True)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/users.py", line 162, in guess_username
    username = fullname[0][0].decode("utf-8").lower() + username
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/user.py", line 326, in _guessNames
    username = guess_username(fullname)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xc5 in position 0: unexpected end of data

Local variables in innermost frame:
OMITTED BINARY DATAerrors: strict


Anaconda instance, containing members:
...

--- Additional comment from Steve Tyler on 2013-07-20 01:00:35 EDT ---

(In reply to Steve Tyler from comment #1)
...
> Local variables in innermost frame:
> OMITTED BINARY DATAerrors: strict
...

The variable name appears to have been omitted too ...

--- Additional comment from Fedora Update System on 2013-07-23 07:57:38 EDT ---

python-meh-0.26-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-meh-0.26-1.fc19

--- Additional comment from Fedora Update System on 2013-07-23 23:22:42 EDT ---

Package python-meh-0.26-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-meh-0.26-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-13453/python-meh-0.26-1.fc19
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2013-10-11 19:58:32 EDT ---

python-meh-0.26-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 2 Radek Vykydal 2017-05-18 12:37:41 UTC
I hit the issue during rhel 7.4 devel phase:
https://bugzilla.redhat.com/show_bug.cgi?id=1443114#c1

Comment 4 RHEL Program Management 2021-01-15 07:36:23 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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