Bug 1856685

Summary: [Day2] Fails to crate new volume, with the cluster of 6 nodes
Product: [oVirt] cockpit-ovirt Reporter: SATHEESARAN <sasundar>
Component: gluster-ansibleAssignee: Gobinda Das <godas>
Status: CLOSED DUPLICATE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: high    
Version: 0.14.9CC: bugs, godas, michal.skrivanek, mtessun, rcyriac, rhs-bugs
Target Milestone: ovirt-4.4.1-1Flags: mtessun: ovirt-4.4+
mtessun: blocker+
mtessun: planning_ack+
sbonazzo: devel_ack+
sasundar: testing_ack+
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: 1856682 Environment:
Last Closed: 2020-07-21 10:12:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description SATHEESARAN 2020-07-14 08:31:55 UTC 
Description of problem:
------------------------
Creation of new volume, as part of Day2 operation from web console (cockpit) with 3 node cluster works good. The same procedure with 6 nodes cluster fails to create new volume


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
cockpit-ovirt-dashboard-0.14.9

How reproducible:
----------------
Always


Steps to Reproduce:
-------------------
1. Create a 6 node RHHI-V deployment
2. From webconsole (cockpit), try to create new volume

Actual results:
-----------------
Dialog opens up to list the host, after proceeding to the next tab,
the dialog closes


Expected results:
-----------------
Volume create should be successful

--- Additional comment from RHEL Program Management on 2020-07-14 08:30:32 UTC ---

This bug is automatically being proposed for RHHI-V 1.8 release at Red Hat Hyperconverged Infrastructure for Virtualization product, by setting the release flag 'rhiv‑1.8' to '?'.

If this bug should be proposed for a different release, please manually change the proposed release flag.
Comment 1 Martin Tessun 2020-07-14 09:14:03 UTC 
This should work with any number of gluster nodes - so we should test all supported combinations (which I hope we already do).

One additional question: Is that the documented default procedure for creating new gluster volumes on a hyperconverged environment?
Comment 3 Michal Skrivanek 2020-07-21 10:12:55 UTC 

*** This bug has been marked as a duplicate of bug 1859063 ***