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 842389 - should not prompt to delete the associated storage files if it's the physical devices.
Summary: should not prompt to delete the associated storage files if it's the physical...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: virt-mgr-maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 842390
TreeView+ depends on / blocked
 
Reported: 2012-07-23 17:19 UTC by Xiaowei Li
Modified: 2015-01-27 00:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 842390 (view as bug list)
Environment:
Last Closed: 2012-07-23 17:43:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Xiaowei Li 2012-07-23 17:19:16 UTC
Description of problem:


Version-Release number of selected component (if applicable):
# virsh version
Compiled against library: libvir 0.9.11
Using library: libvir 0.9.11
Using API: QEMU 0.9.11
Running hypervisor: QEMU 1.0.0


How reproducible:
100%

Steps to Reproduce:
1. using the physical devices as the storage pool.
# virsh vol-list NPIV_host7
Name                 Path                                    
-----------------------------------------
unit:0:0:1           /dev/disk/by-path/pci-0000:15:00.1-fc-0x500173815f9e0111-lun-1
unit:0:1:1           /dev/disk/by-path/pci-0000:15:00.1-fc-0x500173815f9e0110-lun-1
unit:0:2:1           /dev/disk/by-path/pci-0000:15:00.1-fc-0x500173815f9e0113-lun-1
unit:0:3:1           /dev/disk/by-path/pci-0000:15:00.1-fc-0x500173815f9e0112-lun-1

2. attach the volume in pool NPIV_host7 to the guest
3. delete the guest. virt-manager will prompt to delete the associated storage file. If the users select to delete it, will fail. 

so the virt-manager should not list the un-removable storage files while deleting the guest.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dave Allan 2012-07-23 17:43:18 UTC
There are many reasons why storage might be unremovable, most of which are unverifiable until an attempt is actually made to remove it.  Virt-manager has no way of knowing in advance what storage is unremovable, so this BZ is CANTFIX.


Note You need to log in before you can comment on or make changes to this bug.