Bug 1753898
Summary: | Make block size detection compatible with Gluster storage | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Sahina Bose <sabose> | |
Component: | vdsm | Assignee: | Nir Soffer <nsoffer> | |
Status: | CLOSED ERRATA | QA Contact: | bipin <bshetty> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 4.3.6 | CC: | aefrat, aoconnor, lsurette, nsoffer, pelauter, rdlugyhe, srevivo, tnisan, vjuranek, ycui | |
Target Milestone: | ovirt-4.4.0 | Keywords: | ZStream | |
Target Release: | 4.3.6 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | vdsm-4.30.33 | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1755271 (view as bug list) | Environment: | ||
Last Closed: | 2019-10-10 15:36:50 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1753901 | |||
Bug Blocks: | 1751722, 1755271 |
Description
Sahina Bose
2019-09-20 08:02:40 UTC
According to https://bugzilla.redhat.com/show_bug.cgi?id=1751722#c13 the issue is caused by multiple hosts trying to detect block size using the same file (__DIRECT_IO_TEST__). This is expected to work on posix filesystem but it breaks gluster metadata management. ioprocess will implement block size detection in a way that can work with existing Gluster storage, and vdsm will use this new API instead of accessing __DIRECT_IO_TEST__. Reproducing: - It is very hard to reproduce - race when multiple hosts access same file on gluster volume Testing: - Create gluster storage doman - Create NFS storage domain - Create localfs storage domain - Check that storage domain block size was detected correctly (see StorageDomain.getInfo in vdsm log) This bug fixes an issue in unreleased version, so I don't think we need doc text. The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. (In reply to RHEL Product and Program Management from comment #7) This fixes a regression in internal release to QE that no user could experience, so no doc text is needed. The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. Moving the bug to verified based on the below results: Version: ======= glusterfs-3.12.2-47.5.el7rhgs.x86_64 ioprocess-1.3.0-1.el7ev.x86_64 vdsm-4.30.33-1.el7ev.x86_64 1. Complete the RHHI-V deployment 2. Create a RHEL 7.6 template 3. Create 30 vm's using pool 4. After an hour delete the vm's in the pool 5. Repeat step 3 and step 4 for 3 iteration's 6. Create vm's using template and ran kernel untar and FIO Couldn't see any crash during the test. So moving the bug to verified Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3009 |