Bug 2059395

Summary: hammer content-[import,export] uses /tmp directory for temporary decompression location
Product: Red Hat Satellite Reporter: Brad Buckingham <bbuckingham>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lai <ltran>
Severity: high Docs Contact:
Priority: medium    
Version: 6.10.1CC: ahumbe, ggainey, janarula, jjansky, jpasqual, msunil, paji, pratshar, saydas, wpinheir, zhunting
Target Milestone: 6.10.4Keywords: PrioBumpGSS, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: pulpcore-3.14.13-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2030715 Environment:
Last Closed: 2022-03-29 14:48:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 4 Lai 2022-03-23 16:30:07 UTC
Steps to reproduce

1. Change settings for rhel and custom repos to use "Immediate" download policy
2. enable a few rhel repos (ansible + collections)
3. Sync repos
4. Create custom repos
5. sync custom repos
6. create cv and add rhel and custom repos
7. publish cv
8. check /var/lib/pulp/tmp and get the size of the folder (du -sh <folder>)
9. check /var/tmp and get the size of the folder
10. export cv or library
11. check 8,9 for any changes

expected:
/tmp dir on both /var/lib/pulp/tmp and /var/tmp should not have change

actual: 
/tmp dir on both /var/lib/pulp/tmp and /var/tmp should not have change

Each tmp dir has 4k of space and after export, they still have 4k or export.  I also repeated the test case by adding a bunch of files to /var/tmp to fill up the space and ran export again.  After export, the /var/tmp folder is still the same.  Export also passed.

Verified on 6.10.4 snap 3 with python3-pulpcore-3.14.14-1.el7pc.noarch

Comment 9 errata-xmlrpc 2022-03-29 14:48:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.10.4 Async Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1116