Bug 1630689

Summary:	Provide checkbox in Host wizard if user has same host/ip for FQDN to auto add 2nd and 3rd hosts
Product:	[oVirt] cockpit-ovirt	Reporter:	Gobinda Das <godas>
Component:	Gdeploy	Assignee:	Parth Dhanjal <dparth>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	0.11.29	CC:	bugs
Target Milestone:	ovirt-4.2.8	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.38-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-22 10:23:39 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:
Bug Blocks:	1664044

Description Gobinda Das 2018-09-19 06:25:19 UTC

Description of problem:
Now we are allowing user to enter duplicate entry in FQDN wizard if hosts/ips are same as fqdn for auto add 2nd and 3rd hosts.
We should have checkbox which will indicate that both are same.

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


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
No way to avoid duplicate entry for fqdn wizard

Expected results:
Should be avoided duplicate entry for fqdn wizard

Additional info:

Comment 1 SATHEESARAN 2019-01-17 11:29:29 UTC

Tested with cockpit-ovirt-dashboard-0.11.38

New checkbox 'Use same hostnames as in previous step' is available and when checking that the 2nd and 3rd hosts as in previous tab are populated in the FQDN tab automatically

Comment 2 Sandro Bonazzola 2019-01-22 10:23:39 UTC

This bugzilla is included in oVirt 4.2.8 release, published on January 22nd 2019.

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