Description of problem: Some times heketi is creating volumes and some times it give us error that "no space left" even though we have space left on devices. Version-Release number of selected component (if applicable): 6.0.0.11 Actual results: It is creating volumes 4 times out of 10. Expected results: It should create volumes every time.
This is the scenario where it is failing. N1-r N2-r N3-s #100gb-d #100gb-d #100gb-s #100gb-d #100gb-d #100gb-s #100gb-d #100gb-d #100gb-s N stans for node # stands for device d stands for arbiter disabled s stands for arbiter supported 1. Give the required tag to first and second node. # heketi-cli node settags node_id arbiter:required 2. Give the disable tag on drives of first node and drives of second node. # heketi-cli device settags node_id arbiter:disabled 3. Give supported tag on third node and its devices. # heketi-cli node settags node_id arbiter:supported # heketi-cli devices settags node_id arbiter:supported 4. Create volume. # heketi-cli volume create --size=100 --gluster-volume-options='user.heketi.arbiter true' 5. Try to create 10 volumes atleast. 6. Check that it is actually working according to tags. # heketi-cli topology info # gluster v info
pretty much a duplicate of BZ #1575899. Should be fixed by https://github.com/heketi/heketi/pull/1172 and subsequent fixes (https://github.com/heketi/heketi/pull/1182 ...).
As Michael noted this is nearly but not exactly a duplicate of bug #1575899. Thus it should have the same status and be tested along with that bug.
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