Bug 1673277
| Summary: | "Volume Option cluster.granular-entry-heal=enable could not be set" when using "Optimize for Virt store" | |||
|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Netbulae <info> | |
| Component: | Gluster | Assignee: | Kaustav Majumder <kmajumde> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.30.0 | CC: | bugs, godas, kmajumde, lsvaty, michal.skrivanek, sabose, sasundar | |
| Target Milestone: | ovirt-4.4.0 | Keywords: | ZStream | |
| Target Release: | 4.40.5 | Flags: | sasundar:
ovirt-4.4?
sbonazzo: planning_ack? godas: devel_ack+ sasundar: testing_ack+ |
|
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | vdsm-4.40.5 | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1693187 (view as bug list) | Environment: | ||
| Last Closed: | 2020-08-05 06:10:11 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: | 1693187 | |||
|
Description
Netbulae
2019-02-07 08:35:24 UTC
Kaustav, any update on patches? Two patches posted with different approaches. Kindly suggest one to go further. As confirmed with Gobinda, this fix for this bug will targeted for RHV 4.3.6 Tested with vdsm-4.30.29 Still hit the problem, looks like the code path still uses 'volume set'. The behavior as observed: 1. When volume is just created, 'optimize for virt-store' works 2. When the volume is started, 'optimize for virt-store' fails. Expectation: At any stage of volume: created, started, or stopped, volume set operation should not throw any error In this case, it fails for 'granular-entry-heal' Information Replica 3 volume when set with 'granular-entry-heal' during 'optimize for virtstore', should do check for some conditions: 1. When the volume is just created, use 'gluster volume set' to be used 2. Once the volume is in stopped or started state, 'gluster volume heal' command to be used This bug needs fix that will be addressed with patch from Kaustav. ( As we discussed in Google chat platform ) This bug is not a blocker as all the volume options are set through gluster-ansible for deployment. This issue affects only the customers that try to optimize volume ( that is already started ) for virt store from RHV Manager UI. Considering this, the impact/severity is low in this case Re-targeting this bug for RHV 4.3.7 Hi, Yes can be moved to 4.4. So can you abandon https://gerrit.ovirt.org/#/c/104071/ ? Done Tested with RHV Manager 4.4.1.2-0.10.el8ev and vdsm-4.40.20-1.el8ev.x86_64 1. When volume is just created, 'optimize for vmstore' from RHV Manager Admin portal enables granular-entry-heal 2. When volume is started once, 'optimize for vmstore' from RHV Manager Admin portal fails to set granular-entry-heal, but the value is set with 'gluster volume heal' command This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 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. |