Bug 1938110
| Summary: | [GSS][RHHI 1.8: Disable the setting lookup-optimize in the virt group] | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | nravinas | |
| Component: | rhhi | Assignee: | Gobinda Das <godas> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhhiv-1.8 | CC: | bkunal, jahernan, lichen, mkalinin, mpandey, pprakash, rcyriac, rhs-bugs, sasundar | |
| Target Milestone: | --- | |||
| Target Release: | RHHI-V 1.8.z Batch Update 4 | |||
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: lookup-optimize option could cause VM corruption at least on RHHI environments. From what we have found so far, it seems related to sharding.The problem happens after expanding or shrinking the volume and doing a rebalance
Fix: Disable lookup-optimize option default in RHHI-V
Result: There should not be any vm corruption by disabling lookup-optimize option.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1939372 1939894 (view as bug list) | Environment: | ||
| Last Closed: | 2021-04-29 05:48:58 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1939372, 1939894, 1939918 | |||
| Bug Blocks: | ||||
|
Description
nravinas
2021-03-12 08:26:58 UTC
This issue will be fixed with gluster-ansible which disables the option lookup-optimize in RHV 4.4.5 based RHHI-V deployments As per our discussion with QE, we agreed that now will go with gluster-ansible sid fix for RHHI-V-1.8.4. Upstream patch: https://github.com/gluster/gluster-ansible-features/pull/47 The option to disable lookup-optimize on the gluster volume is achieved in 2 ways. RHGS 3.5.4 has disabled this option through virt profile. Verified the same with glusterfs-6.0-55.el8rhgs On the other hand, the ansible deployment module also disabled this option during deployment. RHHI-V 1.8.4 will be using the update ansible deployment module ( gluster-ansible-features-1.0.5-11.el8rhgs ), which disables this option during gluster deployment phase. This option is also qualified. This bug will be verified once the required gluster-ansible-features package is available with RHVH 4.4.5 (In reply to SATHEESARAN from comment #8) > The option to disable lookup-optimize on the gluster volume is achieved in 2 > ways. > RHGS 3.5.4 has disabled this option through virt profile. Verified the same > with glusterfs-6.0-55.el8rhgs > On the other hand, the ansible deployment module also disabled this option > during deployment. > > RHHI-V 1.8.4 will be using the update ansible deployment module ( > gluster-ansible-features-1.0.5-11.el8rhgs ), > which disables this option during gluster deployment phase. > > This option is also qualified. This bug will be verified once the required > gluster-ansible-features package is available > with RHVH 4.4.5 gluster-ansible-features-1.0.5-11.el8rhgs is now available with RHVH 4.4.5 |