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 2182028

Summary:	Foreman-maintain health check should be run before configuring Custom SSL certs.
Product:	Red Hat Satellite	Reporter:	Vedashree Deshpande <vdeshpan>
Component:	Satellite Maintain	Assignee:	Vedashree Deshpande <vdeshpan>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.10.0	CC:	agadhave, ehelms, ekohlvan, mjivraja
Target Milestone:	Unspecified	Keywords:	Documentation, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:11:41 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 Vedashree Deshpande 2023-03-27 10:43:05 UTC

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/installing_satellite_server_from_a_connected_network/performing-additional-configuration#configuring-satellite-custom-server-certificate_satellite

same for 6.11 and 6.12

Section Number and Name: 
In section 4.12

Describe the issue: 
Overall health check should be run to ensure hostname and other services etc are all in place before replacing the custom SSL certificates. 

Suggestions for improvement: 
Add a note to run #foreman-maintain health check before renewal of custom SSL certs. 

for 6.11 and 6.12 respectively. 

Additional information: 
If the hostname is not changed and is not uniform across all config files, installer fails and the only option is to rebuild from Scratch.

Comment 2 Ewoud Kohl van Wijngaarden 2023-03-30 15:19:12 UTC

(In reply to Vedashree Deshpande from comment #0)
> Overall health check should be run to ensure hostname and other services etc
> are all in place before replacing the custom SSL certificates. 

This is not something we'll do, because the health check may fail due to expired certificates. The procedure to replace custom SSL certificates is then supposed to resolve that situation.

Since foreman-installer 2.3.0 (IIRC that was Satellite 6.9) we do verify the certificates, regardless of which options were passed so they should always be checked.
 
> Additional information: 
> If the hostname is not changed and is not uniform across all config files,
> installer fails and the only option is to rebuild from Scratch.

I don't understand this. Why is this? It should never be needed to rebuild from scratch because of incorrect configs: the installer is supposed to always write out the desired config, regardless of the current system state.

I was going to close this as WONTFIX, but I'd first like to understand what made you think a rebuild from Scratch would be needed.

Comment 4 Eric Helms 2024-06-06 16:11:41 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 5 Red Hat Bugzilla 2024-10-05 04:25:56 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days