Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 908724

Summary: [RFE][TEXT] Improve display LUN name in RHEVM UI. Change “\x20” to space character
Product: Red Hat Enterprise Virtualization Manager Reporter: vvyazmin <vvyazmin>
Component: ovirt-engine-webadmin-portalAssignee: Einav Cohen <ecohen>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, amureini, ecohen, iheim, jkt, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-16 10:31:35 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:
Attachments:
Description Flags
## screen-shot none

Description vvyazmin@redhat.com 2013-02-07 11:46:25 UTC
Created attachment 694423 [details]
## screen-shot

Description of problem:
Build on scenario BZ876575

Version-Release number of selected component (if applicable):
RHEVM 3.2 - SF06 environment:

RHEVM: rhevm-3.2.0-7.el6ev.noarch
VDSM: vdsm-4.10.2-7.0.el6ev.x86_64
LIBVIRT: libvirt-0.10.2-18.el6.x86_64
QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64
SANLOCK: sanlock-2.6-2.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create multipath with friendly names (alias) with spaces (possibly due to space in the device name)
2. Create a new SD
3.
  
Actual results:
In UI you get LUN name with “/20”: kipi\x20lun\x2001

Expected results:
Change “\x20” to space character.
In UI see: kipi lun 01

Additional info:

screen-shot attached. 

/var/log/ovirt-engine/engine.log

/var/log/vdsm/vdsm.log

Comment 3 Itamar Heim 2014-06-16 10:31:35 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.