Bug 1490818
Summary: | [Gluster-block]: Block continues to exist in a non-healthy state after a failed create | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sweta Anandpara <sanandpa> | ||||
Component: | gluster-block | Assignee: | Prasanna Kumar Kalever <prasanna.kalever> | ||||
Status: | CLOSED ERRATA | QA Contact: | Sweta Anandpara <sanandpa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | cns-3.9 | CC: | pkarampu, prasanna.kalever, rhs-bugs, sanandpa, storage-qa-internal | ||||
Target Milestone: | --- | ||||||
Target Release: | CNS 3.10 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | gluster-block-0.2.1-18.el7rhgs | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-09-12 09:25:17 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: | |||||||
Bug Blocks: | 1568861 | ||||||
Attachments: |
|
Description
Sweta Anandpara
2017-09-12 10:08:42 UTC
Have received a confirmation from CNS qe that this will not be an issue with heketi. Not proposing it as a blocker for rhgs 3.3.0. Reverified this on the build glusterfs-3.8.4-54.12 and gluster-block-0.2.1-20 and tcmu-runner-1.2.0-20. Executed gluster-block creates multiple times in a loop and did not see any failed create. Also, killed one of the ha peer gluster-blockd service in the middle, and that was gracefully handled. Did not see any other traceback than what is already being tracked in BZ 1595176. Moving this bug to verified. Detailed logs will be attached. Created attachment 1455448 [details]
verification logs rhgs331-async
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/RHEA-2018:2691 |