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 2094280 - rhc_instance_id is not being set correctly by configure cloud connector playbook.
Summary: rhc_instance_id is not being set correctly by configure cloud connector playb...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Cloud Connector
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.11.0
Assignee: Evgeni Golov
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-07 10:42 UTC by Jameer Pathan
Modified: 2023-09-15 01:55 UTC (History)
6 users (show)

Fixed In Version: rubygem-foreman_rh_cloud-5.0.38-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:35:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github RedHatSatellite satellite-operations-collection pull 29 0 None open Update to 1.2.2 2022-06-09 13:39:32 UTC
Github theforeman foreman-operations-collection pull 94 0 None open use a regular expression to parse the CN from the cert 2022-06-07 10:50:05 UTC
Github theforeman foreman_rh_cloud pull 742 0 None open Move sources announcement after configuration job 2022-06-09 13:40:03 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:36:07 UTC

Description Jameer Pathan 2022-06-07 10:42:00 UTC
Description of problem:
rhc_instance_id is not being set correctly by configure cloud connector playbook.

Version-Release number of selected component (if applicable):
- Satellite 6.11.0 snap 23
- rhel 8.6

How reproducible:
- Always

Steps to Reproduce:
1. Go to Configure > Inventory upload
2. Click on "Configure Cloud Connector" button.
3. After job completes successfully, check value of "rhc_instance_id".

Actual results:
subject=O = 1334248, CN = <rhc_instance_id>

Expected results:
field should only contain the rhc_instance_id.

Additional info:

Comment 6 Jameer Pathan 2022-06-16 11:46:13 UTC
Verified:

Verified with:
- Satellite 6.11.0 snap 25
- rubygem-foreman_rh_cloud-5.0.39-1.el8sat.noarch

Test steps:
1. Go to Configure > Inventory upload
2. Click on "Configure Cloud Connector" button.
3. After job completes successfully, check value of "rhc_instance_id".

Observations:
- rhc_instance_id setting value was set correctly.

Comment 9 errata-xmlrpc 2022-07-05 14:35:58 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 (Moderate: Satellite 6.11 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-2022:5498

Comment 10 Red Hat Bugzilla 2023-09-15 01:55:37 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days


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