Bug 2039114

Summary:	neither documentation nor migration-stats tell customers that /var/lib/pulp/media may grow to large sizes during the migration
Product:	Red Hat Satellite	Reporter:	Jessica Hanley <jhanley>
Component:	Documentation	Assignee:	Marie Hornickova <mdolezel>
Documentation sub component:	default	QA Contact:
Status:	NEW ---	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	bangelic, jrichards2, kkeane, mdolezel, pdwyer
Version:	6.9.7
Target Milestone:	Unspecified
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:		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 Jessica Hanley 2022-01-11 02:15:43 UTC

Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#Upgrading_Server_upgrade-guide

Section Number and Name: 

3.1. Upgrading Satellite Server
Before You Begin


Describe the issue: 

The documentation warns customers that /var/lib/pulp/published/ may double in size during the migration, but it doesn't tell customers that docker images will be moved to /var/lib/pulp/media, that this directory could become large, or how to predict the eventual size of that directory.  This isn't mentioned by the output of the command "satellite-maintain content migration-stats" either.

This issue affects customers who have mounted volumes at /var/lib/pulp/published rather than at /var/lib/pulp, because in this case /var/lib/pulp/media will spill over into the /var volume.


Suggestions for improvement: 

- mention that docker images will be moved to /var/lib/pulp/media
- give customers a command to evaluate how much storage their docker images take up on disk prior to the migration

Comment 1 kkeane 2022-01-11 03:08:11 UTC

Additional information:

There appears to be some confusion between /var/lib/pulp/published (a relatively small directory at 36 GB for me) and /var/lib/pulp/content (a very large directory with 1.4 TB for me).

It is actually /var/lib/pulp/content that doubles in size. Correspondingly, the spillover problem mentioned in the bug report applies to customers who have mounted volumes on /var/lib/pulp/content.

Also, this does not affect just docker images, but primarily RPM content.

Comment 2 Marie Hornickova 2022-01-11 11:42:11 UTC

Hello Jessica,
Thank you very much for filing this BZ against docs.
I see some customer cases are attached, so I've increased the severity to "medium".
The BZ is currently assigned, and we'll prioritize it in our sprints according to our workloads and free capacity.
Thank you!

Comment 5 Jessica Richards 2022-01-11 18:02:56 UTC

(In reply to kkeane from comment #1)
> Additional information:
> 
> There appears to be some confusion between /var/lib/pulp/published (a
> relatively small directory at 36 GB for me) and /var/lib/pulp/content (a
> very large directory with 1.4 TB for me).
> 
> It is actually /var/lib/pulp/content that doubles in size. Correspondingly,
> the spillover problem mentioned in the bug report applies to customers who
> have mounted volumes on /var/lib/pulp/content.
> 
> Also, this does not affect just docker images, but primarily RPM content.

Marie,

Thank you for the clarification, I appreciate it!

--
Jessica

Comment 7 Brad Buckingham 2023-07-21 21:06:39 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.