RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1671599 - 'Allocation' under Storage volume quota for qcow2 format volume is redundant
Summary: 'Allocation' under Storage volume quota for qcow2 format volume is redundant
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-manager
Version: 8.0
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-01 02:11 UTC by zhoujunqin
Modified: 2020-11-14 07:46 UTC (History)
5 users (show)

Fixed In Version: virt-manager-2.2.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 21:19:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
Screenshot-1 (129.60 KB, image/png)
2019-02-01 02:11 UTC, zhoujunqin 		no flags Details
Screenshot-2 (128.63 KB, image/png)
2019-02-01 02:11 UTC, zhoujunqin 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3464 0 None None None 2019-11-05 21:20:05 UTC

Description zhoujunqin 2019-02-01 02:11:09 UTC 
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
Comment 1 zhoujunqin 2019-02-01 02:11:55 UTC 
Created attachment 1525671 [details]
Screenshot-2
Comment 2 Cole Robinson 2019-06-15 14:39:15 UTC 
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)
Comment 4 zhoujunqin 2019-07-25 10:55:03 UTC 
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.
Comment 6 errata-xmlrpc 2019-11-05 21:19:40 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.