Project

General

Profile

Actions

Bug #25491

closed

CA cert can't be specified in API while adding a RHEV Compute Resource

Added by Shira Maximov almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1602835

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


Related issues 1 (0 open1 closed)

Has duplicate Foreman - Bug #24391: CA cert can't be specified in API while adding a RHEV Compute ResourceDuplicateIdo KannerActions
Actions #1

Updated by Lukas Zapletal almost 6 years ago

  • Triaged changed from No to Yes
Actions #2

Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6318 added
Actions #3

Updated by Shira Maximov almost 6 years ago

  • Assignee changed from Ido Kanner to Shira Maximov
Actions #4

Updated by Tomer Brisker almost 6 years ago

  • Fixed in Releases 1.21.0 added
Actions #5

Updated by Shira Maximov almost 6 years ago

  • Status changed from Ready For Testing to Closed
Actions #6

Updated by Anonymous over 5 years ago

  • Has duplicate Bug #24391: CA cert can't be specified in API while adding a RHEV Compute Resource added
Actions

Also available in: Atom PDF