Bug 1519389 - Foreman-debug must avoid using tmpfs and clean on error
Summary: Foreman-debug must avoid using tmpfs and clean on error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Debug
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Renzo Nuccitelli
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1533259
TreeView+ depends on / blocked
 
Reported: 2017-11-30 16:37 UTC by Lukas Zapletal
Modified: 2019-04-01 20:27 UTC (History)
4 users (show)

Fixed In Version: foreman-1.15.6.34-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21824 0 None None None 2017-11-30 17:03:36 UTC
Foreman Issue Tracker 22376 0 None None None 2018-01-26 13:04:59 UTC
Foreman Issue Tracker 22426 0 None None None 2018-01-26 12:59:09 UTC

Description Lukas Zapletal 2017-11-30 16:37:00 UTC 
With increased limits, tarballs are now bigger which can lead into two issues:

1) Directory /tmp can run of space, it is on tmpfs, we need to use /var/tmp

2) When there is a fatal error, there is no cleanup hook in the shell script, collected data are left.

Running out of space in /tmp can be fatal, we need this in 6.3 GA.
Comment 5 Lukas Zapletal 2018-01-25 15:36:29 UTC 
The upstream patch is now ready to be merged. Awaiting test pass.
Comment 6 Ivan Necas 2018-01-26 12:59:09 UTC 
Adding additional issue that was discovered as part of the testing of the PR
Comment 7 Ivan Necas 2018-01-26 13:05:00 UTC 
Adding the katello part of the issue
Comment 9 Renzo Nuccitelli 2018-01-31 20:21:00 UTC 
Tar saved on /tmp/var on Satellite 6.3 snap 34.
Comment 10 Satellite Program 2018-02-21 16:54:17 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, 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/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.