Bug 1592642
| Summary: | Unable to uncheck arbiter brick with dedupe and compression enabled | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 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: | unspecified | ||||||||||
| Version: | 0.11.7 | CC: | bshetty, bugs, godas, rbarry, rhs-bugs, sabose, sankarshan, sasundar | ||||||||
| Target Milestone: | ovirt-4.2.5 | Flags: | rule-engine:
ovirt-4.2?
bshetty: planning_ack? rule-engine: devel_ack+ sasundar: testing_ack+ |
||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | cockpit-ovirt-0.11.30-1 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | 1592641 | Environment: | |||||||||
| Last Closed: | 2018-07-31 15:25:25 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: | 1592641, 1596277 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
bipin
2018-06-19 03:38:03 UTC
bipin, FYI, VDO configuration is per device/volume level not brick level. If you want to disable vdo for particular volume then you need to have separate device.With same device you can't check one and uncheck another one. (In reply to Gobinda Das from comment #3) > bipin, > FYI, VDO configuration is per device/volume level not brick level. > If you want to disable vdo for particular volume then you need to have > separate device.With same device you can't check one and uncheck another > one. We should be able to disable dedupe/compression on arbiter brick which is on third host - so separate device on the third host Bipin, can you confirm if you're able to uncheck for third host for all bricks? (In reply to Sahina Bose from comment #5) > Bipin, can you confirm if you're able to uncheck for third host for all > bricks? Sahina, This is not possible. I prefer to have the following: 1. replica 3 volume 'engine' with bricks created from 'sdb' from host{1,2,3} 2. replica 3 volume 'vmstore' with bricks created from 'sdc' from host{1,2,3} 3. arbitrated replicate volume with bricks created from 'sdd' from host{1,2,3} In this case, while enabling dedupe & compression on bricks created on 'sdd', it gets selected automatically on the bricks on all other hosts ( host2, host3 ). Now I have prefer to uncheck the dedupe & compression only on the 3rd brick of the volume, on host3. When I uncheck all the bricks are unchecked. Remember here, I choose the same disk name 'sdb' on different hosts. I am **not** creating all the bricks on the disk on the same device, on the same host. I will be attaching the screenshots for the same Created attachment 1456152 [details]
host1 bricks
Created attachment 1456153 [details]
host2 bricks on cockpit UI
Created attachment 1456154 [details]
host3 bricks on cockpit UI
Gobinda, this looks like a bug and not an error in deployment/understanding . Can you address? In this case uncheck for all hosts will be complex.If we are ok with only auto check but not uncheck for all hosts then fine. I will check and update. Fixed the issue. Verified the bug in the component cockpit-ovirt-dashboard-0.11.30-1.el7ev.noarch. Also attaching the screenshot's Steps: ===== 1.Create a arbiter replica volume 2.Uncheck compression and deduplication in the 3rd brick on host3. 3.Complete the deployment. 4.Brick created without dedupe and compression enabled 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. |