Project

General

Profile

Bug #25491

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

Added by Shira Maximov 4 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Team Backlog:
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

Associated revisions

Revision 3bc4e923 (diff)
Added by Shira Maximov 3 months ago

Fixes #25491 - Add public key option in POST compute resource API

History

#1 Updated by Lukas Zapletal 4 months ago

  • Triaged changed from No to Yes

#2 Updated by The Foreman Bot 3 months ago

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

#3 Updated by Shira Maximov 3 months ago

  • Assignee changed from Ido Kanner to Shira Maximov

#4 Updated by Tomer Brisker 3 months ago

  • Fixed in Releases 1.21.0 added

#5 Updated by Shira Maximov 3 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF