Bug 1773472

Summary:	ssl certificate not computed in ovirt v4
Product:	Red Hat Satellite	Reporter:	Yifat Makias <ymakias>
Component:	Compute Resources - RHEV	Assignee:	Yifat Makias <ymakias>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	egolov, inecas, mshira, orabin
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-1.24.0-0.14.RC3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:27:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yifat Makias 2019-11-18 08:37:10 UTC

An error appears when trying to load datacenters when creating a new ovirt compute resource using apiv4.
Error message: Can't send request: SSL peer certificate or SSH remote key was not OK

The reason for this error is a different message error that is returned from a newer version of libcurl package which is used by ovirtsdk.
This libcurl package is apparently used in the newest versions of fedora.

Comment 1 Yifat Makias 2019-11-18 08:37:15 UTC

Created from redmine issue https://projects.theforeman.org/issues/28280

Comment 4 Yifat Makias 2019-11-18 08:37:21 UTC

Upstream bug assigned to ymakias

Comment 5 Bryan Kearney 2019-11-18 13:01:20 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28280 has been resolved.

Comment 6 Lukáš Hellebrandt 2019-12-13 13:49:44 UTC

Verified with Sat 6.7 snap 4, RHEL7 up-to-date as of 2019-12-13. Tried to add RHEV that uses SSL cert signed by CA unknown to Satellite. Got (correct) message "The remote system presented a public key signed by an unidentified certificate authority. If you are sure the remote system is authentic, go to the compute resource edit page, press the 'Test Connection' or 'Load Datacenters' button and submit".

Comment 9 errata-xmlrpc 2020-04-14 13:27:10 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://access.redhat.com/errata/RHSA-2020:1454