Bug 1602835

Summary:	CA cert can't be specified in API while adding a RHEV Compute Resource
Product:	Red Hat Satellite	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	Compute Resources - RHEV	Assignee:	Shira Maximov <mshira>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	egolov, inecas, mshira, orabin, sjagtap
Target Milestone:	6.6.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-1.21.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 19:50:24 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 Lukáš Hellebrandt 2018-07-18 15:18:31 UTC

Description of problem:
In WebUI, it is possible (sometimes necessary) to specify a CA certificate for https communication with RHEV. This is done using the "X509 Certification Authorities" field in the new Compute Resource creation form.

In API, this is not possible. Consequently, it is also not possible in Hammer, Nailgun and other tools using API.

Steps to Reproduce:
http://SAT_HOSTNAME/apidoc/v2/compute_resources/create.html

Actual results:
No parameter for CA cert

Expected results:
public_key (id of the WebUI input field) parameter

Comment 2 Ido Kanner 2018-07-25 13:25:49 UTC

*** Bug 1607793 has been marked as a duplicate of this bug. ***

Comment 3 Ivan Necas 2018-07-30 13:59:50 UTC

*** Bug 1607799 has been marked as a duplicate of this bug. ***

Comment 4 Shira Maximov 2018-11-18 11:52:31 UTC

Created redmine issue https://projects.theforeman.org/issues/25491 from this bug

Comment 5 Satellite Program 2018-12-10 09:10:45 UTC

Upstream bug assigned to ikanner

Comment 7 Satellite Program 2018-12-12 11:10:44 UTC

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

Comment 9 Lukáš Hellebrandt 2019-07-16 15:18:08 UTC

Verified with Sat 6.6 snap 11.

API now contains parameter public_key.
CLI now contains parameters public-key and public-key-path.

Comment 10 Bryan Kearney 2019-10-22 19:50:24 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-2019:3172