Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
An error message pops up if delete the windows guest in installation procedure.
Version-Release number of selected component (if applicable):
virt-manager-1.2.1-2.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. Launch virt-manager: #virt-manager.
2. Click New button and choose "Local install media(ISO image or CDROM)". Click Forward, choose a windows iso file.
3. Follow the tips to install the guest.
4. when the installation begins check the image file.
# ls /var/lib/libvirt/images/win7.qcow2
/var/lib/libvirt/images/win7.qcow2
5. Right click the guest, click Delete, Check "Delete associated storage files", Check the image file "/var/lib/libvirt/images/win7.qcow2" and click Delete.
Actual results:
1. An error message box pops up.
Error continue install: Cannot access storage file '/var/lib/libvirt/images/win7.qcow2'(as uid:107, gid:107): No such file or directory
2. Check the image file and it has been deleted.
# ls /var/lib/libvirt/images/win7.qcow2
ls: cannot access /var/lib/libvirt/images/win7.qcow2: No such file or directory
3. The win7 guest still exists and is not deleted.
# virsh list --all
Id Name State
----------------------------------------------------
- win7 shut off
Expected results:
The guest should be deleted successfully and no error pops up.
Additional info:
1. This doesn't occur with rhel guest.
2. This doesn't occur if deleting a well-installed windows guest.
Upstream commit:
commit f628c3e266c4e4326bf844e774ad31b96e97d645
Author: Pavel Hrdina <phrdina>
Date: Fri May 13 17:28:03 2016 +0200
create: skip continue-install restart if user destroys VM
Commit 159e4af1 fixed a case where VM was started if user destroyed VM
while installing it. This moves the code before we check whether we
need to restart the VM in order to continue in installation (windows
requires that).
I can reproduce this bug with package:
virt-manager-1.3.2-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. Launch virt-manager: #virt-manager.
2. Click New button and choose "Local install media(ISO image or CDROM)". Click Forward, choose a windows iso file.
3. Follow the tips to install the guest.
4. Right click the guest, click Delete, Check "Delete associated storage files", Check the image file "/var/lib/libvirt/images/win7.qcow2" and click Delete.
5. Check the image file after deleting.
#ls /var/lib/libvirt/images/win7.qcow2
Results:
After step4, the guest can be deleted successfully without error.
After step5, the image file does not exist.
#ls /var/lib/libvirt/images/win7.qcow2
ls: cannot access /var/lib/libvirt/images/win7.qcow2: No such file or directory
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