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.
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.
(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?