Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
While upgrading mongo-storage-engine there should be sanity check.

Version-Release number of selected component (if applicable):
Upgrading from Satellite 6.4 to 6.5


How reproducible:
There is no sanity check option to pre-check the things before upgradation of mongo-storage-engine.

satellite-installer --upgrade-mongo-storage-engine


Actual results:
It will directly start to upgrade the mongo-storage-engine.
It should give option to do sanity check.



Additional info:
As there is no sanity check options many time the upgrade-mongo-storage-engine is getting failed because of disk space issue or any other issue.

Closing as a dupe of 1715898 since there are checks but one to make sure the disk space is good needs an update.

*** This bug has been marked as a duplicate of bug 1715898 ***