Bug 1746728
Summary: | Day 2 [Expand Volume]: Logical size is incorrect while providing the LV size | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] cockpit-ovirt | Reporter: | bipin <bshetty> | ||||||
Component: | gluster-ansible | Assignee: | Parth Dhanjal <dparth> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | bipin <bshetty> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 0.13.6 | CC: | bugs, rhs-bugs, sabose | ||||||
Target Milestone: | ovirt-4.3.6 | Keywords: | ZStream | ||||||
Target Release: | 0.13.8 | Flags: | sasundar:
ovirt-4.3?
sasundar: blocker? sasundar: planning_ack? godas: devel_ack+ sasundar: testing_ack+ |
||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | cockpit-ovirt-0.13.8 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | 1746724 | Environment: | |||||||
Last Closed: | 2019-09-26 19:43:35 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1746724, 1748891 | ||||||||
Attachments: |
|
Description
bipin
2019-08-29 07:31:42 UTC
Created attachment 1609288 [details]
UI_Screenshot
Expand volume feature volume with VDO is not elegant, without automatic computation of LV size, which is 10 times the size of input size. Marking this feature as blocker Created attachment 1612184 [details]
Verified_UI_Screenshot
Verified the bug using cockpit-ovirt-dashboard-0.13.8-1.el7ev.noarch. The logical size now displays correct value corresponding to the LV size. Have attached the verified screenshot above. This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |