Project

General

Profile

Actions
Copy link

Bug #26737

closed

var/tmp/mongodb_engine_upgrade is not removed after successful MongoDB storage engine upgrade

Added by Chris Roberts over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Chris Roberts
Category:
foreman-installer script
Target version:
-
Difficulty:
trivial
Triaged:
Yes
Bugzilla link:
1704803
Pull request:
https://github.com/theforeman/foreman-installer/pull/350
Fixed in Releases:
Foreman - 1.23.0
Found in Releases:
Foreman - 1.22.0
Red Hat JIRA:

Description

Cloned from BZ:

Description of problem:
Satellite 6.5 allows to move existing MongoDB installs from MMAPv1 to wiredTiger. To do so, the installer has a --upgrade-mongo-storage-engine flag, which will dump the existing MMAPv1 DB, re-configure MongoDB to use wireTiger and re-import the dump.

To do so, it will create a dump at /var/tmp/mongodb_engine_upgrade, but it does not remove the dump after the installer completed.

It also creates a backup (like the on-disk data), and that IS removed on success.

Version-Release number of selected component (if applicable):
6.5.0 Snap 26

How reproducible:
100%

Steps to Reproduce:
1. Install Satellite 6.3 (the last that defaulted to MMAPv1)
2. Upgrade to 6.4, 6.5
3. Upgrade storage engine with --upgrade-mongo-storage-engine

Actual results:
/var/tmp/mongodb_engine_upgrade is present after successful upgrade

Expected results:
/var/tmp/mongodb_engine_upgrade absent

Actions
Copy link

Also available in: Atom PDF