Bug 2055340 - rear mkrescue run leaves behind a temporary directory
Summary: rear mkrescue run leaves behind a temporary directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rear
Version: 8.5
Hardware: All
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
Depends On: 2055338
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-16 18:05 UTC by Pavel Cahyna
Modified: 2022-05-10 14:55 UTC (History)
4 users (show)

Fixed In Version: rear-2.6-4.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 2055338
Environment:
Last Closed: 2022-05-10 14:34:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear issues 2667 0 None closed 'rear recover' does not entirely remove build area (any more). 2022-02-16 18:10:12 UTC
Github rear rear pull 2675 0 None Merged Use double quotes for remove_temporary_mountpoint "$BUILD_DIR/..." 2022-02-16 18:05:10 UTC
Red Hat Issue Tracker RHELPLAN-112643 0 None None None 2022-02-16 18:06:39 UTC
Red Hat Product Errata RHBA-2022:1966 0 None None None 2022-05-10 14:34:25 UTC

Description Pavel Cahyna 2022-02-16 18:05:10 UTC
+++ This bug was initially created as a clone of Bug #2055338 +++

Description of problem:
After rear mkrescue (and some other commands) finishes, there is a leftover directory in TMPDIR (/tmp or /var/tmp). This is due to a mistake in one backported patch (PR2625), corrected in upstream PR2675.

Version-Release number of selected component (if applicable):
2.4-19.el8

How reproducible:
very easy

Steps to Reproduce:
1. rear mkrescue
2. ls /tmp

Actual results:
there is a directory like rear.<random string>

Expected results:
no rear temporary directory after rear execution

Additional info:
In debug mode, rear preserves the directory for investigation - do not use any debug flags for reproducing this.

Comment 7 errata-xmlrpc 2022-05-10 14:34:16 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 (rear bug fix and enhancement 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:1966


Note You need to log in before you can comment on or make changes to this bug.