Bug 988486 - lsblk diagnostic not working
lsblk diagnostic not working
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Ryan Barry
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2013-07-25 12:56 EDT by Mike Burns
Modified: 2014-01-21 14:46 EST (History)
14 users (show)

See Also:
Fixed In Version: ovirt-node-3.0.1-2.el6
Doc Type: Bug Fix
Doc Text:
Previously lsblk diagnostic was not working, the following error message was being generated: "ascii' codec can't decode byte 0xe2 in position 169: ordinal not in range(128)" when selecting lsblk in the diagnostic screen. This was caused by the UI not handling the encoding of the console getting changed. This has been fixed by making sure the UI is always using UTF-8. lsblk now works correctly.
Story Points: ---
Clone Of:
Last Closed: 2014-01-21 14:46:16 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 16554 None None None Never

  None (edit)
Description Mike Burns 2013-07-25 12:56:09 EDT
Description of problem:
Error message:
'ascii' codec can't decode byte 0xe2 in position 169: ordinal not in range(128)

when selecting lsblk in diagnostic screen

Version-Release number of selected component (if applicable):

How reproducible:
always (so far)

Steps to Reproduce:
1.install rhev-h
2.go to diagnostics screen
3.select lsblk

Actual results:
error as above

Expected results:
actual output of lsblk is shown

Additional info:
Comment 1 Ying Cui 2013-07-25 22:09:48 EDT
It is duplicated with existing bug 980371.
Comment 7 Cheryn Tan 2013-11-07 19:36:17 EST
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:


Thanks in advance.
Comment 8 cshao 2013-11-08 02:29:20 EST
Test version:

Test steps:
1.install rhev-h
2.go to diagnostics screen
3.select lsblk

Test result:
Actual output of lsblk is shown

So the bug is fixed, change bug status to VERIFIED.
Comment 10 errata-xmlrpc 2014-01-21 14:46:16 EST
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.


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