Bug 1573789

Summary:	Come up with new FQDN wizard which will allow user to enter fqdn for all hosts during Gluster deployment in Cockpit
Product:	[oVirt] cockpit-ovirt	Reporter:	Gobinda Das <godas>
Component:	Gdeploy	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bipin <bshetty>
Severity:	high	Docs Contact:
Priority:	high
Version:	0.11.7	CC:	bshetty, bugs, dfediuck, godas, sabose, sasundar
Target Milestone:	ovirt-4.2.5	Flags:	rule-engine: ovirt-4.2? sasundar: planning_ack? rule-engine: devel_ack+ bshetty: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.25-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-31 15:27:16 UTC	Type:	Bug
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:	1574881
Bug Blocks:	1582207

Description Gobinda Das 2018-05-02 09:41:16 UTC

Description of problem:
Currently we are doing HE deployment by giving IP.So to auto create other Storage Domain, if will use IP then creation may fail because the gluster ip and HE ip may belongs to different networks and both may not be reachable from each other.So in deployment wizard we need to ask user to enter fqdn if auto add 2nd and 3rd hosts and SD needed.
This is optional to user. 

Version-Release number of selected component (if applicable):


How reproducible:
100% if both ips not reachable with each other.

Steps to Reproduce:
1.
2.
3.

Actual results:
Fails if both ips not reachable with each other

Expected results:
Auto create other SD should work

Additional info:

Comment 2 bipin 2018-05-31 13:15:52 UTC

Could verify the bug in the latest cockpit-ovirt-dashboard-0.11.25-1.
Adding the screeshot for the newly added FQDN wizard.

Comment 4 Red Hat Bugzilla Rules Engine 2018-06-18 16:14:47 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 7 Sandro Bonazzola 2018-07-31 15:27:16 UTC

This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

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