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.

Postgres db on the capsule can be more than double in size that in the Satellite server

Please refer to the last 10 comments from BZ https://bugzilla.redhat.com/show_bug.cgi?id=2089936 

The request is applicable for 6.10 - 6.14 

Satellite and Capsule 6.10+ uses postgresql as the main database server

Even though satellite has three databases in postgres whereas capsule has just one, Capsules postgres DB and the size of /var/lib/pgsql can easily get doubled or even tripped in size when the amount of Lifecycles\CVs\Repos would increase for the capsule to sync . 

We need to record this behavior in the Storage Guidelines section perhaps, as an expected behavior. 

Please consult with Katello or Pulp SMEs involved in the other BZ for an appropriate statement around this behavior. 

Reported by: rhn-support-saydas

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/installing_capsule_server/preparing-environment-for-capsule-installation#annotations:0ce73985-8df6-43e7-a9ae-1f9a7f7c412b

PR submitted: https://github.com/theforeman/foreman-documentation/pull/2546

Comment#0 requests fixing this in version 6.10 as well, which means I will need to submit another PR downstream after this one is merged.

(In reply to Aneta Šteflová Petrová from comment #2)
> PR submitted: https://github.com/theforeman/foreman-documentation/pull/2546

PR merged: https://github.com/theforeman/foreman-documentation/pull/2546#issuecomment-1778653041

Another one will be required for 6.12 and 6.11 due to a merge conflict.
 
> Comment#0 requests fixing this in version 6.10 as well, which means I will
> need to submit another PR downstream after this one is merged.

6.10 is actually no longer supported so the fix will not be applied to 6.10.

PR to get the fix into versions 6.12 and 6.11: https://github.com/theforeman/foreman-documentation/pull/2554

(In reply to Aneta Šteflová Petrová from comment #4)
> PR to get the fix into versions 6.12 and 6.11:
> https://github.com/theforeman/foreman-documentation/pull/2554

PR merged: https://github.com/theforeman/foreman-documentation/pull/2554#issuecomment-1779449859

But another one was required for 6.11: https://github.com/theforeman/foreman-documentation/pull/2556
This should be the last one.

Published: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/installing_capsule_server/index#capsule-storage-requirements_capsule

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