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.
Description of problem:
If you add a RHEVM4 self-hosted engine as a compute resource to Satellite 6 then you get error message:
<p>The requested URL /ca.crt was not found on this server.</p>
In RHEV4 ca.crt is accessible by different URL now:
https://rhevm-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA
Workaround:
on RHEVM:
openssl x509 -in /etc/pki/ovirt-engine/ca.pem -out /var/www/html/ca.crt
Version-Release number of selected component (if applicable):
Satellite 6.2.2
RHEV 4.0.4
How reproducible:
100%
Steps to Reproduce:
1. Add a new RHEV compute resource
2. Put URL of your self hosted RHEV4 manager (https://rhevm-fqdn/ovirt-engine/api/v3)
3. Specify username and password
4. Press "Load datacenters"
Actual results:
Error message "Failed to create X509 certificate, error: nested asn1 error"
and X509 Certification authorities field contains:
<!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:
Loaded list of datacenters, obtained X509 certificate
Additional info: