Bug 2278827

Summary:	Documentation doesn't mention the requirement of "high-bandwidth, low-latency storage" for PostgreSQL directory
Product:	Red Hat Satellite	Reporter:	Pablo Mendez Hernandez <pmendezh>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	6.15.0	CC:	agadhave, jkastnin
Target Milestone:	Unspecified	Keywords:	Documentation, MigratedToJIRA, Performance, 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:		Environment:
Last Closed:	2024-06-06 17:36:38 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 Pablo Mendez Hernandez 2024-05-03 09:05:24 UTC

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.15/html/installing_satellite_server_in_a_connected_network_environment/preparing_your_environment_for_installation_satellite#storage-guidelines_satellite


Section Number and Name: 

1.3. Storage guidelines


Describe the issue:

Since the removal of MongoDB in 6.10 the guide only recommends the use of "high-bandwidth, low-latency storage for the /var/lib/pulp/ directories" (that plural is a bug) but with no mention of the PostgreSQL directories (/var/lib/pgsql for the recent releases) that have replaced the role as the main DB in the system.


Suggestions for improvement:

Add the relevant PosgreSQL directory (different among different releases) to the paragraph.


Additional information: 

Needed by the Performance & Scale team in order to state the importance of the disk backend performance that hosts those directories.

Comment 2 Eric Helms 2024-06-06 17:36:38 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:45 UTC

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