Bug 1629543
| Summary: | The LV size should be equal to the logical size on VDO enabled volumes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] cockpit-ovirt | Reporter: | bipin <bshetty> | ||||
| Component: | Gdeploy | Assignee: | Gobinda Das <godas> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | bipin <bshetty> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 0.11.33 | CC: | bugs, dparth, godas, guillaume.pavese, irosenzw, rhs-bugs, sabose, sankarshan, sasundar | ||||
| Target Milestone: | ovirt-4.3.2 | Flags: | rule-engine:
ovirt-4.3+
|
||||
| Target Release: | 0.12.5 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | cockpit-ovirt-0.12.5 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1629542 | Environment: | |||||
| Last Closed: | 2019-03-19 10:03:20 UTC | Type: | Bug | ||||
| 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: | 1629542 | ||||||
| Attachments: |
|
||||||
|
Description
bipin
2018-09-17 04:22:22 UTC
Parth please look this as priority. @Parth Provide info for LVM Size filed that the lvm will be created with given size i.e. input of the LVM will not be same with VDO logical size. (In reply to Gobinda Das from comment #2) > @Parth Provide info for LVM Size filed that the lvm will be created with > given size i.e. input of the LVM will not be same with VDO logical size. Hey Gobinda! I'll add an Info Icon right next to the LVM Cache Size field. Are we only fixing this via info icon - I thought we had discussed that LV size would change to vdo logical size? sahina, Now vdo logical size calculated based on lv size. It's required redesign of page to fix. So now we gave info to user via info icon. This is a known issue. This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. Ovirt-4.3.1 already released, so moving to ovirt-4.3.2 Verified the bug on the latest cockpit dashboard and could see the LV size is equal to the logical size of VDO volume Components version: ================== cockpit-ovirt-dashboard-0.12.5-1.el7ev.noarch rhvh-4.3.0.5-0.20190313.0+1 Steps: ===== 1. Check the VDO box for the brick you want to have dedupe and compression enabled 2. Once deployed compare the size of the LV and VDO logical size Could see that the ansible playbook generated in the review tab had proper values set. Output: ====== sdb 8:16 0 20T 0 disk └─vdo_sdb 253:12 0 80T 0 vdo ├─gluster_vg_sdb-gluster_lv_data 253:14 0 40T 0 lvm /gluster_bricks/data └─gluster_vg_sdb-gluster_lv_vmstore 253:15 0 40T 0 lvm /gluster_bricks/vmstore [root@rhsqa-abc log]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert gluster_lv_data gluster_vg_sdb -wi-ao---- 40.00t gluster_lv_vmstore gluster_vg_sdb -wi-ao---- <40.00t Moving to verified based on above result This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.2 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. |