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 1426391 - Satellite 6.2 is unable to download CA certificate from RHEV 4.0
Summary: Satellite 6.2 is unable to download CA certificate from RHEV 4.0
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 1370169
Blocks: 1375606
TreeView+ depends on / blocked
 
Reported: 2017-02-23 20:37 UTC by Satellite Program
Modified: 2023-09-14 03:54 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1370169
Environment:
Last Closed: 2017-03-01 07:19:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15163 0 None None None 2017-02-23 20:37:50 UTC

Comment 2 Satellite Program 2017-02-28 21:14:34 UTC 
Upstream bug assigned to lzap
Comment 3 Satellite Program 2017-02-28 21:14:42 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15163 has been resolved.
Comment 4 Steven Mercurio 2017-02-28 23:48:49 UTC 
Is there a 6.2.6 patch I can get or an RPM I can test and report back on?
Comment 5 Lukas Zapletal 2017-03-01 07:19:42 UTC 
Steven,

this bug is for Satellite 6.3, we have another clone of this bug for Satellite 6.2:

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

You will see there it is scheduled to be released as part of 6.2.9 errata which is pretty close. If you can't wait, you can patch your instance manually:

https://github.com/theforeman/foreman/pull/3548/files

but we won't release hotfix for this bug, it's easy workaround (just download the certificate with CURL and paste it into the X509 cert Compute Resource field in Satellite form).

Bryan, I think we can close this bug as UPSTREAM, doing it.

***

I am closing this bug, it was fixed upstream and will be part of the 6.3 version.
Comment 7 Tom Gamull 2017-03-01 13:50:36 UTC 
(In reply to Lukas Zapletal from comment #5)
> Steven,
> 
> this bug is for Satellite 6.3, we have another clone of this bug for
> Satellite 6.2:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1370169
> 
> You will see there it is scheduled to be released as part of 6.2.9 errata
> which is pretty close. If you can't wait, you can patch your instance
> manually:
> 
> https://github.com/theforeman/foreman/pull/3548/files
> 
> but we won't release hotfix for this bug, it's easy workaround (just
> download the certificate with CURL and paste it into the X509 cert Compute
> Resource field in Satellite form).
> 
> Bryan, I think we can close this bug as UPSTREAM, doing it.
> 
> ***
> 
> I am closing this bug, it was fixed upstream and will be part of the 6.3
> version.

Can we update the documentation at least or is https://bugzilla.redhat.com/show_bug.cgi?id=1370169 handling the issue?
Comment 8 Lukas Zapletal 2017-03-01 15:34:45 UTC 
The other bug handles this, there is no 6.3 yet so this bug was only for QA purposes. Might get reopened, but you want the other one likely.
Comment 10 Red Hat Bugzilla 2023-09-14 03:54:15 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.