Bug 1842767
Summary: | Unable to call volumeEmptyCheck in vdsm-gluster due to errors in vdsm-gluster | |||
---|---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Kaustav Majumder <kmajumde> | |
Component: | Gluster | Assignee: | Kaustav Majumder <kmajumde> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 4.40.1 | CC: | bugs, godas, sabose | |
Target Milestone: | ovirt-4.4.1 | Flags: | sabose:
ovirt-4.4?
sasundar: blocker? sasundar: planning_ack? godas: devel_ack+ sasundar: testing_ack+ |
|
Target Release: | 4.40.20 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | vdsm-4.40.20 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1844348 (view as bug list) | Environment: | ||
Last Closed: | 2020-08-05 06:24:41 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: | 1844348 |
Description
Kaustav Majumder
2020-06-02 05:03:04 UTC
Hmmm, are you running with libgfapi? (In reply to Yaniv Kaul from comment #1) > Hmmm, are you running with libgfapi? With and without, have checked. Both giving the same errors. (In reply to Yaniv Kaul from comment #1) > Hmmm, are you running with libgfapi? gfapi is also used in vdsm to check volume size - this has no relation to the gfapi driver in qemu. The failure seen here is from the internal usage of gfapi to query volume size. Posted a patch. Please review. Verified with vdsm-4.40.22-1.el8ev.x86_64 There are no exceptions see with supervdsm.log or vdsm.log related to 'vdsm.gluster.exception.GlusterVolumeEmptyCheckFailedException' This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 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. |