Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1375602 +++
Description of problem:
Adding compute resources from provider RHEV try to get certificate from /ca.crt. That works fine for 3.6.x but in version 4 that certificate should be generated from [1]:
/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA
It is no longer possible to obtain that certificate from /ca.crt in version 4.
[1] (from documentation or: https://www.ovirt.org/documentation/how-to/guest-console/connect-to-spice-console-without-portal/)
Version-Release number of selected component (if applicable):
RHEVM 4.0.4-2
Satellite 6.2.1 (the same issue is also in 6.1.9)
How reproducible:
Always
Steps to Reproduce:
1. Have a Satellite
2. RHEVM 4.x
3. Try to add RHEVM 4.x as resource provider
Actual results:
Error:
Unable to save
Failed to create X509 certificate, error: nested asn1 error
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /ca.crt was not found on this server.</p>
</body></html>
Expected results:
Detect rhevm version from api or manually choose it in Satellite and get certificate properly for that version.
Trying to get certificate both ways could lead unnecessary delay
It's only suggestion, it's up to you.
Closing this as a duplicate of the original clone. If it is needed, please do let us know.
*** This bug has been marked as a duplicate of bug 1375602 ***