Bug #25491
CA cert can't be specified in API while adding a RHEV Compute Resource
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
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
Associated revisions
History
#1
Updated by Lukas Zapletal over 4 years ago
Updated by - Triaged changed from No to Yes
#2
Updated by The Foreman Bot over 4 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6318 added
#3
Updated by Shira Maximov over 4 years ago
Updated by - Assignee changed from Ido Kanner to Shira Maximov
#4
Updated by Tomer Brisker over 4 years ago
Updated by - Fixed in Releases 1.21.0 added
#5
Updated by Shira Maximov over 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset 3bc4e923513f1330890fdb11976ebb55483aac8e.
#6
Updated by Anonymous almost 4 years ago
- Has duplicate Bug #24391: CA cert can't be specified in API while adding a RHEV Compute Resource added
Fixes #25491 - Add public key option in POST compute resource API