Bug 1908233

Summary: Order of hosts not preserved for day2 operations
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Gobinda Das <godas>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.8CC: asriram, rhs-bugs
Target Milestone: ---Keywords: Reopened, ZStream
Target Release: RHHI-V 1.8.z Batch Update 4   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-dashboard-0.14.18 Doc Type: Known Issue
Doc Text:
Cause: In day2 operations - create volume, expand volume or expand cluster, the order of hosts is not preserved. This will create problem in the case of arbitrated replicate volume, where the user prefers the particular host to contain the 3rd brick, which is thin in storage Consequence: User may think node3 is arbiter, but we place the arbiter in some other node against the expectation. Workaround (if any): Edit the generated inventory file in preview step and change the hostname which one you intended to be arbiter and save, then proceed. Result: The volume creation should succeed with appropriate arbiter node.
 Story Points: ---
Clone Of:
: 1908234 (view as bug list) Environment:
Last Closed: 2021-04-29 05:49:05 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: 1908234    
Bug Blocks:    

Description SATHEESARAN 2020-12-16 07:31:44 UTC 
Description of problem:
------------------------
When performing day2 operations - create volume, expand volume or expand cluster, the order of hosts is not preserved. This will create problem in the case of arbitrated replicate volume, where the user prefers the particular host to contain the 3rd brick, which is thin in storage.

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

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

Steps to Reproduce:
--------------------
1. Create new volume for day2 operation with host1, host2 and host3 in the input fields
2. Validate the order of hosts in the newly created volume

Actual results:
---------------
Volume are created or expanded with bricks from hosts, but in the incorrect order

Expected results:
-----------------
Volume should be created or expanded with bricks from hosts in the order given per user input in hosts tab
Comment 2 Gobinda Das 2021-01-07 06:25:40 UTC 
As the dependent bug is moved to ovirt-4.4.5, this bug will be included in RHHI-V-1.8.4 once the flag is available.
Comment 4 SATHEESARAN 2021-02-01 17:14:15 UTC 
tested with cockpit-ovirt-dashboard-0.14.18

With RHHI for virtualization 3 node cluster deployed, the day2 operation of creating new volume,
now lists the hosts in the correct order and arbiter node is chosen as expected.
Comment 5 SATHEESARAN 2021-02-01 17:14:32 UTC 
The dependent ovirt bug is in ON_QA state
Comment 8 SATHEESARAN 2021-02-08 09:28:26 UTC 
This bug is verified with comment4
Comment 10 Red Hat Bugzilla 2023-09-15 00:53:07 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days