| Summary: | Wrong error info when import non-existent disk image from virt-manager GUI | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | 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: | 7.3 | CC: | juzhou, knoel, mxie, mzhan, phrdina, rbalakri, virt-bugs, virt-mgr-maint, xiaodwan |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-manager-1.4.0-1.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1305209 | Environment: | |
| Last Closed: | 2016-11-04 02:01:28 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: | 1305209 | ||
| Bug Blocks: | |||
|
Description
tingting zheng
2016-02-06 06:24:18 UTC
Upstream commit:
commit 7280dcf7dfd2f3b55a342c1ccdd4c5447ddc6045
Author: Pavel Hrdina <phrdina>
Date: Tue Jun 7 13:55:58 2016 +0200
create: report an error if storage doesn't exists for import installation
I can reproduce this bug with package: virt-manager-1.2.8-1.el7.noarch Steps are the same as description above. Then try to verify with new build: virt-manager-1.4.0-1.el7.noarch Steps: 1.Lauch 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-2016-2269.html |