Bug 2055338 - 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 9
Classification: Red Hat
Component: rear
Version: 9.0
Hardware: All
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
Depends On:
Blocks: 2055340
TreeView+ depends on / blocked
 
Reported: 2022-02-16 18:01 UTC by Pavel Cahyna
Modified: 2022-05-17 14:18 UTC (History)
2 users (show)

Fixed In Version: rear-2.6-11.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2055340 (view as bug list)
Environment:
Last Closed: 2022-05-17 14:17:50 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 [Bug] Osp16 keystone healtcheck fails 2022-04-20 14:26:29 UTC
Github rear rear pull 2675 0 None Merged Use double quotes for remove_temporary_mountpoint "$BUILD_DIR/..." 2022-02-16 18:01:10 UTC
Red Hat Issue Tracker RHELPLAN-112642 0 None None None 2022-02-16 18:06:22 UTC
Red Hat Product Errata RHBA-2022:2691 0 None None None 2022-05-17 14:17:57 UTC

Description Pavel Cahyna 2022-02-16 18:01:10 UTC
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.6-10.el9

How reproducible:
very easy

Steps to Reproduce:
1. rear mkrescue
2. ls /var/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 8 errata-xmlrpc 2022-05-17 14:17:50 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 (new packages: rear), 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:2691


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