Bug 1387838
Summary: | KVM Import fails when libvirtd qemu+tcp URI is used, with no user/password entered. | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | ling |
Component: | Backend.Core | Assignee: | Tomáš Golembiovský <tgolembi> |
Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.0.4.4 | CC: | bugs, michal.skrivanek, tjelinek |
Target Milestone: | ovirt-4.1.0-alpha | Flags: | tjelinek:
ovirt-4.1?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-18 11:53:13 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
ling
2016-10-22 11:15:10 UTC
I'd say that in v2v.py the _password_file expects the os.write(fd, self._password.value) to have the _password.value not None. It looks like this has never been working. (In reply to Tomas Jelinek from comment #1) > I'd say that in v2v.py the _password_file expects the os.write(fd, > self._password.value) to have the _password.value not None. > It looks like this has never been working. I can confirm the problem. This will be fixed. For now, as a workaround for password-less connections do the following: 1) check 'requires authetication' box 2) put something into username and password text fields; anything like "abcd" or "12345" is ok, the values will be ignored Thanks for looking at the bug and fixing it! the root cause of this is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1388596 hence closing this one as duplicate to track the same issue on one place only. *** This bug has been marked as a duplicate of bug 1388596 *** |