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:
Sounds like a dup of bug 1388336
This is a duplication of bug 1388336
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
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
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).
Hi Nisim, Since this bug is a dup of BZ 1388336, can you please mark this bug as verified? Thanks!
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.
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
BZ<2>Jira Resync
sync2jira