Bug 1496744 - Importing of VM from VmWare fails at username validation (Username has a dot in it (example="user.name") and it's not permitted) but using same username VM can be imported using external provider
Summary: Importing of VM from VmWare fails at username validation (Username has a dot ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.1.2
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Sharon Gratch
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On: 1388336
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-28 09:19 UTC by Chetan Nagarkar
Modified: 2021-06-10 13:10 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Please refer to bug 1388336 since this is a duplication.
Clone Of:
Environment:
Last Closed: 2018-05-15 17:45:15 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1488 0 None None None 2018-05-15 17:46:19 UTC
oVirt gerrit 83494 0 None MERGED webadmin: v2v-VMware's username validation changed to allow dot and domain\user format 2020-03-18 16:31:00 UTC

Description Chetan Nagarkar 2017-09-28 09:19:25 UTC
Description of problem:
Importing VM using vmware external provider added to RHV 4.1 and the test communication pass the test without problem. 
But when tried to import a VM from the external provider using import VM, It is not allowing to test with same Username.
Username has a dot in it (example="user.name") and it's not permitted.

Version-Release number of selected component (if applicable):
rhevm-4.1.2.3-0.1.el7.noarch

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Yaniv Kaul 2017-09-28 09:42:35 UTC
Sounds like a dup of bug 1388336

Comment 5 Sharon Gratch 2017-11-05 11:47:53 UTC
This is a duplication of bug 1388336

Comment 6 RHV bug bot 2017-12-06 15:53:21 UTC
This bug is missing any external trackers, there is no way of knowing which patch fixed it, please add 'TestOnly' or 'Tracking' keywords or attach relevant patch in order to move this bug to ON_QA

Comment 7 RHV bug bot 2017-12-06 16:15:29 UTC
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 8 Sharon Gratch 2017-12-07 10:18:11 UTC
The external tracker was missing (not sure why hook wasn't activated), so I manually added the relevant patch to the external trackers (https://gerrit.ovirt.org/#/c/83494/) and moved status to ON_QA (since patch was already merged on 3/11).

Comment 9 Sharon Gratch 2017-12-11 15:53:10 UTC
Hi Nisim,

Since this bug is a dup of BZ 1388336, can you please mark this bug as verified?

Thanks!

Comment 10 Nisim Simsolo 2017-12-12 09:55:01 UTC
Verified: 
rhvm-4.2.0-0.6.el7
qemu-kvm-rhev-2.9.0-16.el7_4.12.x86_64
sanlock-3.5.0-1.el7.x86_64
vdsm-4.20.9-1.el7ev.x86_64
libvirt-client-3.2.0-14.el7_4.4.x86_64
virt-v2v-1.36.3-6.el7_4.3.x86_64
VMware 6.0.0 Build 2594327

Verification scenario:
1. Authenticate to ESXi using SSO user, add SSO domain/user with dots in it and assign global permission to it.
2. Browse webadmin -> VM -> import dialog, enter VMware details and domainName\userName (in my case the domain\user created is: qa.compute), select VM to import and import it.
3. Verify VM imported and can be run properly.
4. Repeat test case for Windows and Linux VMs.

Comment 15 errata-xmlrpc 2018-05-15 17:45: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://access.redhat.com/errata/RHEA-2018:1488

Comment 16 Franta Kust 2019-05-16 13:05:00 UTC
BZ<2>Jira Resync

Comment 17 Daniel Gur 2019-08-28 13:12:31 UTC
sync2jira

Comment 18 Daniel Gur 2019-08-28 13:16:43 UTC
sync2jira


Note You need to log in before you can comment on or make changes to this bug.