Bug 1517119
Summary: | virt-manager should not report error after deleting a transient domain | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | zhoujunqin <juzhou> |
Component: | virt-manager | Assignee: | Pavel Hrdina <phrdina> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.5 | CC: | kuwei, lmiksik, mxie, tzheng, xiaodwan |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virt-manager-1.4.3-3.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 11:43:03 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: | |
Embargoed: |
Description
zhoujunqin
2017-11-24 09:21:14 UTC
Upstream commit: commit b9bc3b605a96920d3e225d472d549864205e92ce Author: Pavel Hrdina <phrdina> Date: Fri Nov 24 17:26:59 2017 +0100 delete: undefine only persistent domain Try to verify this bug with new build: virt-manager-1.4.3-3.el7.noarch Steps: 1. Create a transient domain with an existing xml file. # virsh create test.xml Domain test created from test.xml # virsh dominfo test Id: 11 Name: test UUID: aaf2501b-53c6-4f14-9cfc-75b5b8efe6f6 OS Type: hvm State: running CPU(s): 1 CPU time: 17.1s Max memory: 1048576 KiB Used memory: 1048576 KiB Persistent: no------------------------>It's a transient domain Autostart: disable Managed save: no Security model: selinux Security DOI: 0 Security label: system_u:system_r:svirt_t:s0:c301,c1009 (enforcing) 2. Launch virt-manager. # virt-manager 3. Delete domain test. (Select 'test', then right click it, select 'Delete'.) Result: Domain 'test' can be deleted successfully with no error. So move this bug from ON_QA to VERIFIED status, thanks. 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://access.redhat.com/errata/RHEA-2018:0726 |