Bug 1336099

Summary:	Rename Verify Credentials to Skip SSL verification during v2v
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	ovirt-engine	Assignee:	Sharon Gratch <sgratch>
Status:	CLOSED ERRATA	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.6.0	CC:	amarchuk, gklein, lsurette, melewis, nsimsolo, rbalakri, Rhev-m-bugs, srevivo, tgolembi, tjelinek, ykaul
Target Milestone:	ovirt-4.0.0-rc
Target Release:	4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	With this update, the Verify Credentials field in the Import Virtual Machines window and the Add/Edit Provider windows has been renamed to SSL Verification. This is clarify that the field should be used for SSL verification.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 20:39:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Skrivanek 2016-05-14 07:46:38 UTC

Description

import vm from vmware provider on RHEVM 3.6 would definitely failed if the VCenter do not use certificate that is included on cert bundle.
So vcenter deployment that use self certificate would 100% failed to use GUI based vm import capabilities.

if were using command line for virt-v2v, we are enable to add ?no_verify=1, which we cannot add this option on GUI based.

Comment 2 Michal Skrivanek 2016-05-17 12:54:42 UTC

is it "Verify Credentials"?

Comment 3 Tomáš Golembiovský 2016-05-18 12:07:51 UTC

Yes that's it. We should rename it to "Verify SSL certificate" or something like that.

Comment 4 Sharon Gratch 2016-05-24 11:13:12 UTC

The field was renamed to "SSL Verification".

Comment 6 Nisim Simsolo 2016-06-09 08:04:06 UTC

Verification build: 
ovirt-engine-4.1.0-0.0.master.20160606111312.gitc7af584.el7

Comment 8 errata-xmlrpc 2016-08-23 20:39:28 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, 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://rhn.redhat.com/errata/RHEA-2016-1743.html