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.

Bug 1393928

Summary: Support for RHEV 4.0 in Satellite 6.2 is missing certificate download
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: Compute Resources - RHEVAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Sanket Jagtap <sjagtap>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.3CC: bbuckingham, bkearney, ehelms, inecas, jcallaha, sjagtap, smercurio, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/15560
Whiteboard:
Fixed In Version: tfm-rubygem-rbovirt-0.0.38-1,foreman-1.11.0.65-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1405489 1417132 (view as bug list) Environment:
Last Closed: 2017-03-06 08:34:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1405489, 1417132    

Description Lukas Zapletal 2016-11-10 16:16:15 UTC 
Due to change in API in RHEV, we need updated version of rbovirt 0.38 or higher.

http://projects.theforeman.org/issues/15560
Comment 1 Lukas Zapletal 2016-11-10 16:17:52 UTC 
Note this patch will only work on RHEV 4.0.1 or higher:

https://bugzilla.redhat.com/show_bug.cgi?id=1346752

WORKAROUND HOTFIX for 6.2: 

http://people.redhat.com/~lzapleta/hotfix/rhev-4.0-sat-6.2-1393928/
Comment 3 Lukas Zapletal 2016-11-10 16:20:00 UTC 
Alternative WORKAROUND:

Change the URL in foreman to <engine-host>/ovirt-engine/api/v3
Comment 4 Bryan Kearney 2016-11-10 19:03:59 UTC 
Upstream bug component is Compute Resources - RHEV
Comment 5 Bryan Kearney 2016-11-10 19:04:02 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15560 has been resolved.
Comment 6 Lukas Zapletal 2017-01-10 12:12:42 UTC 
Ok the support for RHEV 4.0 in Satellite 6.2 is missing the certificate download patch, we need to backport it (small patch):

https://bugzilla.redhat.com/show_bug.cgi?id=1370169
http://projects.theforeman.org/issues/15163

The patch will enable RHEV certificate downloading only for versions 3.4 - 4.0+ and for older releases users will have to paste it manually.

Therefore this is FailedQA. However, this is an easy workaround, download the server CRT certificate from RHEV and paste the contents into the X509 certificate and then continue testing RHEV 4.0 for Satellite 6.2.
Comment 8 Steven Mercurio 2017-01-19 08:55:14 UTC 
I have 6.2.6 now.  Is there an ETA for 6.2.7?  Is there test code I can get and try (and provide feedback on) that will not hamper my ability to update past 6.2.6?
Comment 9 Lukas Zapletal 2017-01-19 09:32:38 UTC 
Steven, does the workaround from comment 3 work for you? Also make sure you have the correct X509 certificate in Satellite Compute Resource and you should be good to go.
Comment 12 Lukas Zapletal 2017-02-14 16:54:23 UTC 
Thanks, please mark this one as verified and we will look into the other two.
Comment 14 errata-xmlrpc 2017-03-06 08:34:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0447