-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
6.10.0, 6.15.0
-
False
-
-
False
-
CLOSED
-
1,800
-
Phoenix - Content
-
-
-
Sprint 141, Sprint 142
-
Important
-
No Coverage
-
None
Description of problem:
Postgres database on the capsule server is double in size as compare to the Satellite server.
Version-Release number of selected component (if applicable):
6.10
How reproducible:
Customer Environment
Steps to Reproduce:
- Install a Satellite and Capsule
- Have generic set of rhel 8 9 and 7 repos enabled and sycned on satellite
- Create a LCE path e.g. Library --> Dev --> Stage --> Test --> Prod
- Create three CVs by name RHEL8 RHEL9 RHEL7 and add respective repos in them
- Publish and promote those CVs to all the LCEs
- Sync all the LCEs to the capsule
- Satellite and Capsule upgraded from 6.9 to 6.10.
Comment #30 from the bugzilla #2089936
It seems the problem is reproducible easily now and mainly happens due to the amount of repository records created in Pulp of Capsule ( compared with satellite ) .
The number of repository records would be increasing in the capsules's pulp and easily surpass the count of the satellite's pulp when
- More than one lifecycle is synced with the capsule server ( including Library ) [ the problem starts here ]
- Each included lifecycle has a good number of CV or CCVs to sync
- Each included CV or CCV has a good number of repos added in them.
Actual results:
/var/opt/rh/rh-postgresql12/lib/pgsql/data/base is much bigger on the size on the capsule server.
Expected results:
/var/opt/rh/rh-postgresql12/lib/pgsql/data/base should be equal or less on the capsule server.
Additional info:
- external trackers