Bug 1855178 - brickEvict/deviceRemove is not working when node is unreachable
Summary: brickEvict/deviceRemove is not working when node is unreachable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: OCS 3.11.z Async
Assignee: Nitin Goyal
QA Contact: susgupta
URL:
Whiteboard:
Depends On:
Blocks: 1850072 1858937
TreeView+ depends on / blocked
 
Reported: 2020-07-09 07:28 UTC by Nitin Goyal
Modified: 2020-09-30 15:17 UTC (History)
9 users (show)

Fixed In Version: heketi-9.0.0-9.5.el7rhgs
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1858937 (view as bug list)
Environment:
Last Closed: 2020-09-30 15:17:24 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4143 0 None None None 2020-09-30 15:17:48 UTC

Description Nitin Goyal 2020-07-09 07:28:12 UTC 
Description of problem:
Brick Evict or device remove is failing with the error "Unable to get volume info from gluster node" when the node is down where brick or device exist

Version-Release number of selected component (if applicable):
3.11.5-async
heketi-9.0.0-9.3

How reproducible:
100%

Steps to Reproduce:
1. Create 4 node cluster
2. Create some vols
3. Bring down the one node
4. Remove the device or brick from the node which is down

Actual results:


Expected results:


Additional info:

Upstream Issue: https://github.com/heketi/heketi/issues/1744
Comment 16 errata-xmlrpc 2020-09-30 15:17:24 UTC 
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 (Moderate: OCS 3.11.z async security, bug fix, and enhancement update), 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/RHSA-2020:4143
Note You need to log in before you can comment on or make changes to this bug.