Description of problem: When running satellite-installer --upgrade-mongo-storage-engine, it will first dump the MongoDB database and then restore it with the new storage engine. While restoring, it runs mongorestore --host localhost --db=pulp_database --drop --quiet --dir=/var/tmp/mongodb_engine_upgrade/pulp_database And with --quiet there is zero output on the terminal. (There is during the dump phase). As this step can easily take multiple hours, it'd be nice to see some progress, even if it's as badly formatted as the one during the dump Version-Release number of selected component (if applicable): 6.5.0 Snap 26 How reproducible: 100% Steps to Reproduce: 1. Install 6.3 (last one to default to MMAPv1 for new installs) 2. Upgrade to 6.4/6.5 3. satellite-installer --upgrade-mongo-storage-engine Actual results: No output during restore Expected results: Output during restore Additional info: Just removing the --quiet should be sufficient
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26746 has been resolved.
Verified this issue on 6.6 with the latest snap. Verified point: * satellite version: satellite-6.6.0-6.el7sat.noarch * foreman-installer version: foreman-installer-1.22.0.10-1.el7sat.noarch * Mongodb upgrade completed successfully on 6.6 upgraded setup(6.3-->6.4-->6.5-->6.6) #satellite-installer --upgrade-mongo-storage-engine Starting disk space check for upgrade Package versions are locked. Continuing with unlock. .... ..... mongorestore --host localhost --db=pulp_database --drop --dir=/var/tmp/mongodb_engine_upgrade/pulp_database finished successfully! ... ... Installing Done [100%] [................................................................................................................................] Package versions are being locked. Success! * File /var/tmp/mongodb_engine_upgrade did not exist after mongodb upgrade. * There is no "quite" option in "mongorestore --host localhost --db=pulp_database --drop --dir=/var/tmp/mongodb_engine_upgrade/pulp_database" * Now we can see proper progress.
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-2019:3172