Bug 1929050

Summary:	Add the ability to unset the migration network
Product:	Migration Toolkit for Virtualization	Reporter:	Fabien Dupont <fdupont>
Component:	User Experience	Assignee:	Mike Turley <mturley>
Status:	CLOSED ERRATA	QA Contact:	Igor Braginsky <ibragins>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	medium
Version:	2.0.0	CC:	amastbau, nachandr
Target Milestone:	---	Keywords:	RFE
Target Release:	2.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-10 17:11:27 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:

Description Fabien Dupont 2021-02-16 06:15:43 UTC

Description of problem:

Once a migration network has been selected for a VMware host, it is only possible to select another network as migration network, not reset to no migration network.

It is possible that the users have invalid credentials and that until they retrieve valid credentials they want to fall back to the default behavior, i.e. connect to vCenter and use the management network. And this is currently not possible.

From a technical point of view, this would mean deleting the Host CR.

Comment 1 Fabien Dupont 2021-03-31 06:46:19 UTC

This should be part of build 2.0.0-8 / iib:62459.

Comment 2 Avital Pinnick 2021-03-31 07:55:33 UTC

Added to docs

Comment 3 Amos Mastbaum 2021-04-27 12:18:18 UTC

@fdupont i am not sure about the expected behavior.

The only way to remove the host configuration is to delete the host CR (api), as you say.
In The UI, it is only possible edit the host.

If this is the case, than this BZ can be set to verified.

Comment 4 Mike Turley 2021-04-27 13:28:27 UTC

@amastbau, the UI does have this capability. When you select the Management Network as the network for a Host, the UI just deletes that host CR instead of editing it.

Comment 5 Amos Mastbaum 2021-05-07 04:13:45 UTC

build 2.0.0-8 / iib:72981

Comment 8 errata-xmlrpc 2021-06-10 17:11:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (MTV 2.0.0 images), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2021:2381