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:
Configure cloud connector playbook tries to retrieve a private key from manifest/organization by talking to katello/api/v2/organizations/:org_id. However this was removed in BZ1828549. We need to figure out an alternative way of obtaining the private key, otherwise the playbook will fail to configure the cloud connector.
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1828549
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Run cloud connector on 6.8 (or anything that has katello >=3.6.0)
Actual results:
It fails to obtain the private key, cloud connector is not configured for the organization.
Expected results:
Private key is obtained, cloud connector is configured and can open connection to the cloud.
Additional info:
Comment 1Lukáš Hellebrandt
2020-06-03 13:36:49 UTC
Created attachment 1694830[details]
receptor_install_job.log
Adding a log of job invocation showing how this manifests.
Comment 2Lukáš Hellebrandt
2020-07-09 15:00:22 UTC
Verified with Sat 6.8 snap 8.0. Installed Receptor successfully using the job template.
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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366