Bug 1671599
| Summary: | 'Allocation' under Storage volume quota for qcow2 format volume is redundant | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | 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: | 8.0 | CC: | crobinso, mxie, tzheng, xiaodwan, zili | ||||||
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
||||||
| Target Release: | 8.0 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | virt-manager-2.2.0-1.el8 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-11-05 21:19: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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1525671 [details]
Screenshot-2
I believe this was fixed as part of:
commit 4b5cfe3cbbe67ccc5c9d678e9758cafd098f0140
Author: Cole Robinson <crobinso>
Date: Sun Feb 3 12:37:41 2019 -0500
createvol: Fix showing backing store UI on first run (bz 1670266)
Try to verify this bug with build: virt-manager-2.2.1-1.el8.noarch virt-install-2.2.1-1.el8.noarch libvirt-4.5.0-24.module+el8.1.0+3205+41ff0a42.x86_64 qemu-kvm-2.12.0-77.module+el8.1.0+3382+49219945.x86_64 Steps: 1. Launch virt-manager # virt-manager. 2. Double click one connection to active it, here i use 'QEMU/KVM' 3. Click Edit->Connection Details. 4. Click 'Storage' tab on host Connection details dialogue. 5. Click on one active storage pool at the left area, here i use 'default'. 6. Click New Volume button '+'. 7. Fill out volume name, keep default format as qcow2, and set Max Capacity. Result: After step 7, Only shows 'Max Capacity' size for qcow2 format volume, it's as expected. So I 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://access.redhat.com/errata/RHSA-2019:3464 |
Created attachment 1525670 [details] Screenshot-1 Description of problem: 'Allocation' under Storage volume quota for qcow2 format volume is redundant Version-Release number of selected component (if applicable): virt-manager-2.0.0-2.el8.noarch virt-manager-common-2.0.0-2.el8.noarch qemu-kvm-2.12.0-60.module+el8+2725+0ab65287.x86_64 virt-install-2.0.0-2.el8.noarch python3-libvirt-4.5.0-1.module+el8+2529+a9686a4d.x86_64 libvirt-4.5.0-20.module+el8+2724+8292f19c.x86_64 How reproducible: 100% Steps to Reproduce: 1. Launch virt-manager # virt-manager. 2. Double click one connection to active it, here i use 'QEMU/KVM' 3. Click Edit->Connection Details. 4. Click Storage tab on host Connection details dialogue. 5. Click on one active storage pool at the left area, here i use 'default'. 6. Click New Volume button '+'. 7. Fill out volume name, keep default format as qcow2, and set Max Capacity. Actual results: 'Allocation' size also displays for qcow2 format volume, please see Screenshot-1. Expected results: Only shows 'Max Capacity' size for qcow2 format volume. Additional info: After i switch volume format from 'qcow2'->'raw'->'qcow2', then it only shows 'Max Capacity' size for qcow2 format volume correctly, please see Screenshot-2