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

Bug 1077806

Summary: [rhevm-shell] Odd formating for 'initialization-configuration-data' VM attribute
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engine-cliAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED CURRENTRELEASE QA Contact: Shai Revivo <srevivo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: aberezin, acathrow, gklein, iheim, jbelka, laravot, ofrenkel, oramraz, pstehlik, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: rhevm-cli-3.5.0.1-1.el6_5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-14 06:49:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Jiri Belka 2014-03-18 15:23:31 UTC 
Created attachment 876006 [details]
screenshot

Description of problem:
just check screenshot, 'initialization-configuration-data' output is broken.

Version-Release number of selected component (if applicable):
av3 rhevm-cli-3.4.0.6-2.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. show vm $vmname --all_content true
2.
3.

Actual results:
'initialization-configuration-data' formatting is broken

Expected results:
no blank space, looks odd

Additional info:
Comment 1 Omer Frenkel 2014-03-25 14:37:10 UTC 
Liron, isn't this part of the vm from ovf feature?
Comment 2 Juan Hernández 2014-03-26 16:17:11 UTC 
This seems related to the type of terminal emulator that you are using. Can you give details about the terminal emulator that you are using?
Comment 3 Jiri Belka 2014-03-27 07:37:36 UTC 
I'm using RHEL6.x as my client, thus it is gnome terminal.
Comment 4 Gil Klein 2014-08-14 06:49:46 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA