Bug 1596523
| Summary: | Guaranteed free space implementation differs between replica and arbiter volumes | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | bipin <bshetty> | ||||||
| Component: | Frontend.WebAdmin | Assignee: | Denis Chaplygin <dchaplyg> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | bipin <bshetty> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | future | CC: | bugs, lsvaty, lveyde, rhs-bugs, sabose, sankarshan, sasundar, starfall | ||||||
| Target Milestone: | ovirt-4.2.5 | Flags: | sabose:
ovirt-4.2?
sabose: blocker? bshetty: planning_ack? rule-engine: devel_ack+ sasundar: testing_ack+ |
||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ovirt-engine-4.2.5.2 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
Cause: Arbiter brick was treated as a data brick.
Consequence: Volume physical size was calculated incorrectly
Fix: Arbiter was excluded from the guaranteed size calculations.
Result: Only data nodes participate in the calculations right now, so results are correct.
|
Story Points: | --- | ||||||
| Clone Of: | 1596520 | Environment: | |||||||
| Last Closed: | 2018-07-31 15:31:08 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: | 1596520 | ||||||||
| Attachments: |
|
||||||||
|
Description
bipin
2018-06-29 07:45:05 UTC
Created attachment 1455450 [details]
Screenshot1
Verified the bug in ovirt-engine-4.2.5.2. Steps: ===== 1.Create a arbiter replica volume on a VDO volume using cockpit 2.Once the HE deployment is completed navigate to storage domain 3.The guaranteed free space and free space should be relatively same Attaching the screenshot Created attachment 1470592 [details]
Cockpit_UI_Verified
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.5 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. I'm running into the exact same problem here with the gluster arbiter is being created on 2nd host, while the arbiter LV is created on the 3rd host. This is on the latest version of ovirt.
ovirt-host.x86_64 - 4.3.1-1.el7
This happened during the original hyperconverged HE ansible deploy as well as during subsequent gluster volume creation from cockpit. VDO was not used in this deployment.
Configuration of the volume in ovirt-engine HE UI -
nde1:/gluster_bricks/data1/data1
nde2:/gluster_bricks/data1/data1 (Arbiter)
nde3:/gluster_bricks/data1/data1
lsblk output:
nde1:
└─md101 9:101 0 431.8G 0 raid1
├─gluster_vg_md101-gluster_lv_engine 253:2 0 80G 0 lvm /gluster_bricks/engine
├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tmeta 253:3 0 4M 0 lvm
│ └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm
│ ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm
│ └─gluster_vg_md101-gluster_lv_data1 253:7 0 330G 0 lvm /gluster_bricks/data1
└─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tdata 253:4 0 351.8G 0 lvm
└─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm
├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm
└─gluster_vg_md101-gluster_lv_data1 253:7 0 330G 0 lvm /gluster_bricks/data1
nde2:
└─md101 9:101 0 431.8G 0 raid1
├─gluster_vg_md101-gluster_lv_engine 253:2 0 80G 0 lvm /gluster_bricks/engine
├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tmeta 253:3 0 4M 0 lvm
│ └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm
│ ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm
│ └─gluster_vg_md101-gluster_lv_data1 253:7 0 330G 0 lvm /gluster_bricks/data1
└─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tdata 253:4 0 351.8G 0 lvm
└─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm
├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm
└─gluster_vg_md101-gluster_lv_data1 253:7 0 330G 0 lvm /gluster_bricks/data1
nde3:
└─md101 9:101 0 431.8G 0 raid1
├─gluster_vg_md101-gluster_lv_engine 253:2 0 80G 0 lvm /gluster_bricks/engine
├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tmeta 253:3 0 4M 0 lvm
│ └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm
│ ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm
│ └─gluster_vg_md101-gluster_lv_data1 253:7 0 20G 0 lvm /gluster_bricks/data1
└─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tdata 253:4 0 351.8G 0 lvm
└─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm
├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm
└─gluster_vg_md101-gluster_lv_data1 253:7 0 20G 0 lvm /gluster_bricks/data1
|