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 1901919 - Satellite restore fails with Unrecognised option '--reset'
Summary: Satellite restore fails with Unrecognised option '--reset'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.9.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: 6.9.0
Assignee: Amit Upadhye
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-26 12:31 UTC by Amit Upadhye
Modified: 2021-07-28 11:27 UTC (History)
4 users (show)

Fixed In Version: rubygem-foreman_maintain-0.7.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 14:48:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31394 0 Urgent Closed Backup restore fails with Unrecognised option '--reset' 2021-02-02 15:49:31 UTC
Red Hat Product Errata RHBA-2021:1312 0 None None None 2021-04-21 14:48:34 UTC

Description Amit Upadhye 2020-11-26 12:31:45 UTC 
Restore is failing on Foreman 2.2 and 2.3 RC2 with below error,

~~~
[root@puppet ~]# yes | foreman-maintain restore $RESTORE_DIR
Running Restore backup ================================================================================
Check if command is run as root user: [OK]
--------------------------------------------------------------------------------
Validate backup has appropriate files: [OK]
--------------------------------------------------------------------------------
Confirm dropping databases and running restore:

WARNING: This script will drop and restore your database.
Your existing installation will be replaced with the backup database.
Once this operation is complete there is no going back.
[OK]
--------------------------------------------------------------------------------
Validate hostname is the same as backup: [OK]
--------------------------------------------------------------------------------
Setting file security:
- Restoring SELinux context [OK]
--------------------------------------------------------------------------------
Restore configs from backup:
\ Restoring configs [OK]
--------------------------------------------------------------------------------
Ensure restored MongoDB storage engine matches the current DB: [OK]
--------------------------------------------------------------------------------
Run installer reset:
- Installer reset [FAIL]
Failed executing yes | foreman-installer -v --reset , exit status 1:
ERROR: Unrecognised option '--reset'

See: 'foreman-installer --help'
--------------------------------------------------------------------------------
Scenario [Restore backup] failed.
~~~
Comment 1 Brad Buckingham 2020-11-30 15:08:07 UTC 
Moving from POST -> ASSIGNED, since the PR is still open upstream.
Comment 2 Bryan Kearney 2020-12-02 12:01:13 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31394 has been resolved.
Comment 3 Jameer Pathan 2020-12-15 07:49:37 UTC 
Verified

Verified with:
- Satellite 6.9.0 snap 5
- rubygem-foreman_maintain-0.7.0-1.el7sat.noarch

Test steps:
- Perform satellite backup and restore using foreman-maintain.

Observation:
- satellite backup/restore finished successfully.
Comment 6 errata-xmlrpc 2021-04-21 14:48:24 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 (Satellite 6.9 Satellite Maintenance Release), 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-2021:1312
Note You need to log in before you can comment on or make changes to this bug.