| Summary: | Wrong error info when import non-existent disk image from virt-manager GUI | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | tingting zheng <tzheng> | |
| Component: | virt-manager | Assignee: | Pavel Hrdina <phrdina> | |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 6.8 | CC: | juzhou, mxie, mzhan, phrdina, rbalakri, xiaodwan | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | virt-manager-0.9.0-32.el6 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1305210 (view as bug list) | Environment: | ||
| Last Closed: | 2017-03-21 10:42:05 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 1305210 | |||
|
Description
tingting zheng
2016-02-06 06:23:04 UTC
I can reproduce with package: virt-manager-0.9.0-31.el6.x86_64 python-virtinst-0.600.0-29.el6.noarch Then try to verify this bug with new build: python-virtinst-0.600.0-30.el6.noarch virt-manager-0.9.0-33.el6.x86_64 Steps: 1.Launch virt-manager . #virt-manager 2.Create a new guest,choose "Import existing disk image",click "Forward",input non-existent disk image path in input field "Provide the existing storage path",eg:sdfsfd Results: After step2, An input error "The import path must point to an existing storage" pops up. According to the result above in the latest version of virt-manager, move this bug from ON_QA to VERIFIED. 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://rhn.redhat.com/errata/RHBA-2017-0686.html |