Back to bug 1379363
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Nisim Simsolo | 2016-11-13 12:55:48 UTC | Depends On | 1377271 | |
| Link ID | Red Hat Knowledge Base (Solution) 2604231 | |||
| Link ID | oVirt gerrit 63464 | |||
| Link ID | oVirt gerrit 63484 | |||
| Status | NEW | POST | ||
| Status | POST | MODIFIED | ||
| Status | MODIFIED | ON_QA | ||
| CC | nsimsolo | |||
| Nisim Simsolo | 2016-11-13 12:56:39 UTC | Status | ON_QA | VERIFIED |
| Byron Gravenorst | 2017-01-15 23:31:25 UTC | CC | bgraveno | |
| Doc Text | Cause: VMware seems to allow all special characters for data center, folder and cluster name, while v2v failed to handle those special chars. Consequence: RHEV v2v failed for a VMware external provider which contains special characters (e.g. space,&,#...) in Data Center/cluster/folder name. Fix: handle it correctly in v2v engine side by encoding those characters before sending them to VDSM: 1. This solution encodes the VMware data center and VMware cluster parts of the uri i.e. for uri vpx://user@vcenter/DATACENTER/CLUSTER/esxi?no_verify=1 we encode the DATACENTER and CLUSTER parts, including folders if exists. Other parts of the uri are left decoded. 2. In UI we continue to display the data center and cluster as was originally typed by the user (decoded). 3. The encoding is done on frontend and therefore should be also done while using REST apis for VMware v2v. Result: RHEV v2v works fine for a VMware external provider which contains special characters in uri. | 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. |
||
| errata-xmlrpc | 2017-01-17 00:51:02 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-01-17 18:04:24 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-01-17 13:04:24 UTC | |||
| Red Hat One Jira (issues.redhat.com) | 2021-08-30 12:39:14 UTC | Link ID | Red Hat Issue Tracker RHV-43256 |
Back to bug 1379363