Bug 2130173 - Configure Cloud Connector runs against an old hostname after a hostname change
Summary: Configure Cloud Connector runs against an old hostname after a hostname change
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: satellite-change-hostname
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.14.0
Assignee: Patrick Creech
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-27 12:10 UTC by Jameer Pathan
Modified: 2023-06-30 18:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-13193 0 None None None 2022-09-29 14:20:03 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.