Hello,

The satellite-clone should take care of installing this packages on new system. The package installation on target system using foreman-maintain can complicate the restore procedure. Considering this, if packages are missing foreman-maintain will throw error and fail the check explicitly.

https://github.com/theforeman/foreman_maintain/pull/447
_
Amit Upadhye.

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31886 has been resolved.

Hi Vlad, do you happen to know if the failure mentioned in comment 3 would impact verification of bug 1889927?   If not, we may be able to get that one to go back through verification.  That bug had failed due to missing packages and referenced this one.

Hello Brad, the fix for comment#3 was already merged (https://github.com/theforeman/foreman_maintain/pull/453) and will be released today.

Regarding the BZ#1889927, I supposed the 'missing packages issue' will be fixed by this BZ and then cherrypicked into 6.8, which will allow me to verify #1889927. However, it seems this can't be done on the foreman-maintain side (see the comment#1). So we need to fix it in sat-clone or at least in docs to let the user know he needs to install those packages manually.

Just catching up on the conversation - What are the expectations for foreman-maintain restoring a backup on a Satellite remote db install? Sat-clone mostly installs a fresh Satellite with some of the user's configuration and then restores using foreman-maintain.

In theory, a fresh remote db install and a foreman-maintain restore would cause the same errors seen here. If the packages foreman-maintain is using for db checks aren't on a Satellite w/ remote db install, that seems like something we will need to address.

Using satellite-clone-2.0.1-1.el7sat.noarch and rubygem-foreman_maintain-0.7.7-1.el7sat.noarch (from 6.9.0 snap 17) I was able to verify that the output of the foreman-maintain restore informs the user properly about the missing commands when cloning the remote DB setup:

stdout: Running preparation steps required to run the next scenarios
================================================================================
Make sure Candlepin DB is up:                                         [FAIL]
The psql command not found. Make sure system has psql utility installed.
--------------------------------------------------------------------------------
Make sure Foreman DB is up:                                           [FAIL]
The psql command not found. Make sure system has psql utility installed.
--------------------------------------------------------------------------------
Make sure Mongo DB is up:                                             [FAIL]
The mongo command not found. Make sure system has mongo utility installed.
--------------------------------------------------------------------------------
Checks whether the tools for Mongo DB are installed:                  [OK]
--------------------------------------------------------------------------------
Scenario [preparation steps required to run the next scenarios] failed.

The following steps ended up in failing state:

  [candlepin-db-up]
  [foreman-db-up]
  [mongo-db-up]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="candlepin-db-up,foreman-db-up,mongo-db-up"


At the same time, the underlying issue is being fixed at the satellite-clone side (see BZ#1889927).

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

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days