Bug 1472002
Summary: | Trying to use user:glfs with vmware | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Mike Ciccarelli <techno10> |
Component: | unclassified | Assignee: | bugs <bugs> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.10 | CC: | bugs, prasanna.kalever, techno10 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-20 18:29:06 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: |
Description
Mike Ciccarelli
2017-07-17 22:51:55 UTC
This seems like a tcmu-runner problem (it does not know about certain events?). What version of tcmu-runner are you using, and do you have the same problem if you use a non-Gluster storage backend? 1) I had similar issues with tcmu-running versions 1.1.3-2.fc26 and 1.2. I compiled 1.2 from source. 2) I do not have the same issue if I use fileio backstore in targetcli. I actually opened a github issue for tcmu-runner as well and it looks like they have acknowledged the issue and are aware of it. I opened the tcmu-runner issue first but then I thought it might actually be related to glusterfs as they wrote the user:glfs module? thanks, Mike Ciccarelli This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately. |