Bug 1379363
| Summary: | [z-stream clone - 3.6.10] [z-stream clone - 4.0.5] Special characters in VMware cluster and data center name should be handled correctly | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Sharon Gratch <sgratch> |
| Status: | CLOSED ERRATA | QA Contact: | Nisim Simsolo <nsimsolo> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6.7 | CC: | berrange, bgraveno, dornelas, gklein, lsurette, mavital, mgoldboi, michal.skrivanek, nsimsolo, rbalakri, Rhev-m-bugs, rjones, sgratch, srevivo, tjelinek, ykaul |
| Target Milestone: | ovirt-3.6.10 | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
This update fixes an issue where V2V fails for a VMware external provider which contains special characters in a data center, cluster, or folder name. The characters are now encoded on the V2V engine side before sending them to the VDSM.
1) This solution encodes the VMware data center and VMware cluster parts of the uri. For example, in the URI vpx://user@vcenter/<DATACENTER>/<CLUSTER>/esxi?no_verify=1 the <DATACENTER> and <CLUSTER> parts are encoded, including folders if they exist. Other parts of the URI are left decoded.
2) The UI will display the data center and cluster as was originally typed by the user.
3. The encoding is done on the frontend and should be also done while using REST APIs for VMware V2V.
|
Story Points: | --- |
| Clone Of: | 1377271 | Environment: | |
| Last Closed: | 2017-01-17 18:04:24 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1377271 | ||
| Bug Blocks: | |||
|
Comment 1
Nisim Simsolo
2016-11-13 12:56:39 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/RHEA-2017-0108.html |