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 2130173

Summary:	Configure Cloud Connector runs against an old hostname after a hostname change
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	satellite-change-hostname	Assignee:	Patrick Creech <pcreech>
Status:	CLOSED ERRATA	QA Contact:	Jameer Pathan <jpathan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.12.0	CC:	egolov, ehelms, osousa, pcreech
Target Milestone:	6.14.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2246591 (view as bug list)		Environment:
Last Closed:	2023-11-08 14:18:02 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:

Description Jameer Pathan 2022-09-27 12:10:25 UTC

Description of problem:
Configure Cloud Connector runs against an old hostname after a hostname change

Version-Release number of selected component (if applicable):
- Satellite 6.12.0 snap 11

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a Satellite prepared to get cloud connecor configured (e.g. ssh keys copied, s-m registered, manifest uploaded etc.)
2. Run satellite-change-hostname
3. Attempt Configure -> Inventory Upload -> Configure Cloud connector

Actual results:
Failure, job run against an old hostname

Expected results:
Job run against a new hostname

Additional info:
- Fix https://github.com/theforeman/foreman-packaging/commit/e76bc4d43aa1f6dfbca8feb5799573a1fa36c8b4 is missing in 6.12.
- See also BZ#2094255 and BZ#2042480

Comment 1 Brad Buckingham 2022-09-28 21:30:03 UTC

Hi Evgeni,

Are you able to confirm that inclusion of the referenced commit resolves the issue raised?

Thanks!

Comment 2 Evgeni Golov 2022-09-29 06:13:15 UTC

(In reply to Brad Buckingham from comment #1)

> Are you able to confirm that inclusion of the referenced commit resolves the
> issue raised?

I can confirm that the commit referenced is missing from 6.12 and that w/o it it's not worth of a further investigation.
I did not spin up a 6.12 to verify the commit does actually fix it, but am rather confident that it won't work without it.

Comment 5 Jameer Pathan 2022-10-10 13:11:22 UTC

FailedQA: Satellite 6.12.0 snap 14 still doesn't contain the necessary fix.

Comment 9 Jameer Pathan 2023-08-31 12:17:23 UTC

Verified

Verified with:
- satellite 6.14.0 snap 13
- rubygem-foreman_rh_cloud-8.0.48-1.el8sat.noarch

test steps:
1. Run satellite-change-hostname
2. Attempt Configure -> Inventory Upload -> Configure Cloud connector


Additional info:
tried the steps mentioned in BZ#2094255#c2 
[root@satellite ~]# foreman-rake console
Loading production environment (Rails 6.1.7.3)
irb(main):001:0> ForemanRhCloud.foreman_host_name
=> "new.satellite.fqdn.com"
irb(main):002:0> ::Host.unscoped.search_for('infrastructure_facet.foreman = true').length
=> 1

There's still an old hostname entry present on all host page, but as per Evgeni it's expected. See BZ#2224019

Comment 12 errata-xmlrpc 2023-11-08 14:18:02 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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818