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

Bug 1437480

Summary:	v2v - Few special characters in VMware cluster and data center are not handled well by libvirt/virt-v2v
Product:	[oVirt] ovirt-engine	Reporter:	Sharon Gratch <sgratch>
Component:	BLL.Virt	Assignee:	Michal Skrivanek <michal.skrivanek>
Status:	CLOSED DEFERRED	QA Contact:	meital avital <mavital>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.1.3	CC:	bugs, tjelinek
Target Milestone:	---	Keywords:	TestOnly
Target Release:	---	Flags:	rule-engine: ovirt-4.2? tjelinek: planning_ack? tjelinek: devel_ack? tjelinek: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-31 07:19:38 UTC	Type:	Bug
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:	1373863
Bug Blocks:

Description Sharon Gratch 2017-03-30 11:59:42 UTC

Description of problem:

oVirt fails to load list of VMs for importing from VMware when querying a VMware vCenter that includes at least one of the following special chars within the VMware-datacenter, VMware-Folder or VMware-cluster:
"%", "/", "\", "&", "+", "=", "?"

The same reproduced when running virsh or virt-v2v from command line to that VMware vCenter.

For details, please see depended BZ 1373863

Comment 1 Michal Skrivanek 2017-03-31 07:19:38 UTC

I do not see a reason to track it in oVirt, the libvirt bug is clear, being targeted to a minor RHEL version - not a zstream, hence we will not require a specific version in vdsm spec, there is nothing extra to be tested on oVirt side since the characters are passed through to libvirt and as soon as it does work in libvirt it shall work in oVirt