Bug 1244566
| Summary: | Cannot create a new guest in virt-manager | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Xiaodai Wang <xiaodwan> |
| Component: | virt-manager | Assignee: | Pavel Hrdina <phrdina> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.2 | CC: | juzhou, mzhan, ohudlick, qiguo, qxiao, tzheng |
| Target Milestone: | alpha | Keywords: | Regression, TestBlocker |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-manager-1.2.1-4.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 05:31:45 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
Xiaodai Wang
2015-07-20 02:47:10 UTC
Upstream patch proposed: https://www.redhat.com/archives/virt-tools-list/2015-July/msg00084.html Upstream commit:
commit cce1f89a345e3837dc79b9aac8af9bfb476b326f
Author: Pavel Hrdina <phrdina>
Date: Mon Jul 20 09:19:57 2015 +0200
virtManager/create: update capsinfo sooner in set_conn_state
We need to update/initialize the capsinfo sooner in that function to be
able to call has_install_options().
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1244566
Signed-off-by: Pavel Hrdina <phrdina>
*** Bug 1246973 has been marked as a duplicate of this bug. *** I can reproduce the bug with the build: virt-manager-1.2.1-3.el7.noarch Try to verify this bug with package: virt-manager-1.2.1-4.el7.noarch steps: 1. Launch virt-manager 2. Click the New button to create a new guest. Result: New VM window pops up and create a new guest successfully. 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-2015-2206.html |