Bug 1463066
| Summary: | "Clone this disk" button should disable for scsi disk guest in virt-manager GUI | ||
|---|---|---|---|
| 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: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 7.4 | CC: | mxie, phrdina, tzheng, xiaodwan |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-manager-1.5.0-2.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-06 13:07:59 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-06-20 03:49:52 UTC
Upstream commit:
commit 26a433fc421b7c23e02deb8fe84cdedc21fd8f95
Author: Pavel Hrdina <phrdina>
Date: Thu Feb 28 11:47:40 2019 +0100
virtManager: clone: check which storage pools supports volume cloning
I can reproduce this issue with package:
virt-manager-1.5.0-1.el7.noarch
Steps to Reproduce:
1. Installed a guest with disk on iscsi pool.
# virsh dumpxml rhel7.6-iscsi
...
<disk type='block' device='disk'>
<driver name='qemu' type='raw' cache='none' io='native'/>
<source dev='/dev/disk/by-path/ip-10.73.194.15:3260-iscsi-iqn.2001-05.com.equallogic:0-8a0906-8771f7d03-573263eebf54d2c2-s1-rwu-v2v-libvirt-lun-0'/>
<backingStore/>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</disk>
...
2. Then clone it to rhel7.6-iscsi-clone.
2.1 Select guest: rhel7.6-iscsi
2.2 Right click guest: rhel7.6-iscsi
2.3 Select 'Clone' to clone guest.
3. In "Clone Virtual Machine" page, change Storage from the defualt item 'Share disk with rhel7.6-iscsi' to "Clone this disk" then click "Clone".
Result:
Clone failed with error:Error creating virtual machine clone 'rhel7.6-iscsi-clone': missing source information for device vda
Then try to verify this bug with new build:
virt-manager-1.5.0-3.el7.noarch
virt-install-1.5.0-3.el7.noarch
libvirt-4.5.0-16.el7.x86_64
qemu-kvm-rhev-2.12.0-27.el7.x86_64
libvirt-python-4.5.0-1.el7.x86_64
1.Check that the iscsi pool does not support cloning.
1.1 Select guest: rhel7.6-iscsi
1.2 Right click guest: rhel7.6-iscsi
1.3 Select 'Clone' to clone guest.
2. In "Clone Virtual Machine" page, all options to clone or share disk is disabled.
Result:as expected results,unable to clone with warning info: Storage can not be shared or cloned.
I also did tests for cloning guests with gluster pool,scsi pool and disk,please have a look when you have time.Thank you so much.
https://docs.google.com/spreadsheets/d/1dUS_dvQiPuz024xLEd0IO67C8hDBuP2F2_WeUSHH-pI/edit#gid=0
Hi, thanks for that detailed testing:
dir: OK
disk: The issue here is that virt-manager doesn't know how to create default volume name as
it has to follow kernel naming rules (/dev/sda1, /dev/nvme0n1p1, ...) so by default it
will fail with that error message. When I selected the target volume manually it faild
with error message that cloning to existing volume is not supported.
This should be probably fixed by not allowing to clone the disk.
fs: OK
gluster: Works for me as expected, I can only select share disk.
iscsi: Works for me as expected, cloning disk is disable. I should check if we can allow
sharing for iscsi.
logical: OK
netfs: OK
rbd: not supported
scsi: Works for me as expected, cloning disk is disable. I should check if we can allow
sharing for scsi.
sheepdog: not supported
zfs: not supported
Hi Pavel, Thank you so much for your checking. If a new bug occurs in the above scenario, we will report it instead of continuing to add it to a new comment on the current bug. I remove the bug status from ON_QA to VERIFIED based on above results. 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/RHBA-2019:2232 |