RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1232599 - Would you like to reuse this storage? dialogue should not pop up when import an existent but not used image file
Summary: Would you like to reuse this storage? dialogue should not pop up when import ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.2
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-17 06:46 UTC by Xiaodai Wang
Modified: 2015-11-19 05:26 UTC (History)
3 users (show)

Fixed In Version: virt-manager-1.2.1-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 05:26:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2206 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2015-11-19 08:17:29 UTC

Description Xiaodai Wang 2015-06-17 06:46:42 UTC 
Description of problem:
Would you like to reuse this storage? dialogue should not pop up when import an existent but not used image file.

Version-Release number of selected component (if applicable):
virt-manager-1.2.0-4.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. make sure default Storage format is "qcow2" in Preferences(virt-manager-->Edit-->Preferences-->New VM-->Storage format) and "/var/lib/libvirt/images/generic.qcow2" is existent.
2. Launch virt-manager, Click "Create a new virtual machine" icon, choose "Import existing disk image", Click "Forward".
3. Click "Browse" button, Select one existent image file,such as demo.img, keep OS type and Version to "Generic", and click Forward.


Actual results:
Would you like to reuse this storage? dialogue pops up.

The following storage already exists, but is not in use by any virtual machine:
/var/lib/libvirt/images/generic.qcow2
Would you like to reuse this storage?

Expected results:
1. The image file info in the dialogue is wrong. Because demo.img but generic.qcow2 is the file i want to reuse.
2. I think it's not necessary to pop up this dialogue when the image file is not used by any VM.

Additional info:
At step3, if select generic.qcow2, The same dialogue still occurs.
Comment 2 Pavel Hrdina 2015-07-23 12:45:05 UTC 
Upstream patch proposed:

https://www.redhat.com/archives/virt-tools-list/2015-July/msg00119.html
Comment 3 Pavel Hrdina 2015-08-11 12:06:33 UTC 
Upstream commit:

commit 9f26bbb5e9e1c6837994883d1c682421c829f080
Author: Pavel Hrdina <phrdina>
Date:   Thu Jul 23 14:31:55 2015 +0200

    addstorage: remove _check_ideal_path
    
    This feature has been added few years ago.  I don't think, that it's a
    good feature, as it can ask a user to use different storage than he
    actually wants to use.  One thing is automatically create a new storage
    for user, if he let as do that, but we shouldn't annoy a user with this
    question as he probably don't want to use the proposed storage.  For
    example he would like to use different storage pool or while importing
    existing storage.
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1232599
    
    Signed-off-by: Pavel Hrdina <phrdina>
Comment 6 fwu 2015-08-12 03:36:32 UTC 
I can reproduce this bug with package:
virt-manager-1.2.0-4.el7.noarch

Steps are the same as description above.

Then try to verify with new build:
virt-manager-1.2.1-5.el7.noarch

Steps:
1. Open virt-manager and select default installation storage format as qcow2.
virt-manager --> Edit --> Preferences --> New VM --> Storage format --> qcow2
2. Make sure that "/var/lib/libvirt/images/generic.qcow2" is existent. If not, created a new one.
3. Click "Create a new virtual machine" icon, choose "Import existing disk image", Click "Forward".
4. Click "Browse" button, Select one existent image file, such as test.img, keep OS type and Version to "Generic", and click Forward.

Results:
No pop-up dialogue occurs, the guest can be installed successfully.

According to the result above in the latest version of virt-manager, move this bug from ON_QA to VERIFIED.
Comment 8 errata-xmlrpc 2015-11-19 05:26:34 UTC 
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-2015-2206.html
Note You need to log in before you can comment on or make changes to this bug.