Bug 1451291
Summary: | Import from KVM (via libvirt) is confusing | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Roman Hodain <rhodain> |
Component: | Frontend.WebAdmin | Assignee: | bugs <bugs> |
Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.1 | CC: | bugs, michal.skrivanek, rhodain, tjelinek |
Target Milestone: | --- | Flags: | rhodain:
planning_ack?
rhodain: devel_ack? rhodain: testing_ack? |
Target Release: | --- | ||
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-05-17 07:36:22 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: |
Description
Roman Hodain
2017-05-16 10:25:18 UTC
(In reply to Roman Hodain from comment #0) > In order to be able to import VM from another qemu system the key pair needs > to be exchanged between the importing host and the source hypervisor. This > information should be displayed when "KVM (via libvirt) is chosen from the " > source" dropdown menu. > > The reason for this is that when this option is chosen then the > authentication are shown. Than can confuse the users and make them think > that the user and password for the source system is sufficient, but this > will not work for qemu+ssh protocol. Technically that is not entirely correct. It depends on authentication scheme set up on the source host I agree it looks confusing but some examples in KB might be better than trying to repeat the libvirt documentation. We do have a (?) next to URI pointing people to that If you feel a different text would be better understood please feel free to propose one, no problem changing it. There is a different bug regarding this dialog already opened so Im closing this as duplicate and lets continue the discussion there. *** This bug has been marked as a duplicate of bug 1395753 *** |