Bug 1113499

Summary: [RHEVM] Special character handling on VM Description is not correct
Product: Red Hat Enterprise Virtualization Manager Reporter: Alexandros Gkesos <agkesos>
Component: ovirt-engine-webadmin-portalAssignee: Shahar Havivi <shavivi>
Status: CLOSED ERRATA QA Contact: Pavel Novotny <pnovotny>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.0CC: ecohen, iheim, mavital, ngupta, ofrenkel, pdwyer, ppostler, pstehlik, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Regression
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: vt1.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-11 18:04:15 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:
Bug Depends On:    
Bug Blocks: 1142923, 1156165    

Description Alexandros Gkesos 2014-06-26 09:45:10 UTC 
Created attachment 912391 [details]
RHEVM - Special Characters on VM's description handling

Description of problem:Special character handling on VM Description is not correct 


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


How reproducible: Create/Edit a VM's description with Special Characters


Steps to Reproduce:
1.Include special characters &, ', ",< ,> in a VM's description
2.
3.

Actual results: &amp; &#39; &quot; &lt; &gt;


Expected results: & ' " < >


Additional info:
Comment 1 Omer Frenkel 2014-06-26 10:25:38 UTC 
i verified it is reproduced in UI only, in rest api the result is ok
Comment 3 Pavel Novotny 2014-08-12 12:42:32 UTC 
Verified upstream in ovirt-engine-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch (rc1; post-vt1.3 upstream build).

Created VM with description & ' " < >
- VM -> General sub-tab shows Description: & ' " < >
- edit VM -> Description input box has value & ' " < >
Comment 5 errata-xmlrpc 2015-02-11 18:04:15 UTC 
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.

https://rhn.redhat.com/errata/RHSA-2015-0158.html