Bug 1135920
| Summary: | [Windows sysprep] Run Once: Special characters are not encoded in XML sysprep files for Windows 7, 8, 2008, 2012 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Shahar Havivi <shavivi> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4.0 | CC: | bugs, ecohen, eedri, iheim, juwu, lpeer, lsurette, mavital, michal.skrivanek, ofrenkel, pnovotny, pstehlik, rbalakri, Rhev-m-bugs, sherold, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.4.3 | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | virt | ||
| Fixed In Version: | org.ovirt.engine-root-3.4.3-1 | Doc Type: | Bug Fix |
| Doc Text: |
When running a sealed Windows 7, 8, 2008, or 2012 virtual machine with sysprep floppy attached, all values provided from Run Once dialog are put in the sysprep file as plain-text, even when these Windows versions are using XML format for sysprep file, thus allowing to create a syntactically incorrect sysprep file. With this bug fix, all variables in XML sysprep template files are now placed into CDATA section so all characters are represented the same way as they are entered.
|
Story Points: | --- |
| Clone Of: | 1132191 | Environment: | |
| Last Closed: | 2014-10-23 12:30:17 UTC | Type: | --- |
| 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: | 1132191 | ||
| Bug Blocks: | |||
|
Comment 1
Michal Skrivanek
2014-09-01 07:47:30 UTC
Verified in rhevm-3.4.3-1.1.el6ev.noarch (av12.1). All variables in XML sysprep template files are now placed into CDATA section so all characters are represented the same way as they are entered. For example password 'pass</word>' now doesn't cause parsing error and it's set in the Windows guest. Note that the above doesn't apply to *custom* sysprep file, where user has to take care about the sysprep file validity by himself. 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/RHBA-2014-1712.html |