Bug 1715430

Summary: Storage Domains should be created irrespective of automatic host addition
Product: [oVirt] cockpit-ovirt Reporter: bipin <bshetty>
Component: gluster-ansibleAssignee: Gobinda Das <godas>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: high    
Version: 0.13.1CC: bugs, lsvaty, rhs-bugs, sabose, sasundar
Target Milestone: ovirt-4.4.0Flags: sasundar: ovirt-4.4?
Target Release: 0.14.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.14.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1715428 Environment:
Last Closed: 2020-08-05 06:09:54 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: 1715428    

Description bipin 2019-05-30 10:32:35 UTC 
+++ This bug was initially created as a clone of Bug #1715428 +++

Description of problem:
======================
Currently the storage domains are created only when the additional FQDN are provided. 

Version-Release number of selected component (if applicable):
===========================================================
RHHI-V 1.6

How reproducible:
================

Steps to Reproduce:
==================
1.
2.
3.

Actual results:
==============


Expected results:
================


Additional info:
===============
Comment 1 SATHEESARAN 2019-05-30 12:38:38 UTC 
@Gobinda,

We need to make sure that the storage domains are created with back-end FQDN
Comment 4 SATHEESARAN 2020-06-16 02:58:28 UTC 
Verified with RHVH 4.4.1 and cockpit-ovirt-dashboard-0.14.8

Now, there is no option available for the user to treat additional hosts as optional.
2 other hosts are added to the cluster.
Storage domains are created automatically
Comment 5 Sandro Bonazzola 2020-08-05 06:09:54 UTC 
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.