Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1990472

Summary: [RFE] "# hammer content-export" command should check if sufficient disk space is available in "/var/lib/pulp/exports/" directory
Product: Red Hat Satellite Reporter: Jayant Bhatia <jbhatia>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.12.0CC: aheverle, ahumbe, dalley, dkliban, dsinglet, faguiard, ggainey, mjivraja, paji, rchan, ttereshc
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, PrioBumpGSS, Reopened, 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 01:01:51 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 Jayant Bhatia 2021-08-05 13:26:04 UTC
Description of problem:

While exporting the content in Satellite-6.10 using "# hammer content-export" command, there should be a pre-check performed which should check if "/var/lib/pulp/exports/" has sufficient space available for the export to be successful. This pre-check should be performed before export process is started and should give a warning or error beforehand instead of getting failed at the end.


Version-Release number of selected component (if applicable): Satellite-6.10


Steps to Reproduce:
1. Ensure "/var/lib/pulp/exports/" has very less disk space available.
2. Initiate a complete library synchronization using command "# hammer content-export complete library --organization-id 1".

Actual results: The export process is started and disk space check for "/var/lib/pulp/exports/" is not performed. The command later fails when "/var/lib/pulp/exports/" gets full in between the export process.


Expected results: A pre-check should be performed to ensure enough disk space is available in "/var/lib/pulp/exports/" before starting the export process after running "# hammer content-export" command.

Comment 1 pulp-infra@redhat.com 2021-08-05 15:18:07 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

Comment 2 pulp-infra@redhat.com 2021-08-05 15:18:09 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 3 Tanya Tereshchenko 2021-10-29 16:54:10 UTC
This RFE is not on the roadmap in the short term, we will re-evaluate it in a few months.

Comment 4 Brad Buckingham 2022-09-02 20:25:18 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.

Comment 5 Brad Buckingham 2022-09-05 22:55:19 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.

Comment 7 Daniel Alley 2022-10-20 20:05:03 UTC
Not sure how it got onto the maybe-close list, but it should probably stay open.

Comment 8 Brad Buckingham 2022-10-28 18:05:34 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 9 Daniel Alley 2022-10-28 18:27:53 UTC
Reopening - this seems like a valid and useful RFE

Comment 10 Brad Buckingham 2022-11-03 21:47:41 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.

Comment 12 Daniel Alley 2023-08-22 04:39:29 UTC
*** Bug 2167500 has been marked as a duplicate of this bug. ***

Comment 13 Daniel Alley 2023-08-22 04:41:23 UTC
I closed https://bugzilla.redhat.com/show_bug.cgi?id=2167500 as a duplicate of this one. Summarized:

---

[RFE] Add hammer command/option to show size of content view

Add hammer command/option to show size of content view

Why: Other than running an "ls" on the exported file, you are not able to see the size the the content view. Prior to exporting a content view, you are not able to determine the size of the content view.  It is suggested to have double the amount of free space than the size of the content view.

Comment 14 Daniel Alley 2023-08-22 04:43:26 UTC
*** Bug 2184954 has been marked as a duplicate of this bug. ***

Comment 15 Daniel Alley 2023-08-22 04:45:19 UTC
I closed  https://bugzilla.redhat.com/show_bug.cgi?id=2184954 as a duplicate also

---

[RFE] Hammer command should report the size of the export

Description of problem:  While importing the content to the Disconnected satellite, the import fails due to insufficient storage space.

How reproducible: hammer content-import version --organization=RedHat --path=/SatelliteBackup/imports/RedHat/v7_Server_x86_64/125.0/2023-01-03T10-32-07-05-00.

Actual results: [Errno 28] No space left on device (Katello::Errors::Pulp3Error)

Expected results: As mentioning the static storage size is not possible to document, we can request the hammer command to report the size of the export data to the user before the export process.

Comment 16 Eric Helms 2024-06-06 01:01:51 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.