Bug 1842004

Summary: Addition of IPV6 hosts to hyperconverged cluster fails
Product: [oVirt] ovirt-engine Reporter: SATHEESARAN <sasundar>
Component: Frontend.WebAdminAssignee: Ritesh Chikatwar <rchikatw>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: bugs, godas, rhs-bugs
Target Milestone: ovirt-4.4.1Flags: sasundar: ovirt-4.4?
sasundar: blocker?
sasundar: planning_ack?
pm-rhel: devel_ack+
sasundar: testing_ack+
Target Release: 4.4.1.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.1.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1842003 Environment:
Last Closed: 2020-08-05 06:25:02 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:
Bug Depends On:    
Bug Blocks: 1842003    

Description SATHEESARAN 2020-05-30 05:21:53 UTC
Description of problem:
-----------------------

During the RHHI-V deployment with IPV6 hosts, the additional hosts are tried to be added to the 'Default' cluster and that fails.

Also manually tried adding the hosts to the cluster, and that also fails.


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHV - 4.4.1.1-0.5.el8ev

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

Steps to Reproduce:
---------------------
1. Add the IPV6 hosts to the HC cluster ( cluster with both virt + gluster enabled )

Actual results:
---------------
RHV manager fails to add that host to the cluster erroring out as - "Server already part of another cluster"

Expected results:
-----------------
Addition of IPV6 hosts should be successful

Comment 1 RHEL Program Management 2020-05-30 05:22:01 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 SATHEESARAN 2020-05-30 05:25:13 UTC
This test was done with self-hosted-engine deployment and that localhost is added to the cluster successfully, 
its only the additional hosts when added, fails to add.


Error from /var/log/engine.log
--------------------------------
2020-05-29 17:57:14,668Z WARN  [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-1) [9efe8a20-1e52-4009-89d8-d995a11c31af] Validation of action 'AddVds' failed for user admi
n@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server rhsqa-grafton8-nic2-ipv6.lab.eng.blr.redhat.com,SERVER_ALREADY_PART_OF_ANOTHER_CLUSTER
2020-05-29 17:57:14,672Z WARN  [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-2) [7f5435bd-0dfe-488f-ab2d-a975bd890274] Validation of action 'AddVds' failed for user admi
n@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server rhsqa-grafton9-nic2-ipv6.lab.eng.blr.redhat.com,SERVER_ALREADY_PART_OF_ANOTHER_CLUSTER
2020-05-29 17:57:14,757Z INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (default task-3) [ad74d94a-4437-46cd-8e14-8c0ba6b1fa67] FINISH, ConnectStorageServer
VDSCommand, return: {00000000-0000-0000-0000-000000000000=0}, log id: 21452c07
2020-05-29 17:57:14,929Z ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Server rhsqa-grafton8-nic2-ipv6.lab.eng.blr.redhat.com is already part of another cluster.]
2020-05-29 17:57:14,982Z ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-2) [] Operation Failed: [Server rhsqa-grafton9-nic2-ipv6.lab.eng.blr.redhat.com is already part of another cluster.]

Comment 3 SATHEESARAN 2020-07-12 14:01:05 UTC
Tested with RHV Manager 4.4.1.8-0.7.el8ev and additional hosts are added to the cluster successfully

Comment 4 Sandro Bonazzola 2020-08-05 06:25:02 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.