Bug 1388749 - Can't add RHEVM4 self-hosted engine as a compute resource
Summary: Can't add RHEVM4 self-hosted engine as a compute resource
Keywords:
Status: CLOSED DUPLICATE of bug 1370169
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
high
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 05:28 UTC by Alexey Masolov
Modified: 2017-01-10 09:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-21 11:27:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Alexey Masolov 2016-10-26 05:28:41 UTC
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:


Note You need to log in before you can comment on or make changes to this bug.