Bug 1576311 - Volume creation is failing when out of three nodes two of them are taged as arbiter:disabled and one of them is taged as arbiter:supported
Summary: Volume creation is failing when out of three nodes two of them are taged as a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: CNS 3.10
Assignee: John Mulligan
QA Contact: Nitin Goyal
URL:
Whiteboard:
Depends On:
Blocks: 1568862
TreeView+ depends on / blocked
 
Reported: 2018-05-09 08:22 UTC by Nitin Goyal
Modified: 2018-09-12 09:23 UTC (History)
6 users (show)

Fixed In Version: heketi-6.0.0-14.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-12 09:22:13 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2686 0 None None None 2018-09-12 09:23:23 UTC

Description Nitin Goyal 2018-05-09 08:22:43 UTC
Description of problem: Volume creating i failing sometimes, out of 10 6 times it is failing.

Version-Release number of selected component (if applicable):6.0.0.11

Actual results: Volume Creation failing sometimes.

Expected results: Volume creation should happen every time.

Comment 2 Nitin Goyal 2018-05-09 08:30:12 UTC
This is scenario where it is failing

N1-d      N2-d      N3-s
#100gb    #100gb    #100gb
#100gb    #100gb    #100gb
#100gb    #100gb    #100gb

N stands for node
# stands for device
d stands for arbiter disabled
s stands for abiter supported

Steps to reproduce:

1. Give disabled tags to first node and second node
# heketi-cli node settags node_id arbiter:disabled

2. Give supported tag third node
# heketi-cli node settags node_id arbiter:supported

3. Create volumes
# heketi-cli volume create --size=1  --gluster-volume-options='user.heketi.arbiter true'

4. Create 10 vols minimum

Comment 8 errata-xmlrpc 2018-09-12 09:22:13 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, 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:2686


Note You need to log in before you can comment on or make changes to this bug.