Bug 1218278
| Summary: | Allow renaming of disks in Virt-Manager | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Robert McSwain <rmcswain> |
| Component: | virt-manager | Assignee: | Giuseppe Scrivano <gscrivan> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | gscrivan, jherrman, juzhou, mzhan, phrdina, tzheng, xiaodwan |
| Target Milestone: | rc | Keywords: | Upstream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | virt-manager-1.2.0-1-el7 | Doc Type: | Bug Fix |
| Doc Text: |
Changing the default guest name when creating a new guest in virt-manager previously caused the guest's disk name to be incorrectly based on the operating system rather than on the guest name. This update modifies virt-manager to properly obtain the name for the created virtual disk from the name of the guest.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 05:25:40 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: | |||
this has been fixed upstream with commit:
commit 27298c8a805826fa7b9ed1e9a0684dd85232e234
Author: Cole Robinson <crobinso>
Date: Wed Oct 2 19:58:21 2013 -0400
addhw: Fix disk naming from 'customize' dialog (bz 744137)
I can reproduce this issue with package: virt-manager-1.1.0-12.el7.noarch steps: 1. Open virt-manager: #virt-manager 2. Create a new virtual machine: Step 1 of 5, choose "Local install media", then click "Forward" Step 2 of 5, use iso: RHEL-6.7-20140415.0-Server-i386-dvd1.iso, then virt-manager will check "OS type"(Linux) and "Version"(Red Hat Enterprise Linux 6.6) automatically, click "Forward". Step 3 of 5, as default , then click "Forward". Step 4 of 5, as default, then click "Forward". Step 5 of 5, Name showing "rhel6.6" as default, if we check "Customize configuration before installation" and click "Finish", in next page, we can check disk name is "/var/lib/libvirt/images/rhel6.6.qcow2". If we change guest name in Step5/5 to "test1", and also check "Customize configuration before installation" and click "Finish", in next page, we can check disk name is kept as "/var/lib/libvirt/images/rhel6.6.qcow2". Result: We cannot rename a disk even if we changed guest name. Then try to verify on new build: virt-manager-1.2.0-2.el7.noarch Steps as above: On Step 5 of 5, guest name "rhel6.6" was set as default, if we check "Customize configuration before installation" and click "Finish", in next page, we can check disk name is "/var/lib/libvirt/images/rhel6.6.qcow2". If we change guest name in Step5/5 to test2, and also check "Customize configuration before installation" and click "Finish", in next page, we can check disk name is "/var/lib/libvirt/images/test2.qcow2". Result: We can rename a disk via virt-manager, and the storage name matches the VM's name. According to aboves steps, 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 |
1. Proposed title of this feature request Allow renaming of disks in Virt-Manager. 3. What is the nature and description of the request? Virt-manager upon updating to version 1.1.0-12 from version 0.10.0-20 in RHEL7 at least, the name field was moved to the last page of the VM build interface. This resulted in all storage files being named after the OS version you are running, no matter the VM Name you define. 4. Why does the customer need this? (List the business requirements here) If you use the same OS for many of your VMs, managing the storage could become quickly confusing since unrelated VMs will have similar "rhel7.0-1.qcow2" names. 5. How would the customer like to achieve this? (List the functional requirements here) The old way of the qcow/storage files being named after the VM's name would be preferred for clarity of the storage. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Using virt-manager, create a VM and name it something other than the OS's name. Other variables should be irrelevant. Once it is created, check the storage behind the VM and see what name the file was given. It should match the VM's name and not the OS's name. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? Not that I was able to find as of 04/23/15 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? RHEL7 is what it was discovered on, so this would be preferred to be first in line. Unsure if this actually affects RHEL5/6. 9. Is the sales team involved in this request and do they have any additional input? No. 10. List any affected packages or components. Virt-manager version 1.1.0-12 11. Would the customer be able to assist in testing this functionality if implemented? Yes.