Bug 988486
| Summary: | lsblk diagnostic not working | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Burns <mburns> |
| Component: | ovirt-node | Assignee: | Ryan Barry <rbarry> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.5 | CC: | acathrow, bsarathy, cboyle, cshao, gouyang, hadong, huiwa, jboggs, leiwang, mburns, ovirt-maint, rbarry, yaniwang, ycui |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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: | Environment: | ||
| Last Closed: | 2014-01-21 19:46:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Mike Burns
2013-07-25 16:56:09 UTC
It is duplicated with existing bug 980371. 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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. Test version: rhevh-6.5-20131031.1.0 ovirt-node-3.0.1-7.el6.noarch 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. 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. http://rhn.redhat.com/errata/RHBA-2014-0033.html |