Bug 2271177

Summary:	Documentation Discrepancy: Inconsistency in Private Key Filename
Product:	Red Hat Satellite	Reporter:	Ganesh Payelkar <gpayelka>
Component:	Security	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.14.3	CC:	agadhave, ehelms, mhulan
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 17:26:50 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 Ganesh Payelkar 2024-03-23 11:15:41 UTC

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/administering_red_hat_satellite/renewing-the-custom-ssl-certificate_admin#Renewing_a_Custom_SSL_Certificate_on_satellite_admin

Section Number and Name: 

15.1. Renewing a Custom SSL Certificate on Satellite Server


Describe the issue: 

Upon reviewing the instructions provided, I found an inconsistency regarding the filename of the private key required for deploying renewed CA certificates to the Satellite Server.

In the section detailing the `katello-certs-check` and `satellite-installer` commands, the filename for the private key is listed as "/root/satellite_cert/satellite_key.pem". 


However, upon further review, it seems that the correct filename should be "/root/satellite_cert/satellite_cert_key.pem", which matches the filename specified in the `katello-certs-check` command.

Suggestions for improvement: 

This inconsistency could potentially lead to confusion for users attempting to deploy renewed CA certificates to the Satellite Server. Therefore, I wanted to bring it to your attention for correction.

Additional information:

Comment 2 Eric Helms 2024-06-06 17:26:50 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 3 Red Hat Bugzilla 2024-10-05 04:27:29 UTC

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