Actions
Bug #25491
closed
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
Updated by
Updated by The Foreman Bot about 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6318 added
Updated by Shira Maximov about 6 years ago
- Assignee changed from Ido Kanner to Shira Maximov
Updated by
Updated by Shira Maximov about 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset 3bc4e923513f1330890fdb11976ebb55483aac8e.
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