Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1593253

Summary: installer missing --upgrade-mongo-storage option
Product: Red Hat Satellite Reporter: Ales Dujicek <adujicek>
Component: InstallationAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: chrobert, cwelton, ehelms, ekohlvan, inecas, ktordeur, mbacovsk, mmccune, pcreech, rjerrido, sghai
Target Milestone: 6.5.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: https://projects.theforeman.org/issues/25634
Whiteboard:
Fixed In Version: katello-installer-base-3.10.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:37:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ales Dujicek 2018-06-20 11:45:12 UTC
Description of problem:

during upgrade from 6.3 to 6.4 I am asked to run satellite-installer --upgrade-mongo-storage

/var/log/foreman-installer/satellite.log
[ INFO 2018-06-20T04:47:27 main] Upgrade Step: mongo_mmapv1_check...
[DEBUG 2018-06-20T04:47:28 main] systemctl stop mongod finished successfully!
[ INFO 2018-06-20T04:47:28 main] Detecting Pulp database and no wiredTiger files, keeping storage engine as MMAPv1
[ INFO 2018-06-20T04:47:28 main] To upgrade to wiredTiger at a later time run foreman-installer with the --upgrade-mongo-storage flag.
[ INFO 2018-06-20T04:47:28 main] Upgrade Step: Running installer...

https://github.com/Katello/katello-installer/blob/00105a73b6da68d6051ed8a62e380b263f2bc6ec/hooks/pre/30-upgrade.rb#L63

but:
# satellite-installer --upgrade-mongo-storage
ERROR: Unrecognised option '--upgrade-mongo-storage'

See: 'satellite-installer --help'


Version-Release number of selected component (if applicable):
foreman-installer-katello-3.7.0-1.rc1.el7sat.noarch
satellite-installer-6.4.0.5-1.beta.el7sat.noarch
foreman-installer-1.18.0-0.1.RC1.el7sat.noarch
katello-installer-base-3.7.0-1.rc1.el7sat.noarch


How reproducible:
always

Comment 2 Satellite Program 2018-06-20 22:27:26 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23030 has been resolved.

Comment 3 Satellite Program 2018-07-11 12:26:34 UTC
Upstream bug assigned to chrobert

Comment 4 Satellite Program 2018-07-11 12:26:37 UTC
Upstream bug assigned to chrobert

Comment 12 Ewoud Kohl van Wijngaarden 2019-04-30 14:45:39 UTC
Related: https://bugzilla.redhat.com/show_bug.cgi?id=1704806 is about the inconsistent naming in the option.

Comment 15 errata-xmlrpc 2019-05-14 12:37:27 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, 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:1222